AgentReader
https://api.axiomworks.co.uk/mcp
● down
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-11-25
negotiated, not declared
MCP readiness
F · 40/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 D, 25.8/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 | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 8.57/15 | 4/7 probes succeeded over 30 days (57%). |
| Tool declaration | 10/10 | Lists 60 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 | 2/5 | seen within 30 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Applicable criteria total 90 points, scaled to 100.
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 4% of peers
- This listing 40 · peer median 81
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.
- Valid MCP handshake −10
— Complete the MCP handshake without errors.
Now: No MCP handshake completed.
- Uptime (30 days) −6.4
— Stay reachable in our daily probes.
Now: 4/7 probes succeeded over 30 days (57%).
Listed in
Directories this entry was found in.
submission since 2026-11-05
↗
mcp-registry since 2026-11-05
How to connect
MCP endpoint (streamable-http)
https://api.axiomworks.co.uk/mcpJSON-RPC initialize probe
curl -X POST https://api.axiomworks.co.uk/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'Homepage
https://api.axiomworks.co.uk/mcp
Listed at (submission)
https://api.axiomworks.co.uk/mcp