Moxie Docs MCP vs SiteCheck
A side-by-side look at the Moxie Docs MCP and SiteCheck MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SiteCheckCommunication · Remote HTTP/SSE29 pay-per-call agent tools: web reader, PDF, tech stack, email, domain, Solana, KYB. Paid via x40243FairAuth: no auth requiredVerdict: choose Moxie Docs MCP for knowledge & memory work as a local process; choose SiteCheck for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
SChoose SiteCheck when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SiteCheck | |
|---|---|---|
| Category | Knowledge & Memory | Communication |
| Quality signal | 80/100 · Excellent | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | Freemium | Paid service |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removal
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
SiteCheck
{
"mcpServers": {
"sitecheck": {
"url": "https://api.sitecheck-api.workers.dev/mcp"
}
}
}
Frequently asked questions
Moxie Docs MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. SiteCheck belongs to Communication and uses a remote HTTP/SSE transport. Pick Moxie Docs MCP for knowledge & memory work and SiteCheck for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. SiteCheck is listed as a paid service. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add moxie-docs-mcp and sitecheck as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Moxie Docs MCP has a quality signal of 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars. SiteCheck has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
