Remote MCP · Endpoint

Metal Mantra MCP server

No. Metal Mantra answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://metalmantra.io/mcp

The last check completed an MCP handshake.

Registry name
io.metalmantra/registry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
655 ms
Tools exposed
6 tools
Uptime, last 30 days
71.4% from 14 checks
Described by its publisher as
Read-only evidence reports on AI agents: search, fetch a report, check trust. Not a certification.
Listing
From the official MCP registry (active).
Recent checks of Metal Mantra
CheckedResultHandshake
2 hours agoHandshake completed655 ms
1 day agoHandshake completed664 ms
2 days agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
9 days agoHandshake completed654 ms
12 days agoHandshake completed716 ms
14 days agoHandshake completed760 ms
16 days agoHandshake completed758 ms
18 days agoHandshake completed733 ms
20 days agoHandshake completed713 ms
22 days agoHandshake completed690 ms
23 days agoHandshake completed736 ms

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

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 Metal Mantra and makes no claim about it beyond what these checks measured.