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

com.logiccommons/calculators

https://mcp.logiccommons.com

Registry code: 08852d8691ca6369

api record

Find and run trustworthy calculators with clear methods, provenance, and sources.

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

endpoint
https://mcp.logiccommons.com/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 com.logiccommons/calculators live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is com.logiccommons/calculators free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.logiccommons/calculators have?
3 tools: get_calculator_schema, search_calculators, run_calculator.
Is com.logiccommons/calculators 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
98.4%

90 days 98.4%· all time 98.4%

latency
336ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 123 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • search a catalog of calculators
  • get a calculator input schema
  • run a calculator with inputs
takes → gives
text, data → data
tools
3 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • get_calculator_schema reads unknown 23h ago

    Get the input and output schema for a calculator, generated from its reviewed contract: parameter types, units, allowed dropdown values and definitional bounds, plus outputs keyed by named range (including the status output). Table inputs carry a 'grid' block giving the exact number of rows to send, the column layout, which columns are editable, and how to shape a row; a table whose 'grid' block says writable=false cannot be supplied at all. Schema 0.18 exposes required and omitted declarations plus version-bound visibility tables; older versions require every input while awaiting metadata migration. Optionally resolves one immutable platform version. Returns trust metadata for the resolved version.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The calculator slug, e.g. 'steel-column-capacity-calculator'."
        },
        "platform_version": {
          "type": [
            "integer",
            "null"
          ],
          "default": null,
          "description": "Optional positive platform version number. Omit for the current published version."
        }
      }
    }
    arguments 20 lines
  • search_calculators reads unknown 23h ago

    Search the LogicCommons calculator catalog by keyword and optional category. Returns matching published calculators with slug, name, summary, category, a citation URL, and trust metadata.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Free-text query matched against calculator name, summary and category. Empty returns the catalog."
        },
        "category": {
          "type": [
            "string",
            "null"
          ],
          "default": null,
          "description": "Optional category slug to filter by, e.g. 'structural-civil'."
        }
      }
    }
    arguments 20 lines
  • run_calculator reads unknown never probed

    Run a calculator with the given inputs. Inputs are validated against the resolved version's reviewed contract and computed by SpreadsheetWeb through the same proxy as the web channel. An optional platform_version pins both validation and computation to that immutable version. Returns outputs keyed by named range (including the status output) and trust metadata with a citation URL, resolvedInputs, and warnings for omitted inputs. Missing or blank visible required inputs are refused before computation; inspect get_calculator_schema and the complete error detail. For schema 0.18, optional omissions are sent explicitly as declared blank or standing default and disclosed with their values and sources. Older pinned contracts require all inputs during migration. Visibility follows version-bound dropdown truth tables; a missing controller makes its dependents indeterminate until it is supplied. A hidden controller is ignored only when all of its option branches have the same remaining visibility subtree; otherwise its dependents stay hidden. Hidden omissions use explicit blank/default values; supplied hidden inputs are retained with a not-applicable warning. Always read Model_Status and status outputs; CHECK and STOP are load-bearing verdicts about the result's validity. Results are informational and not professional advice; the applicable notice is returned in the trust block.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug",
        "inputs"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The calculator slug."
        },
        "inputs": {
          "type": "object",
          "description": "Input name/value pairs matching the calculator schema (from get_calculator_schema). A table input takes a list of rows matching its 'grid' block exactly; a table of the wrong extent or shape is refused rather than partially applied."
        },
        "platform_version": {
          "type": [
            "integer",
            "null"
          ],
          "default": null,
          "description": "Optional positive platform version number. Omit for the current published version."
        }
      }
    }
    arguments 25 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 08852d8691ca6369.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/08852d8691ca6369/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/08852d8691ca6369/badge.svg)](https://brick.blue/agent/08852d8691ca6369?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
70%

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.