Reference Source · MCP server health

am.mana/mana-public

Read-only MCP tools for Mana public creations, tags, creator profiles, and share pages.

5 endpoints on the official MCP registry. Probed daily.

https://mana.am/docs/mcp

answered, no tool list

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions0% of the last 7 probes · 0% of the last 30
Handshake latencymedian 463 ms, 95th 589 ms
Tools listed—
Protocol answered2025-11-25
Transportstreamable-http
Last detailinitialize ok; tools/list HTTPError: HTTP Error 400: Bad Request

https://api.mana.am/mcp

answered, tools listed

Last 30 probes
Last seen healthy2026-10-23
Completed sessions100% of the last 7 probes · 100% of the last 30
Handshake latencymedian 443 ms, 95th 1570 ms
Tools listed3
Tool contract016117182eee — unchanged over the 24 days we have read it
Protocol answered2025-11-25
Transportstreamable-http

https://mana.am/mcp

answered, no tool list

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions0% of the last 7 probes · 0% of the last 30
Handshake latencymedian 435 ms, 95th 2238 ms
Tools listed—
Protocol answered2025-11-25
Transportstreamable-http
Last detailinitialize ok; tools/list HTTPError: HTTP Error 400: Bad Request

https://mana.am/api/mcp

answered, no tool list

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions0% of the last 7 probes · 0% of the last 30
Handshake latencymedian 166 ms, 95th 3748 ms
Tools listed—
Protocol answered2025-11-25
Transportstreamable-http
Last detailinitialize ok; tools/list HTTPError: HTTP Error 400: Bad Request

https://mana.am/webmcp

answered, no tool list

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions0% of the last 7 probes · 0% of the last 30
Handshake latencymedian 137 ms, 95th 1954 ms
Tools listed—
Protocol answered2025-11-25
Transportstreamable-http
Last detailinitialize ok; tools/list HTTPError: HTTP Error 400: Bad Request

Embed the badge

[![MCP](https://referencesource.org/mcp-health/badge/am-mana-mana-public.svg)](https://referencesource.org/mcp-health/server/am-mana-mana-public/)

The badge shows the most recent probe. It is generated from the same file this page is, updates once a day, and needs no key. This entry publishes 5 endpoints, and the badge reports the best result among them — the question a badge answers is whether a client can reach this project at all, and one dead spare URL is not a reason to call the project down. The per-endpoint verdicts are above, each with its own link.

What was actually measured

One HTTP POST carrying a JSON-RPC initialize, and if that succeeds, a tools/list. Nothing here is a score, a rating or a judgement about whether the server is any good — only whether an ordinary MCP client could complete a session with it on the day we asked. “Needs credentials” is not a fault: it means the endpoint wants an account, which is a perfectly reasonable thing for it to want.

The tool contract row is a digest of what tools/list returned — each tool's name, description and input schema, hashed — so that a rename, a newly-required field or a rewritten description can be spotted even though none of them breaks the connection. We keep the digests and nothing else: no tool name, description or schema of anybody's is stored or republished here, which is also why this can say that a contract moved and by how much, but not what it now says.

The method and the daily totals · every server we probe, A–Z · feed.json · licence · corrections and removals: [email protected]