io.github.TheDoxaWay/doxa-mcp

MCPcommunitylive
v1.0.3io.github.TheDoxaWayUnknownUpdated 4mo agoGitHub

Christian AI for any question, in any season. Bible (BSB), grace + truth. faith.tools 5/5.

A Christian AI for any question, in any season. Truth that points to Jesus, and to real relationships. Get the Doxa app · Doxa on Telegram · A hosted Model Context Protocol server that brings Bible verses and Christian encouragement to any AI assistant. Drop it into Claude Desktop, Cursor, Cline, or any MCP client. For anyone with a question. The believer growing in faith. The…

Endpoint healthlive
checked 10 days ago · 576ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
4mo agoLast update
Package
Authorio.github.TheDoxaWay
LicenseUnknown
Version1.0.3
Sourcemcp-registry
GitHubThe-Doxa-Way/doxa-mcp-schema
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 2 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

A Christian AI for any question, in any season. Truth that points to Jesus, and to real relationships. Get the Doxa app · Doxa on Telegram · A hosted Model Context Protocol server that brings Bible verses and Christian encouragement to any AI assistant. Drop it into Claude Desktop, Cursor, Cline, or any MCP client. For anyone with a question. The believer growing in faith. The seeker searching. The curious. The skeptical. The hurt. Built for the growing chapters: loving God more,…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.