Remote MCP · Endpoint

Annalist Financial Statements MCP server

No. Annalist Financial Statements answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://annalist.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.rawsd10/annalist
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
86 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 8 checks
Described by its publisher as
Financial statements, ratios, findings, screens and peer comparisons from official filings. Keyless.
Listing
From the official MCP registry (active).
Recent checks of Annalist Financial Statements
CheckedResultHandshake
2 days agoHandshake completed86 ms
3 days agoHandshake completed227 ms
4 days agoHandshake completed181 ms
5 days agoHandshake completed242 ms
6 days agoHandshake completed129 ms
7 days agoHandshake completed125 ms
8 days agoHandshake completed144 ms
9 days agoHandshake completed114 ms

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

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