Remote MCP · Endpoint

SecFeed: SEC EDGAR filings MCP server

No. SecFeed: SEC EDGAR filings answered an MCP handshake 15 minutes ago.

UpLast checked 15 minutes ago

Server URL

https://secfeedapi.com/mcp

The last check completed an MCP handshake.

Registry name
com.secfeedapi/secfeed
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
293 ms
Tools exposed
40 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
SEC EDGAR data as tools: filing search, full text, XBRL financials, insider trades, 13F, 8-K events.
Listing
From the official MCP registry (active).
Recent checks of SecFeed: SEC EDGAR filings
CheckedResultHandshake
15 minutes agoHandshake completed293 ms
9 days agoHandshake completed293 ms
9 days agoHandshake completed296 ms
11 days agoHandshake completed289 ms
12 days agoHandshake completed330 ms
13 days agoHandshake completed291 ms
14 days agoHandshake completed292 ms
14 days agoHandshake completed356 ms
16 days agoHandshake completed294 ms
19 days agoHandshake completed323 ms
21 days agoHandshake completed478 ms
24 days agoHandshake completed301 ms
26 days agoHandshake completed299 ms
28 days agoCredentials required—

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

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 SecFeed: SEC EDGAR filings and makes no claim about it beyond what these checks measured.