Remote MCP · Endpoint

Zovo SEC Filings MCP server

No. Zovo SEC Filings answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://sec-filings.zovo.one/mcp

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/sec-filings
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
457 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
SEC filings and financials
Listing
From the official MCP registry (active).
Recent checks of Zovo SEC Filings
CheckedResultHandshake
44 minutes agoHandshake completed457 ms
3 days agoHandshake completed65 ms
13 days agoHandshake completed319 ms
13 days agoHandshake completed310 ms
15 days agoHandshake completed211 ms
15 days agoHandshake completed211 ms
17 days agoHandshake completed245 ms
18 days agoHandshake completed159 ms
18 days agoHandshake completed177 ms
20 days agoHandshake completed295 ms
22 days agoHandshake completed154 ms
25 days agoHandshake completed220 ms
27 days agoHandshake completed266 ms

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

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