Remote MCP · Endpoint

io.github.SirCharan/theflamesgame MCP server

No. io.github.SirCharan/theflamesgame answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://theflamesgame.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.SirCharan/theflamesgame
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
140 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 8 checks
Described by its publisher as
FLAMES name game plus love and friendship calculators by name. A game, not a prediction.
Listing
From the official MCP registry (active).
Recent checks of io.github.SirCharan/theflamesgame
CheckedResultHandshake
4 days agoHandshake completed140 ms
5 days agoHandshake completed104 ms
6 days agoHandshake completed172 ms
7 days agoHandshake completed105 ms
9 days agoHandshake completed478 ms
9 days agoHandshake completed72 ms
10 days agoHandshake completed159 ms
11 days agoHandshake completed85 ms

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

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 io.github.SirCharan/theflamesgame and makes no claim about it beyond what these checks measured.