Remote MCP · Endpoint

hamir MCP server

No. hamir answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://hamir.app/mcp

The last check completed an MCP handshake.

Registry name
app.hamir/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
News search, article lookup, story coverage and save links for hamir's RSS catalogue
Listing
From the official MCP registry (active).
Recent checks of hamir
CheckedResultHandshake
7 hours agoHandshake completed160 ms
2 days agoHandshake completed165 ms
4 days agoHandshake completed162 ms
5 days agoHandshake completed146 ms
7 days agoHandshake completed141 ms
8 days agoHandshake completed145 ms
9 days agoHandshake completed138 ms
12 days agoHandshake completed184 ms
13 days agoHandshake completed151 ms
15 days agoHandshake completed151 ms
16 days agoHandshake completed197 ms
17 days agoHandshake completed156 ms
19 days agoHandshake completed135 ms
19 days agoHandshake completed136 ms
20 days agoHandshake completed167 ms
21 days agoHandshake completed177 ms
22 days agoHandshake completed163 ms

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

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