Remote MCP · Endpoint
Arche: SEC EDGAR Fundamentals MCP Server and API MCP server
No. Arche: SEC EDGAR Fundamentals MCP Server and API answered an MCP handshake 20 hours ago.
UpLast checked 20 hours ago
Server URL
https://api.arche.fi/mcp
The last check completed an MCP handshake.
- Registry name
- fi.arche/arche
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 31 ms
- Tools exposed
- 67 tools
- Uptime, last 30 days
- 100% from 10 checks
- Described by its publisher as
- SEC EDGAR fundamentals: filings, XBRL facts and normalized statements, point-in-time by acceptance.
- Website
- https://arche.fi/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 20 hours ago | Handshake completed | 31 ms |
| 4 days ago | Credentials required | — |
| 8 days ago | Credentials required | — |
| 17 days ago | Credentials required | — |
| 17 days ago | Credentials required | — |
| 19 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 21 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
The last 10 checks. Full history is kept for 30 days; the all-time counter stands at 10 responding of 10.
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 Arche: SEC EDGAR Fundamentals MCP Server and API and makes no claim about it beyond what these checks measured.