Remote MCP · Endpoint

Mangainfo MCP server

No. Mangainfo answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://mangainfo.com/mcp

The last check completed an MCP handshake.

Registry name
com.mangainfo/mangainfo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
428 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 10 checks
Described by its publisher as
English manga release dates, volumes, ISBNs and new licenses. Read only, no sign in.
Listing
From the official MCP registry (active).
Recent checks of Mangainfo
CheckedResultHandshake
2 days agoHandshake completed428 ms
6 days agoHandshake completed509 ms
16 days agoHandshake completed430 ms
17 days agoHandshake completed434 ms
17 days agoHandshake completed696 ms
19 days agoHandshake completed380 ms
20 days agoHandshake completed409 ms
21 days agoHandshake completed392 ms
22 days agoHandshake completed390 ms
23 days agoHandshake completed384 ms

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

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