Remote MCP · Endpoint

hamir MCP server

No. hamir answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
130 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 18 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
1 hour agoHandshake completed130 ms
1 day agoHandshake completed140 ms
2 days agoHandshake completed136 ms
3 days agoHandshake completed239 ms
4 days agoHandshake completed232 ms
5 days agoHandshake completed134 ms
7 days agoHandshake completed154 ms
10 days agoHandshake completed134 ms
12 days agoHandshake completed160 ms
15 days agoHandshake completed168 ms
17 days agoHandshake completed167 ms
19 days agoHandshake completed159 ms
21 days agoHandshake completed160 ms
23 days agoHandshake completed165 ms
25 days agoHandshake completed162 ms
26 days agoHandshake completed146 ms
28 days agoHandshake completed141 ms
29 days agoHandshake completed145 ms

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

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.