Remote MCP · Endpoint

Sec Events MCP server

No. Sec Events answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/sec-events/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/sec-events
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
53 ms
Tools exposed
40 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
SEC 8-K event triage — query pre-classified 8-K filings from the last
Listing
From the official MCP registry (active).
Recent checks of Sec Events
CheckedResultHandshake
1 day agoHandshake completed53 ms
3 days agoHandshake completed74 ms
5 days agoHandshake completed54 ms
7 days agoHandshake completed72 ms
8 days agoHandshake completed95 ms
9 days agoHandshake completed56 ms
12 days agoHandshake completed41 ms
13 days agoHandshake completed41 ms
15 days agoHandshake completed58 ms
17 days agoHandshake completed41 ms
18 days agoHandshake completed53 ms
19 days agoHandshake completed45 ms
20 days agoHandshake completed103 ms
20 days agoHandshake completed37 ms
21 days agoHandshake completed51 ms
23 days agoHandshake completed59 ms

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

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