Remote MCP · Endpoint

io.github.cyanheads/secedgar-mcp-server MCP server

No. io.github.cyanheads/secedgar-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://secedgar.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/secedgar-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
244 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Query SEC EDGAR filings, XBRL financials, and company data via MCP. STDIO or Streamable HTTP.
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/secedgar-mcp-server
CheckedResultHandshake
1 hour agoHandshake completed244 ms
1 day agoHandshake completed380 ms
3 days agoHandshake completed117 ms
3 days agoHandshake completed237 ms
4 days agoHandshake completed247 ms
5 days agoHandshake completed122 ms
7 days agoHandshake completed402 ms
10 days agoHandshake completed264 ms
12 days agoHandshake completed243 ms
15 days agoHandshake completed260 ms
17 days agoHandshake completed275 ms
19 days agoHandshake completed104 ms
21 days agoHandshake completed103 ms
23 days agoHandshake completed605 ms
25 days agoHandshake completed245 ms
26 days agoHandshake completed91 ms
28 days agoHandshake completed128 ms
29 days agoHandshake completed86 ms

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

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 io.github.cyanheads/secedgar-mcp-server and makes no claim about it beyond what these checks measured.