Remote MCP · Endpoint

Sec Financial Statements MCP server

No. Sec Financial Statements answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://gateway.pipeworx.io/sec-financial-statements/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/sec-financial-statements
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
780 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
SEC Financial Statement & Notes data sets — dimensional facts + note text.
Listing
From the official MCP registry (active).
Recent checks of Sec Financial Statements
CheckedResultHandshake
8 hours agoHandshake completed780 ms
10 days agoHandshake completed62 ms
11 days agoHandshake completed79 ms
12 days agoHandshake completed106 ms
13 days agoHandshake completed80 ms
15 days agoHandshake completed62 ms
15 days agoHandshake completed66 ms
16 days agoHandshake completed172 ms
17 days agoHandshake completed173 ms
19 days agoHandshake completed776 ms
22 days agoHandshake completed1.18 s
24 days agoHandshake completed1.90 s
27 days agoHandshake completed1.30 s
29 days agoHandshake completed1.11 s

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

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