‹ directory
87MCP SCORE
B
nanoparse-mcp
https://nanoparse.app/mcp
2 tools~1.0k tok/req0% annot.proto 2024-11-05
Score by pillar
Security ·20100
Tool design ·18100
Schemas / desc ·16100
Reliability ·14100
Context-cost ·1281
Compliance ·1257
Coverage ·850
reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)
Context-cost
1.0ktokens for
tools/listPaid on every request. Lean footprint for 2 tools.
this server1.0k
median≈ 3k
MCP primitive coverage
the quality score covers tools2
Tools
0
Resources · none
0
Prompts · none
Why this score — causal attribution
Each penalty: measure → mechanism → effect → Δscore.
Compliance · MEDIUM−3.6
0 declared annotations → destructiveHint/openWorldHint missing -> worst-case defaults → the tool is treated as destructive & open-world by clients
Compliance · MEDIUM−1.6
proto 2024-11-05 (4 rev. behind 2025-11-25) → outdated protocol version → recent features unavailable, recent clients weakened
Compliance · LOW−0.6
no OAuth discovery (.well-known missing) → RFC 9728/8414 not exposed → auth not auto-discoverable by clients
Badge — paste it in your README
[](https://checkmcp.dev/report?url=https%3A%2F%2Fnanoparse.app%2Fmcp)Own this server?Get verified — fresh re-audit, badge if you pass ›
About nanoparse-mcp — FAQ
Is the nanoparse-mcp MCP server safe to use?+
CheckMCP audited nanoparse-mcp and gave it an MCP Score of 87/100 (grade B) — good — only minor issues. The audit runs an OWASP MCP Top 10 security pass (tool poisoning, hardcoded secrets, command injection, the lethal trifecta) against the live endpoint; see the per-pillar breakdown and the "why this score" attribution on this page, and re-audit anytime at checkmcp.dev.
What is the MCP Score of nanoparse-mcp?+
nanoparse-mcp scores 87/100 (grade B) on CheckMCP's vendor-neutral audit across six weighted pillars — security, tool design, schemas, context-cost, compliance and coverage — with reliability measured and shown but not yet credited.
How many tools does nanoparse-mcp expose, and what is its context cost?+
nanoparse-mcp exposes 2 tools, and its tools/list response costs roughly 1.0k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was nanoparse-mcp scored?+
By probing the live MCP endpoint (https://nanoparse.app/mcp), inspecting its tools, schemas and protocol compliance, running an OWASP MCP Top 10 security pass, and measuring the token cost of tools/list — then attributing every penalty as measure → mechanism → effect. The methodology is open: checkmcp.dev/#methodology.