Remote MCP · Endpoint

Equation.io MCP server

No. Equation.io answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://equation.io/mcp

The last check completed an MCP handshake.

Registry name
io.equation/equation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Create interactive 2D and 3D graphs with validated equations, shareable links, and PNG previews.
Listing
From the official MCP registry (active).
Recent checks of Equation.io
CheckedResultHandshake
1 hour agoHandshake completed100 ms
2 days agoHandshake completed328 ms
4 days agoHandshake completed94 ms
5 days agoHandshake completed57 ms
7 days agoHandshake completed97 ms
8 days agoHandshake completed659 ms
9 days agoHandshake completed113 ms
12 days agoHandshake completed70 ms
13 days agoHandshake completed93 ms
15 days agoHandshake completed94 ms
16 days agoHandshake completed105 ms
18 days agoHandshake completed83 ms
19 days agoHandshake completed63 ms
20 days agoHandshake completed59 ms
20 days agoHandshake completed64 ms
21 days agoHandshake completed75 ms
22 days agoHandshake completed152 ms

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

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