Remote MCP · Endpoint

AuthiChain MCP server

No. AuthiChain answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://authichain.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.undone0603/authichain
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
84 ms
Tools exposed
6 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Look up AuthiChain product records. x402 paid verification and on-chain anchoring in development.
Listing
From the official MCP registry (active).
Recent checks of AuthiChain
CheckedResultHandshake
1 hour agoHandshake completed84 ms
2 days agoHandshake completed224 ms
4 days agoHandshake completed190 ms
6 days agoHandshake completed61 ms
8 days agoHandshake completed151 ms
10 days agoHandshake completed118 ms
11 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed126 ms
14 days agoHandshake completed71 ms
15 days agoHandshake completed110 ms
18 days agoHandshake completed126 ms
19 days agoHandshake completed69 ms
21 days agoHandshake completed829 ms
22 days agoHandshake completed70 ms
23 days agoHandshake completed59 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 AuthiChain and makes no claim about it beyond what these checks measured.