Remote MCP · Endpoint

MimirAPI MCP server

No. MimirAPI answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mimirapi.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Latimer-Woods-Tech/mimirapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
167 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pay-per-call agent tools over x402 (USDC on Base) — no signup or API key.
Listing
From the official MCP registry (active).
Recent checks of MimirAPI
CheckedResultHandshake
2 hours agoHandshake completed167 ms
1 day agoHandshake completed120 ms
2 days agoHandshake completed187 ms
2 days agoHandshake completed194 ms
4 days agoHandshake completed120 ms
7 days agoHandshake completed281 ms
9 days agoHandshake completed149 ms
12 days agoHandshake completed413 ms
14 days agoHandshake completed132 ms
16 days agoHandshake completed110 ms
18 days agoHandshake completed204 ms
20 days agoHandshake completed123 ms
22 days agoHandshake completed105 ms
23 days agoHandshake completed216 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 MimirAPI and makes no claim about it beyond what these checks measured.