Remote MCP · Endpoint

Mana Public MCP server

No. Mana Public answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://api.mana.am/mcp

The last check completed an MCP handshake.

Registry name
am.mana/mana-public
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
65 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only MCP tools for Mana public creations, tags, creator profiles, and share pages.
Listing
From the official MCP registry (active).
Recent checks of Mana Public
CheckedResultHandshake
7 hours agoHandshake completed65 ms
2 days agoHandshake completed101 ms
4 days agoHandshake completed110 ms
5 days agoHandshake completed67 ms
7 days agoHandshake completed56 ms
8 days agoHandshake completed106 ms
9 days agoHandshake completed98 ms
12 days agoHandshake completed75 ms
13 days agoHandshake completed75 ms
15 days agoHandshake completed55 ms
16 days agoHandshake completed59 ms
17 days agoHandshake completed62 ms
19 days agoHandshake completed69 ms
19 days agoHandshake completed315 ms
20 days agoHandshake completed50 ms
21 days agoHandshake completed83 ms
22 days agoHandshake completed65 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Mana Public and makes no claim about it beyond what these checks measured.