_ registry / mcp streamable-http · checked 3h ago

mokxi

https://mokxi.com

Registry code: ad1266a444b42cd9

api record

Mokxi is an electronics and microcontroller simulator that runs in the browser. Build a project for the person in the Mokxi AI project format: get_project_format explains it with an example. Start from get_example for the board or part in question, or find parts with search_parts and their pins with get_part; never write a pin name from memory. Check the project with validate_project and fix every error it names, then call create_project. Always give the person the link it returns, whole and unchanged, as a link they can click: it opens the project in the Mokxi editor and runs it, with no…

endpoint
https://mokxi.com/mcp
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 mokxi live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is mokxi free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does mokxi have?
8 tools: search_parts, validate_project, get_part, get_example, get_project_format, list_boards, create_project, create_code_link.
Is mokxi 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
303ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 8 tools
8 auth-required 8 of 8 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.

  • search_parts auth-required never probed

    Find Mokxi parts by what they are ("temperature sensor", "oled", "motor driver"). Returns each part's type, pins and settings, from the simulator's own catalog.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "description": "How many to return, 1 to 30. 10 by default."
    },
    "query": {
      "type": "string",
      "description": "A few words: what the part is or does, or its chip name."
    }
  }
}
    arguments 16 lines
  • validate_project auth-required never probed

    Check a project the way the Mokxi editor does: every unknown part, wrong pin, bad setting and code problem, in plain words naming the part and pin. Fix every error, then call create_project.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project"
  ],
  "properties": {
    "project": {
      "type": "object",
      "required": [
        "board"
      ],
      "properties": {
        "code": {
          "type": "object",
          "description": "File name to its text: {\"sketch.ino\": \"...\"} or {\"main.py\": \"...\"}."
        },
        "name": {
          "type": "string"
        },
        "board": {
          "type": [
            "string",
            "null"
          ],
          "description": "A board type from list_boards, such as \"uno\", \"esp32\" or \"pico\"; null for a circuit with no board."
        },
        "parts": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "id",
              "type"
            ],
            "properties": {
              "id": {
                "type": "string"
              },
              "type": {
                "type": "string"
              },
              "props": {
                "type": "object"
              }
            }
          }
        },
        "wires": {
          "type": "array",
          "items": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "maxItems": 3,
            "minItems": 2
          },
          "description": "Pairs of ends, \"partId.pin\"; the board is \"board\". A third item may name a color."
        },
        "format": {
          "type": "string",
          "const": "mokxi-ai/1"
        }
      },
      "description": "A project in the Mokxi AI format: {\"format\": \"mokxi-ai/1\", \"name\": \"...\", \"board\": \"uno\", \"parts\": [{\"id\": \"led1\", \"type\": \"led\"}], \"wires\": [[\"board.13\", \"led1.A\"]], \"code\": {\"sketch.ino\": \"...\"}}. get_project_format has the full rules."
    }
  }
}
    arguments 68 lines
  • get_part auth-required never probed

    One part in full: its pins with their directions, its settings with ranges and units, and how a Mokxi template wires it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "type"
  ],
  "properties": {
    "type": {
      "type": "string",
      "description": "The part type, such as \"led\" or \"hcsr04\"."
    }
  }
}
    arguments 12 lines
  • get_example auth-required 3h ago

    A complete, working starter for a board, a part or both: a real Mokxi template as a project with its wiring and code, ready for create_project. Change it to what the person asked for instead of writing pins from memory. With no arguments, the smallest whole project.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "part": {
      "type": "string",
      "description": "A part type from search_parts, such as \"servo\" or \"hcsr04\"."
    },
    "board": {
      "type": "string",
      "description": "A board type from list_boards, such as \"uno\" or \"esp32\"."
    }
  }
}
    arguments 13 lines
  • get_project_format auth-required 3h ago

    How to write a Mokxi project (board, parts, wires as "partId.pin" pairs, code), with the rules, the common parts and boards with their pins, and a complete example. Read this first.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_boards auth-required 3h ago

    Every microcontroller board Mokxi runs, with its type for the "board" field, the code it takes and its pin names.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • create_project auth-required never probed

    Make the link that opens the project in the Mokxi editor and runs it: the board, its code, and the parts and wires when there are any. Nothing is stored and no account is needed: the link carries the whole project. Refused, with the errors, while validate_project finds any. Always give the person the link, whole and unchanged.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project"
  ],
  "properties": {
    "project": {
      "type": "object",
      "required": [
        "board"
      ],
      "properties": {
        "code": {
          "type": "object",
          "description": "File name to its text: {\"sketch.ino\": \"...\"} or {\"main.py\": \"...\"}."
        },
        "name": {
          "type": "string"
        },
        "board": {
          "type": [
            "string",
            "null"
          ],
          "description": "A board type from list_boards, such as \"uno\", \"esp32\" or \"pico\"; null for a circuit with no board."
        },
        "parts": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "id",
              "type"
            ],
            "properties": {
              "id": {
                "type": "string"
              },
              "type": {
                "type": "string"
              },
              "props": {
                "type": "object"
              }
            }
          }
        },
        "wires": {
          "type": "array",
          "items": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "maxItems": 3,
            "minItems": 2
          },
          "description": "Pairs of ends, \"partId.pin\"; the board is \"board\". A third item may name a color."
        },
        "format": {
          "type": "string",
          "const": "mokxi-ai/1"
        }
      },
      "description": "A project in the Mokxi AI format: {\"format\": \"mokxi-ai/1\", \"name\": \"...\", \"board\": \"uno\", \"parts\": [{\"id\": \"led1\", \"type\": \"led\"}], \"wires\": [[\"board.13\", \"led1.A\"]], \"code\": {\"sketch.ino\": \"...\"}}. get_project_format has the full rules."
    }
  }
}
    arguments 68 lines
  • create_code_link auth-required never probed

    Make a link that opens a sketch in the Mokxi editor, for code with no circuit worked out: Mokxi reads the sketch, picks the board when none is given and places and wires the parts the code names. Nothing is checked here, so prefer create_project when the wiring matters. Always give the person the link, whole and unchanged.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The whole sketch, 24 thousand characters at most."
    },
    "board": {
      "type": "string",
      "description": "The board to open it on, such as \"uno\", \"esp32\" or \"pico\". Left out, Mokxi picks one from the code."
    }
  }
}
    arguments 16 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 ad1266a444b42cd9.

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

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.