Remote MCP · Endpoint

Annalist MCP server

No. Annalist answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.annalist.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.ryanroskowski/annalist
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
72 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Signed data for agents: agentic-commerce census, dependency digest, x402/MCP checks, Hyperliquid
Listing
From the official MCP registry (active).
Recent checks of Annalist
CheckedResultHandshake
1 hour agoHandshake completed72 ms
12 hours agoHandshake completed252 ms
1 day agoHandshake completed271 ms
2 days agoHandshake completed136 ms
4 days agoHandshake completed40 ms
4 days agoHandshake completed158 ms
5 days agoHandshake completed289 ms
6 days agoHandshake completed134 ms
8 days agoHandshake completed205 ms
11 days agoHandshake completed170 ms
13 days agoHandshake completed140 ms
16 days agoHandshake completed230 ms
18 days agoHandshake completed235 ms
20 days agoHandshake completed198 ms
22 days agoHandshake completed140 ms
24 days agoHandshake completed294 ms

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

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