Establish verifiable identities and reputations through a public registry and tiered certification system. Discover new capabilities or request specific features via a collaborative wishing well and marketplace. Foster trust and visibility using secure on-chain payments and community endorsements.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here E, 7.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 0/10 | No MCP handshake completed. |
| Live MCP endpoint | 0/25 | Endpoint did not answer. |
| Protocol revision | 0/10 | No protocol revision reported by initialize. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 0/15 | 0/28 probes succeeded over 30 days (0%). |
| Tool declaration | 0/10 | No tools listed by tools/list. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.
- Readiness
- Higher than 0% of peers
- This listing 8 · peer median 81
- Latency
- Faster than 28% of peers
- This listing 532 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Live MCP endpoint −25
— Answer initialize and tools/list at the declared endpoint.
Now: Endpoint did not answer.
- Uptime (30 days) −15
— Stay reachable in our daily probes.
Now: 0/28 probes succeeded over 30 days (0%).
- Valid MCP handshake −10
— Complete the MCP handshake without errors.
Now: No MCP handshake completed.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/agentstamp/agentstamp/mcp
curl -X POST https://server.smithery.ai/agentstamp/agentstamp/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'