ClaimFinder Settlements MCP Server
https://claimfinder-mcp.sigrunner.workers.dev/mcp
● healthy
Free keyless MCP: list, search & look up open US class-action settlements and claim deadlines.
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2026-07-28
negotiated, not declared
MCP readiness
A · 90/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 A, 99.5/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (84 ms). |
| Protocol revision | 10/10 | Speaks the current MCP revision 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 1/1 probes succeeded; final after 5 probes in 30 days. |
| Tool declaration | 10/10 | Lists 3 tool(s) with descriptions. |
| Verified identity | 7/10 | Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time). |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive
(84 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 52,570 reachable MCP servers in our daily snapshot (2026-11-11 14:47 UTC). Display only; it does not change search order.
- Readiness
- Higher than 98% of peers
- This listing 90 · peer median 81
- Latency
- Faster than 95% of peers
- This listing 84 ms · peer median 371 ms
Where it loses the most points
- Auth declaration −5 — How to authenticate is not stated.
- Verified identity −3 — Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
- Freshness + modern flags −1 — seen in a source within 7 days.
Listed in
Directories this entry was found in.
mcp-registry since 2026-11-11
How to connect
MCP endpoint (streamable-http)
https://claimfinder-mcp.sigrunner.workers.dev/mcpJSON-RPC initialize probe
curl -X POST https://claimfinder-mcp.sigrunner.workers.dev/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'