‹ directory
90MCP SCORE
A

synap

https://synap402.com/mcp
4 tools~1.3k tok/req100% annot.proto 2026-07-28
View public page ›
Xin
Raw JSON ›

Score by pillar

Security ·20100
Tool design ·18100
Schemas / desc ·1680
Reliability ·14100
Context-cost ·1289
Compliance ·12100
Coverage ·850

reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)

Context-cost

1.3ktokens for tools/list

Paid on every request. Lean footprint for 4 tools.

this server1.3k
median≈ 3k

MCP primitive coverage

the quality score covers tools
4
Tools
0
Resources · none
0
Prompts · none

Why this score — causal attribution

Each penalty: measure → mechanism → effect → Δscore.

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

MCP Score badge — synap[![MCP Score](https://checkmcp.dev/badge/synap402-com.svg?url=https%3A%2F%2Fsynap402.com%2Fmcp)](https://checkmcp.dev/report?url=https%3A%2F%2Fsynap402.com%2Fmcp)

About synap — FAQ

Is the synap MCP server safe to use?+
CheckMCP audited synap and gave it an MCP Score of 90/100 (grade A) — strong — no blocking security or design issues were found. 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 synap?+
synap scores 90/100 (grade A) 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 synap expose, and what is its context cost?+
synap exposes 4 tools, and its tools/list response costs roughly 1.3k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was synap scored?+
By probing the live MCP endpoint (https://synap402.com/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.