Remote MCP · Endpoint

Linkame MCP server

No. Linkame answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://linkame-a5883.web.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.ohdonpiano/linkame
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
182 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Access authorized Linkame contacts, profiles, events, tickets and matching results.
Listing
From the official MCP registry (active).
Recent checks of Linkame
CheckedResultHandshake
42 minutes agoHandshake completed182 ms
3 days agoHandshake completed193 ms
13 days agoHandshake completed168 ms
13 days agoHandshake completed171 ms
15 days agoHandshake completed176 ms
15 days agoHandshake completed180 ms
17 days agoHandshake completed230 ms
18 days agoHandshake completed173 ms
18 days agoHandshake completed194 ms
20 days agoHandshake completed158 ms
22 days agoHandshake completed239 ms
25 days agoHandshake completed180 ms
27 days agoHandshake completed183 ms

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

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