Expert-curated knowledge, brand, research & earnings intelligence — 31 tools, 220+ graphs.

MCP readiness

F · 11/100

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, 13.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	0/10	initialize did not answer cleanly (HTTP 410).
Live MCP endpoint	5/25	Endpoint answers, but not with MCP JSON-RPC (89 ms).
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/30 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	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (89 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

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 11 · peer median 81
Latency: Faster than 93% of peers; This listing 89 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Live MCP endpoint −20 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers, but not with MCP JSON-RPC (89 ms).
Uptime (30 days) −15 — Stay reachable in our daily probes.
Now: 0/30 probes succeeded over 30 days (0%).
Valid MCP handshake −10 — Complete the MCP handshake without errors.
Now: initialize did not answer cleanly (HTTP 410).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

chiark since 2026-06-16 ↗ agenstry since 2026-08-18 ↗

How to connect

MCP endpoint (sse)

https://mcp.fodda.ai/sse

JSON-RPC initialize probe

curl -X POST https://mcp.fodda.ai/sse \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://mcp.fodda.ai

Listed at (chiark)

https://agenstry.com/mcp/ai.fodda/mcp-server