Remote MCP · Endpoint

Figurewell MCP server

No. Figurewell answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://figurewell-api.cybermax-tools.workers.dev/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
dev.workers.cybermax-tools.cybermax/figurewell-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
166 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Point-in-time SEC financials API + MCP: XBRL as first reported, EDGAR times. 100 free/day.
Listing
From the official MCP registry (active).
Recent checks of Figurewell
CheckedResultHandshake
7 hours agoHandshake completed166 ms
12 hours agoHandshake completed91 ms
2 days agoHandshake completed187 ms
4 days agoHandshake completed365 ms
7 days agoHandshake completed275 ms
9 days agoHandshake completed111 ms
11 days agoHandshake completed108 ms
14 days agoHandshake completed130 ms
15 days agoHandshake completed193 ms
18 days agoHandshake completed129 ms
20 days agoHandshake completed175 ms
21 days agoHandshake completed109 ms
23 days agoHandshake completed128 ms

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

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