Remote MCP · Endpoint

Data APIs SEC Event Intelligence API MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://api.data-apis.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.data-apis.api/sec-event-intelligence
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
17.6% from 17 checks
Described by its publisher as
Data APIs SEC Event Intelligence API for SEC API/EDGAR filings, OpenAPI, MCP, A2A at data-apis.com.
Website
https://api.data-apis.com/mcp
Listing
From the official MCP registry (active).
Recent checks of Data APIs SEC Event Intelligence API
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
20 days agoHandshake completed342 ms
21 days agoHandshake completed125 ms
22 days agoHandshake completed142 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Data APIs SEC Event Intelligence API and makes no claim about it beyond what these checks measured.