Remote MCP · Endpoint
FilingDesk Data MCP server
No. FilingDesk Data answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://filingdesk.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.filingdesk/data
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 142 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- US LLC filing fees, annual-report deadlines and naming-rule checks, from official state sources.
- Website
- https://filingdesk.com/mcp/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 142 ms |
| 18 hours ago | Handshake completed | 348 ms |
| 2 days ago | Handshake completed | 149 ms |
| 3 days ago | Handshake completed | 120 ms |
| 4 days ago | Handshake completed | 328 ms |
| 5 days ago | Handshake completed | 336 ms |
| 6 days ago | Handshake completed | 127 ms |
| 7 days ago | Handshake completed | 142 ms |
| 10 days ago | Handshake completed | 187 ms |
| 13 days ago | Handshake completed | 309 ms |
| 15 days ago | Handshake completed | 469 ms |
| 17 days ago | Handshake completed | 152 ms |
| 19 days ago | Handshake completed | 254 ms |
| 21 days ago | Handshake completed | 300 ms |
| 23 days ago | Handshake completed | 743 ms |
| 25 days ago | Handshake completed | 174 ms |
| 27 days ago | Handshake completed | 319 ms |
| 28 days ago | Handshake completed | 167 ms |
| 29 days ago | Handshake completed | 157 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 FilingDesk Data and makes no claim about it beyond what these checks measured.