Remote MCP · Endpoint
beatandraise.com SEC Filings MCP server
No. beatandraise.com SEC Filings answered an MCP handshake 1 day ago.
UpLast checked 1 day ago
Server URL
https://beatandraise.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.beatandraise/sec-filings
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 166 ms
- Tools exposed
- 29 tools
- Uptime, last 30 days
- 100% from 10 checks
- Described by its publisher as
- SEC EDGAR since 1993: search and read filings, insiders, 13F, statements; verify quotes and figures.
- Website
- https://beatandraise.com/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 day ago | Handshake completed | 166 ms |
| 5 days ago | Handshake completed | 150 ms |
| 16 days ago | Handshake completed | 191 ms |
| 16 days ago | Handshake completed | 216 ms |
| 17 days ago | Handshake completed | 161 ms |
| 19 days ago | Handshake completed | 141 ms |
| 20 days ago | Handshake completed | 148 ms |
| 21 days ago | Handshake completed | 152 ms |
| 22 days ago | Handshake completed | 153 ms |
| 23 days ago | Handshake completed | 151 ms |
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 beatandraise.com SEC Filings and makes no claim about it beyond what these checks measured.