Doxa MCP
REMOTE · DOXA.APP
Christian AI for any question, any season. Bible (BSB), grace + truth. Self-run faith-AI check: 5/5.
Available components
Last scanned (21 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 452 tokens (~150/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://doxa.app/mcp/v1?src=registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=doxa.app | CN=YR2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | RSA 2048 | SHA256-RSA | 5dfc39537ebff0ed157b5051b3306c9e2c4 |
| SANs: doxa.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of doxa.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| doxa.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://*.googletagmanager.com https://cdn.clarity.ms https://www.clarity.ms https://connect.facebook.net https://analytics.tiktok.com https://static.ads-twitter.com https://insight.doxa.app https://accounts.google.com/gsi/ https://eu.posthog.com; style-src 'self' 'unsafe-inline' https://accounts.google.com/gsi/style; font-src 'self'; img-src 'self' data: https://nhkmkvwodisevtyvauvt.supabase.co https://www.facebook.com https://www.google.com https://www.google.co.uk https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.g.doubleclick.net https://storage.googleapis.com https://*.googleusercontent.com; connect-src 'self' https://nhkmkvwodisevtyvauvt.supabase.co https://nhkmkvwodisevtyvauvt.storage.supabase.co https://www.google-analytics.com https://*.google-analytics.com https://region1.analytics.google.com https://analytics.google.com https://*.analytics.google.com https://*.googletagmanager.com https://*.g. |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://doxa.app/mcp/v1?src=registry | Verified | 200 | |
| http (plaintext) | http://doxa.app/mcp/v1?src=registry | HTTPS enforced | 308 | https://doxa.app/mcp/v1?src=registry |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
doxa_encourage Scripture-anchored encouragement ~147
Generate Christian encouragement in the Doxa voice for the situation a user describes. Returns a short, screenshot-shareable response anchored in Scripture (Berean Standard Bible), tagged to one of the nine movements of The Doxa Way journey map: hear, discern, test, record, remember, engage, trust, fight, endure. No anthropomorphism, no AI companion framing.
| Name | Type | Req | Description |
|---|---|---|---|
| movement | string | – | Optional. Which movement of The Doxa Way fits: hear, discern, test, record, remember, engage, trust, fight, or endure. If absent, server infers. |
| situation | string | yes | Describe what the user is facing in 1-3 sentences. |
No output schema declared.
No examples provided.
doxa_scripture Look up a Bible verse ~109
Look up a Bible verse and return the Scripture text with a deep link to its Doxa Bible page. Defaults to the Berean Standard Bible (BSB, public domain Bible translation). Use for any Christian, biblical, Scripture, verse lookup, or devotional citation task where a clickable verse link matters. Reference format: "John 14:6" or "Psalm 23:1-3".
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Verse reference, e.g., "John 14:6" |
No output schema declared.
No examples provided.
doxa_way_movement The Doxa Way movements ~98
Get the nine movements of The Doxa Way, a biblical Christian discipleship framework: Hear, Discern, Test, Record, Remember, Engage, Trust, Fight, Endure. Use for faith journey mapping, Bible-grounded spiritual growth, or Christian encouragement context. Returns all nine movements, or one if specified.
| Name | Type | Req | Description |
|---|---|---|---|
| movement | string | – | Optional. Get a single movement by id. If absent, returns all 9. |
No output schema declared.
No examples provided.
How do I install the Doxa MCP server?
Doxa MCP is a hosted endpoint at https://doxa.app/mcp/v1?src=registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · doxa.app
claude mcp add --transport http the-doxa-way-doxa-mcp 'https://doxa.app/mcp/v1?src=registry'
What is the Doxa MCP server?
Doxa MCP is listed in the public MCP registry as io.github.The-Doxa-Way/doxa-mcp. Christian AI for any question, any season. Bible (BSB), grace + truth. Self-run faith-AI check: 5/5. This page covers its hosted endpoint (https://doxa.app/mcp/v1?src=registry).
Is the Doxa MCP server safe to use?
Doxa MCP scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Doxa MCP server expose?
Doxa MCP exposes 3 tools: doxa_encourage, doxa_scripture, doxa_way_movement. Their descriptions and schemas cost roughly 354 tokens of context every time the server is loaded.
Does the Doxa MCP server require authentication?
No. We connected to Doxa MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Doxa MCP server still maintained?
Doxa MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.