✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.
What it offers — 6 tools · Developer Tools
geo_check
Run the 24-rule Synapse GEO linter against a URL or a local project path and return a scored report. Use this BEFORE shipping a new product.
geo_fix
Apply Synapse's auto-fixers to a local project — writes static files (llms.txt, robots.txt, agent-answer.json, etc.). Requires write access to the pat
geo_track_init
Register the project with the Synapse dashboard to begin tracking AI-agent referrals. Returns a slug and tracking ID.
geo_prompts
Generate the prompt pack used to test whether AI engines surface this product.
geo_status
Fetch the live Growth Score and agent-mention stats for an installed Synapse site.
geo_corpus_query
Query the public Synapse corpus for products matching a given intent.
Spec conformance20%100
✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 6 tools
✓ every tool has name + inputSchema
Security (OWASP MCP)30%100
6 tools scanned
no injection markup
no secret-path refs
Reliability / performance20%84
single-probe latency 1090ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)
Tool hygiene15%80
100% of tools have typed inputSchema
0/6 declare outputSchema
no unannotated destructive tools
Transparency / provenance15%70
HTTPS ✓
advertises protocol 2025-06-18
Observed behavior
No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.
Findings
No blocking issues found in the static + spec checks.
We re-grade runsynapse.dev on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.