Skip to content

Mokxi MCP server

com.mokxi/mcpmokxi.comstreamable-httpv1.0.0Scanned

Build, check and open Arduino, ESP32 and Pico circuits with code in the Mokxi simulator.

8 tools: 2 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Mokxi MCP server can do

The Mokxi MCP server is published by mokxi.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (2 tools: create_project and create_code_link), but cannot delete data. 6 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 2Claude Code: ask
  • create_projectMake 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.1 finding

    Why it is in this group

    • The name "create_project" says "create": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "create_project" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_project" says "create": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • get_exampleA 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.No findings

    Why it is in this group

    • The name "get_example" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_partOne part in full: its pins with their directions, its settings with ranges and units, and how a Mokxi template wires it.No findings

    Why it is in this group

    • The name "get_part" says "get": a word for reading.
    Description, as the server wrote it
    One part in full: its pins with their directions, its settings with ranges and units, and how a Mokxi template wires it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_project_formatHow 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.No findings

    Why it is in this group

    • The name "get_project_format" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_boardsEvery microcontroller board Mokxi runs, with its type for the "board" field, the code it takes and its pin names.No findings

    Why it is in this group

    • The name "list_boards" says "list": a word for reading.
    Description, as the server wrote it
    Every microcontroller board Mokxi runs, with its type for the "board" field, the code it takes and its pin names.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_partsFind Mokxi parts by what they are ("temperature sensor", "oled", "motor driver").No findings

    Why it is in this group

    • The name "search_parts" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validate_projectCheck 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.No findings

    Why it is in this group

    • The name "validate_project" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:21 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mokxi.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mokxi.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mokxi.com/mcp: tools/list returned 8 tools to an anonymous client, including create_project (write), create_code_link (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "create_project" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_project" says "create": a word for a change.

    What this check looks for
  • The server marks "create_code_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_code_link" says "create": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http mokxi https://mokxi.com/mcp
claude mcp add --transport http mokxi https://mokxi.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mokxi__get_project_format",
      "mcp__mokxi__list_boards",
      "mcp__mokxi__search_parts",
      "mcp__mokxi__get_part",
      "mcp__mokxi__get_example",
      "mcp__mokxi__validate_project"
    ],
    "ask": [
      "mcp__mokxi__create_project",
      "mcp__mokxi__create_code_link"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mokxi. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.mokxi/mcp/verify?hash=fe5d621eafeed0ea45413eaf015fac3b38ea5da15ddceff36a8d28bc380b32fa" | jq -e '.changed == false'

Pinned hash fe5d621eafee, from Nov 10, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.mokxi/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.mokxi/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.mokxi/mcp.svg)](https://radar.anlyon.com/servers/com.mokxi/mcp)

Source: MCP Registry. Synced Nov 10, 2026, 20:17 UTC.

Mokxi MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Mokxi MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Mokxi MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Mokxi MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Mokxi MCP server have?

8 tools: 2 write, 6 read. create_project, create_code_link, get_project_format, list_boards, search_parts, get_part, get_example and validate_project.

Does the Mokxi MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Mokxi MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Mokxi MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.