Remote MCP · Endpoint

io.github.inamprotocol/inam-mcp MCP server

No. io.github.inamprotocol/inam-mcp answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.inamprotocol.org/mcp

The last check completed an MCP handshake.

Registry name
io.github.inamprotocol/inam-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
495 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check an agent's INAM reputation before trusting it, and sign a receipt when work is done.
Website
https://inamprotocol.org/
Repository
https://github.com/inamprotocol/inam-protocol
Listing
From the official MCP registry (active).
Recent checks of io.github.inamprotocol/inam-mcp
CheckedResultHandshake
5 hours agoHandshake completed495 ms
2 days agoHandshake completed235 ms
4 days agoHandshake completed373 ms
6 days agoHandshake completed375 ms
8 days agoHandshake completed538 ms
10 days agoHandshake completed160 ms
12 days agoHandshake completed184 ms
13 days agoHandshake completed250 ms
14 days agoHandshake completed351 ms
16 days agoHandshake completed189 ms
18 days agoHandshake completed154 ms
20 days agoHandshake completed196 ms
22 days agoHandshake completed241 ms
23 days agoHandshake completed237 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.inamprotocol/inam-mcp and makes no claim about it beyond what these checks measured.