_ registry / mcp streamable-http · checked 29m ago

metamodel

https://metamodel.app

Registry code: 50ee799079b95999

api record

MetaModel provides certified formula computation — published calculators and engineering models with real dependency-tracked formulas, so answers are computed, not hallucinated. Flow: metamodel_list_projects to browse, metamodel_get_schema to discover a project's inputs/outputs, metamodel_compute to run it.

endpoint
https://www.metamodel.app/api/mcp
door code
12798ff0b3d0cc6a
protocol
streamable-http ·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 metamodel live?
Yes — it answered the hub's last check (checked 29m ago). It answered 100% of checks over the last 30 days.
Is metamodel free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does metamodel have?
4 tools: metamodel_export_kn, metamodel_compute, metamodel_list_projects, metamodel_get_schema.
Is metamodel 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
99.7%

90 days 99.8%· all time 99.6%

latency
229ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 646 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • unknown → live
_ what it is for
used for
  • browse published engineering calculators
  • get calculator input schema
  • compute outputs from formula models
takes → gives
data → data
tools
4 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 4 tools
1 open1 auth-required 2 never probed 2 of 4 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.

  • metamodel_list_projects reads open 2h ago

    Browse available MetaModel calculators and engineering models. Returns project names, descriptions, tokens, and model names for each published project.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • metamodel_get_schema reads auth-required 2h ago

    Get the input/output schema for a published MetaModel project. Returns model names, input parameters (with types, defaults, validation), and output fields. Models marked "presentation": true are display scaffolding (3D scenes etc.) — skip them for engineering analysis. Use a token from metamodel_list_projects.

    mcp-tool

    {
      "type": "object",
      "required": [
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "The publish token of the project (from metamodel_list_projects)"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • metamodel_export_kn reads unknown never probed

    Export a published MetaModel project as KN notation — a human-readable text spelling of the model: nested Component blocks, "Name: value" literals, "Name: expression" formulas, dotted cross-references. Deliberately lossy (rules, indicators, validations, table data and views are omitted). Useful for reading or diffing the engineering knowledge behind a project.

    mcp-tool

    {
      "type": "object",
      "required": [
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "The publish token of the project (from metamodel_list_projects)"
        }
      }
    }
    arguments 12 lines
  • metamodel_compute reads unknown never probed

    Run a computation on a MetaModel project. Send input values and get computed outputs from all models. Inputs are auto-routed to the correct model by property name. Models marked "presentation": true in results are display scaffolding, not engineering outputs. Use metamodel_get_schema first to discover available inputs and outputs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "token"
      ],
      "properties": {
        "model": {
          "type": "string",
          "description": "Target a specific model by name. When omitted, returns outputs from ALL models (recommended)."
        },
        "token": {
          "type": "string",
          "description": "The publish token of the project"
        },
        "inputs": {
          "type": "object",
          "description": "Input values as key-value pairs (e.g., {\"width\": 12}). Auto-routed to the correct model. Omitted inputs use defaults.",
          "additionalProperties": true
        }
      },
      "additionalProperties": false
    }
    arguments 22 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 50ee799079b95999.

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

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.