Remote MCP · Endpoint

符文戰場新手指南 MCP server

No. 符文戰場新手指南 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://riftbound-guide.panda198271.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.panda198271.riftbound-guide/riftbound-guide
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
117 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
符文戰場集換式卡牌新手規則與入門指南查詢。
Listing
From the official MCP registry (active).
Recent checks of 符文戰場新手指南
CheckedResultHandshake
1 hour agoHandshake completed117 ms
2 days agoHandshake completed86 ms
4 days agoHandshake completed79 ms
6 days agoHandshake completed154 ms
8 days agoHandshake completed97 ms
10 days agoHandshake completed87 ms
11 days agoHandshake completed90 ms
13 days agoHandshake completed72 ms
14 days agoHandshake completed75 ms
15 days agoHandshake completed419 ms
18 days agoHandshake completed108 ms
19 days agoHandshake completed37 ms
21 days agoHandshake completed139 ms
22 days agoHandshake completed43 ms
23 days agoHandshake completed47 ms

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

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 符文戰場新手指南 and makes no claim about it beyond what these checks measured.