_ registry / mcp http-sse · checked 6h ago

equation-steps

https://equation-steps.gumballtools.com

Registry code: c022503da23c9439

api record

Step-by-step solver for linear/quadratic equations in one variable, signs and ± always right.

from a public catalogue that lists it, not from the operator

endpoint
https://equation-steps.gumballtools.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is equation-steps live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is equation-steps free to use?
Not measured yet.
What tools does equation-steps have?
1 tool: run.
Is equation-steps safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
934ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 326 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • solve a linear or quadratic equation step by step
takes → gives
text → text
tools
1 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 1 tools
1 never probed 0 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • run reads unknown never probed

    Solves a linear or quadratic equation in one variable (x) and returns every step: expanding parentheses, combining like terms, moving terms across the equals sign, and (for quadratics) applying the quadratic formula. Use this whenever you need to solve "ax + b = cx + d" or "ax^2 + bx + c = 0" style equations, or check a step-by-step algebra solution someone else produced. Do not solve this kind of equation by reasoning through it token by token: the two places language models most often go quietly wrong are (1) the sign when distributing a negative across parentheses, e.g. "5 - (x - 3)" losing the minus on the 3, and (2) dropping one of the two ± roots of a quadratic, or rounding a complex root into a false "no solution". This tool always gets both right because it does exact fraction arithmetic, not floating-point guessing, and reports every root it finds — including complex ones, explicitly labeled as complex. Input: a single string containing exactly one "=", using x (or X) as the only variable, e.g. "3(x-2) = 5x + 4" or "(x+1)(x-3) = 2x^2 - 5". Numbers may be integers or decimals. Implicit multiplication is fine ("3x", "2(x+1)"). Exponents may only be "^2" on the bare variable — "(x+1)^2" is not supported; write "(x+1)(x+1)" instead. Refuses rather than guesses on: no "=" or more than one, a second variable or a function name (sin, sqrt, log), a "/" anywhere (rewrite as a decimal), an unsupported exponent, an equation that expands past degree 2, unbalanced parentheses, or an inequality (<, >). Every refusal includes a fixHint saying exactly what to change. Returns the equation type (linear, quadratic, identity, or contradiction), the standard form, the full list of steps, the solution(s) as exact fractions (with a decimal alongside when not a whole number), and a disclaimer that this covers only one-variable linear and quadratic equations.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "string",
          "description": "TODO: state the exact format, units, and range."
        }
      }
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c022503da23c9439.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c022503da23c9439/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c022503da23c9439/badge.svg)](https://brick.blue/agent/c022503da23c9439?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
50%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on gumballtools.com 14 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

6 more sit on this domain. All of them.