Remote MCP · Endpoint

Akashi Notari MCP server

No. Akashi Notari answered an MCP handshake 38 minutes ago.

UpLast checked 38 minutes ago

Server URL

https://anchor.akashi-notari.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.self-reality/akashi-notari
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
113 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Proof of existence for files: anchor a SHA-256 hash on Base, look up proofs. Paid with x402.
Listing
From the official MCP registry (active).
Recent checks of Akashi Notari
CheckedResultHandshake
38 minutes agoHandshake completed113 ms
3 days agoHandshake completed205 ms
13 days agoHandshake completed111 ms
13 days agoHandshake completed102 ms
15 days agoHandshake completed131 ms
16 days agoHandshake completed153 ms
17 days agoHandshake completed76 ms
18 days agoHandshake completed81 ms
18 days agoHandshake completed121 ms
20 days agoHandshake completed100 ms
22 days agoHandshake completed145 ms
25 days agoHandshake completed102 ms
27 days agoHandshake completed182 ms

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

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