Pre-install MCP check
B Passed 9/10 protocol & hygiene checks when last observed — a protocol/readiness measurement, not a quality or safety verdict.
Operational state: Observed callable — last observed 2026-08-29 (fresh). The most recent check completed the MCP handshake (initialize + tools/list) successfully.
https://api.echoloc.ai/mcp
· signed observation (ed25519)
| ✓ | Speaks the MCP protocol correctly (valid handshake) | C1 |
| ✓ | Lists its tools | C2 |
| ✓ | Tools are well-formed (valid names + typed input schemas) | C3 |
| ✓ | Tool descriptions are clear enough for an agent to pick the right one | C4 |
| ✓ | Tools declare safety hints (read-only vs destructive) | C5 |
| ✓ | Is live and responds within 5s | C6 |
| — | Returns real content — not an empty 'ghost' server | C7 · gap |
| ✓ | Identifies itself (name + version) | C8 |
| ✓ | Doesn't bloat your context window (reasonable payload size) | C9 |
| ✓ | Handles malformed input honestly (structured error, no crash) | C10 |
Top gap: C7 Returns real content (anti-ghost) — UNVERIFIED — read-only tool 'list_technologies' rejected synthetic args (validation/no-match, not a ghost) (sampled 3 read-only tools, none substantive)
This check looks only at how the server speaks the MCP protocol from the outside. It does not inspect the server's source code, its npm/package supply chain, hidden or poisoned tool instructions, what it does with your data, or whether it changes after you install it (a "rug-pull"). Always review the source before installing.
Observed 2026-08-29 · check another server
SaSame MCP Observatory — an independent, external observer of public MCP servers. Observations are made from outside via the public MCP handshake; unclaimed servers have not confirmed their listing, and a passing check is not an endorsement. This is a protocol/liveness/hygiene check, not a malware or supply-chain audit. About the standard · Public MCP (no key)