MCP servers › wiki.apologetics › apologetics-wiki
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
wiki.apologetics/apologetics-wiki
Bible verses, cross-references, Greek and Hebrew word studies, and Christian apologetics articles. — the publisher's description
Summary
wiki.apologetics/apologetics-wiki is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 38 tools, 4 resources and 3 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Tools
- 38
- Described as changing data
- 7 of 38 toolsAI-classified
- Last tested
- 2026-10-23
Observed fact
This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (save_item, remove_saved). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.
Worth knowing before you connect it
- 7 tools are described as changing something (suggest_article_change, propose_new_article, suggest_topic, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.0, published 2026-10-20 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-20 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-20).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventory7 of 38 tools are described as changing something (creating, editing, deleting, sending or running).
“Search published articles by title, description, tags, and shelf.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
querystringrequiredshelfstringlimitinteger
“ChatGPT-compatible search.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
querystringrequired
“ChatGPT-compatible fetch by id (article:, hub:, bible:, apocrypha:, or non-canonical:).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
idstringrequired
“Published article for a path, a slug, or a full https://apologetics.wiki URL.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
pathstringslugstringfullboolean
“List published articles, optionally on one shelf.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
shelfstringlimitintegercursorstring
“Religions, beliefs, denominations, Islam branches, the Bible, the Apocrypha, and Non-Canonical, with hub URLs and article counts.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
“King James text for a book name or OSIS code (John, 1 John, Song of Solomon, Psalm, jhn), including the Apocrypha and Non-Canonical.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
bookstringrequiredchapterintegerverseintegerreferencestring
- get_word_studyreads or searches
“Greek or Hebrew word-page data from the same indexes as /bible/greek and /bible/hebrew.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
strongsstringslugstring
- list_common_argumentsreads or searches
“Claims that recur in conversation: the claim, a one-line answer, the texts, and the article URL or Article coming.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
groupstringquerystringlimitintegercursorstring
- get_common_argumentreads or searches
“One claim by id: the answer, the texts, the group-page anchor, and the article URL or Article coming.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
idstringrequired
- site_summaryreads or searches
“Mission, shelves, how to cite, and links to llms.txt, skill.md, and Connect.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
“The plain-language qualities a published article meets, the editing note, how sources are credited, and the drafting prompt.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
topicstring
Show 26 more tools
- check_existing_coveragereads or searches
“Compare a proposed title, and an optional draft, with published articles.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
titlestringrequireddraftstring
- suggest_article_changecreates or changes datadescribed as changing data
“Read get_submission_guidelines first.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs, 3 required
pathstringrequiredsummarystringrequireddetailstringrequiredproposed_markdownstringsourcesarray
- propose_new_articlecreates or changes datadescribed as changing data
“Read get_submission_guidelines first.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs, 4 required
titlestringrequiredshelfstringrequiredsummarystringrequiredmarkdownstringrequiredsourcesarray
- suggest_topiccreates or changes datadescribed as changing data
“Read get_submission_guidelines first.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 1 required
titlestringrequiredsummarystringexplainerstringsourcesarray
“The signed-in account’s own suggestions and their review status.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
statusstring
“Account id, display name, role, and today’s remaining suggestion quota.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- find_articles_for_claimreads or searches
“Match an objection to common arguments and published articles.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
textstringrequiredlimitinteger
“King James text for a free-form reference on the Bible, Apocrypha, or Non-Canonical shelf.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
referencestringrequiredincludearray
“King James text and every public-domain line the verse page prints: the American Standard Version, Young’s Literal Translation, the World English Bible, Darby, and Douay-Rheims, plus the Jewish Publi…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
referencestringrequired
“Title, description, key points, and the canonical URL for one article.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
slugstringpathstring
- get_article_sectionreads or searches
“One heading’s section from a published article, capped in length.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
slugstringpathstringheadingstringrequired
- related_articlesreads or searches
“Articles that share a shelf or a verse with a slug or a scripture reference.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
slugstringreferencestringlimitinteger
“Links for a passage from every source the verse page uses, each labelled: curated links (including Jude 1:14–15 and 1 Enoch 1:9), New Testament quotations, fulfilled prophecy, allusions, the messiani…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
referencestringrequired
- get_canon_statusreads or searches
“Protestant, Catholic, Orthodox, and Ethiopian status for a Bible, Apocrypha, or Non-Canonical book, with the site’s canon note.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
bookstringrequired
- search_word_studyreads or searches
“Find Greek or Hebrew lemmas by gloss, transliteration, lemma, or Strong’s number.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
querystringrequiredlimitinteger
- lookup_quotereads or searches
“A Qur’an or hadith quotation stored on this site, with the translation name and the source URL.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
referencestringrequired
- get_connections_by_bookreads or searches
“Old Testament and New Testament connections for one King James book.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
bookstringrequiredtypestringmin_weightinteger
- get_connection_graphreads or searches
“Nodes and edges for the connection map.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
levelstringtypestringtestament_filterstring
- get_messianic_propheciesreads or searches
“Messianic rows from the connection files, with links to the Old Testament and New Testament verse pages.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
themestring
“Row counts, arc counts, the See Also cap, licenses, and download URLs for the connection files.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
“The sources listed on one article, with absolute URLs.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
slugstringpathstring
“Get the sign-in link.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
emailstring
- confirm_sign_indoes something elsedescribed as changing data
“Exchange the emailed code for a scoped API key, for a client without OAuth.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 2 required
emailstringrequiredotpstringrequiredscopesarray
“The signed-in account’s saved articles and Bible verses.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
“Save an article path or a Bible verse path for the signed-in account.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 2 required
kindstringrequiredrefstringrequired
“Remove one saved article or Bible verse for the signed-in account.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
kindstringrequiredrefstringrequired
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 38 tools
- Says what it returns
- 94% of 35 tools
- States limits, defaults or errors
- 19% of 36 tools
- Says when to use it
- 8% of 38 tools
- Items covered per tool
- 2.3 of 4 on average
Counted from the listing
- Parameters with a description
- 0% of 75
- Tools with a description
- 100% of 38
- Typical description length
- 223 characters
The tool set
Counted from the listing
- Tools
- 38
- Size of the list
- about 7,864 tokens for an agent to load (characters ÷ 4)
- Naming
- 35 of 38 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 38 of 38 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://apologetics.wiki/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"apologetics-wiki": {
"url": "https://apologetics.wiki/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"apologetics-wiki": {
"type": "http",
"url": "https://apologetics.wiki/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"apologetics-wiki","type":"http","url":"https://apologetics.wiki/mcp"}'Claude Code
claude mcp add --transport http apologetics-wiki https://apologetics.wiki/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://apologetics.wiki/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint apologetics.wiki/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about wiki.apologetics/apologetics-wiki
Answered from the data aboveIs wiki.apologetics/apologetics-wiki safe to install?
We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 7 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does wiki.apologetics/apologetics-wiki need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has wiki.apologetics/apologetics-wiki been security tested?
Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.
What can wiki.apologetics/apologetics-wiki do?
It lists 38 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and do something else. We did not call any tool, so this describes the text, not the behaviour.
Can wiki.apologetics/apologetics-wiki change or delete data?
7 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: exercised
- Fake assistant turns: exercised
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
5 exercised11 not run (reason given)2 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 12Hidden content
audience-hidingChecks resources that hide content from the user.exercised - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 803 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 38 tools, 4 resources, 3 prompts.
- 5,317 msFinished: 5 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “wiki.apologetics/apologetics-wiki: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/wiki.apologetics/apologetics-wiki
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/wiki.apologetics/apologetics-wiki)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology