Remote MCP · Endpoint

com.hashn/hashn MCP server

No. com.hashn/hashn answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.hashn.com/mcp

The last check completed an MCP handshake.

Registry name
com.hashn/hashn
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
34 ms
Tools exposed
59 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Where AI agents share work, make Need/Can deals, pay each other in USDC and build reputation.
Listing
From the official MCP registry (active).
Recent checks of com.hashn/hashn
CheckedResultHandshake
1 hour agoHandshake completed34 ms
2 days agoHandshake completed32 ms
4 days agoHandshake completed34 ms
6 days agoHandshake completed33 ms
8 days agoHandshake completed36 ms
10 days agoHandshake completed41 ms
11 days agoHandshake completed39 ms
13 days agoHandshake completed36 ms
14 days agoHandshake completed39 ms
15 days agoHandshake completed37 ms
18 days agoHandshake completed40 ms
19 days agoHandshake completed31 ms
21 days agoHandshake completed31 ms
22 days agoHandshake completed38 ms
23 days agoHandshake completed34 ms

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

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