Skip to content

uniwire MCP server

io.github.uniwire-dev/uniwireuniwire-devstreamable-httpv0.1.9Scanned

Electrical single-line and multi-line diagrams: build, check (NF C 15-100, IEC 60364), draw, PDF.

14 tools: 8 change things and 6 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

8 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 uniwire MCP server can do

The uniwire MCP server is published by the GitHub account uniwire-dev. It has 14 tools. It can create or change data (8 tools: type_info, validate, check, apply_patch and 4 more), but cannot delete data. 6 tools only read.

3 tools read private data (get_reference_card, get_example and normalize); 5 tools bring in text other people can write (validate, check, apply_patch and 2 more).

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, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.1.9.

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.

14 tools

Changes things 8Claude Code: ask
  • apply_patchEdit an electrical diagram by node id (change a rating, add a circuit, move a load...) and return the new document.Reads text others writeNo findings

    Why it is in this group

    • The name "apply_patch" says "apply": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Edit an electrical diagram by node id (change a rating, add a circuit, move a load...) and return the new document. ops (applied in order): {"op":"set","id":ID,"path":"in_A","value":20} (null value removes; no id = document root, e.g. path "installation.earthing"); {"op":"add","parent":ID,"node":{...},"index":0} (or "at":"sources"); {"op":"remove","id":ID}; {"op":"move","id":ID,"parent":ID,"index":0}; {"op":"rename","id":ID,"new_id":NEW}; {"op":"link","link":{"kind":"control","from":ID,"to":ID}}; {"op":"unlink","id":LINK_ID} or {"op":"unlink","from":ID,"to":ID,"kind":K}. On failure returns ok=false and errors naming the failing op index (null = validation of the result).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
    • title: Edit an electrical diagram
  • bomCompute the bill of materials (nomenclature) of an electrical installation from its document: one row per manufacturer / part number for the nodes with a product reference, then on…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Compute the bill of materials (nomenclature) of an electrical installation from its document: one row per manufacturer / part number for the nodes with a product reference, then one row per kind of equipment without a reference (type and main characteristics in 'spec', e.g. 'C16 1P+N') and per kind of cable (total length in 'length_m'), with quantities and the reference designations involved. Use it to prepare a quote or an order; wiring gives the wire list and cable schedule.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Bill of materials
  • checkCheck an electrical installation (single-line diagram, panel, schéma unifilaire, tableau électrique): validates the document, then applies the rule profiles (NF C 15-100 'nfc15100'…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check an electrical installation (single-line diagram, panel, schéma unifilaire, tableau électrique): validates the document, then applies the rule profiles (NF C 15-100 'nfc15100', French grid connection 'enedis', IEC 60364 'iec60364', PLC; default: the document's 'profiles'; 'core' always applies): breaker ratings against cable sections, RCDs, circuits per protection, selectivity... Returns findings (level error/warning/info, rule, node id, message, source), a summary, 'scope' (what the checks cover and do not cover: automatic checks of the document data, not a conformity certificate), viewer_url (the document in the uniwire web editor: drawing, findings, downloads) and pdf_url (the PDF drawn by uniwire).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
    • title: Check an electrical installation (NF C 15-100, IEC 60364)
  • renderDraw the electrical diagram (schéma unifilaire / multifilaire).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Draw the electrical diagram (schéma unifilaire / multifilaire). kind: 'single-line' or 'multi-line'; view: a view id of the document (e.g. a wire-marking view). format 'svg' returns the SVG text of every sheet (or of 'sheet', numbered from 1); 'pdf' writes to 'path' if given, else returns base64 (requires the uniwire[pdf] extra); on the hosted server it returns pdf_url (the PDF drawn by uniwire) instead. color: 'none' | 'conductors' | 'phase' | 'source' | 'status' | 'voltage' (adds a legend); conductor_colors: 'iec' (IEC 60445) | 'us'.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
    • title: Draw the single-line or multi-line diagram
  • type_infoReturn every field of one node type with its description, unit and allowed values (enums).1 finding

    Why it is in this group

    • The name "type_info" says "type": 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 "type_info" 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 "type_info" says "type": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Return every field of one node type with its description, unit and allowed values (enums). Use it before writing or editing a node of that type; list_types gives the type names.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Fields of a node type
  • validateValidate a uniwire document (electrical diagram as JSON) against the format only: structure, types, ids, references and links, without the electrical rules (use check for those).Reads text others write1 finding

    Why it is in this group

    • The name "validate" says "validate": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "validate" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    Validate a uniwire document (electrical diagram as JSON) against the format only: structure, types, ids, references and links, without the electrical rules (use check for those). Returns valid + issues, each naming the node id and field when possible, plus viewer_url (the document in the uniwire web editor) and pdf_url (the PDF drawn by uniwire).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
    • title: Validate an electrical diagram
  • wiringWiring exports of an installation as rows with stable column names (repérage des fils, carnet de câbles, liste d'E/S, borniers): what='markers' (one row per wire end, for label pri…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Wiring exports of an installation as rows with stable column names (repérage des fils, carnet de câbles, liste d'E/S, borniers): what='markers' (one row per wire end, for label printers), 'wires' (wire list), 'cables' (cable schedule), 'io' (one row per PLC channel, connected or spare, with the device linked to it) or 'terminals' (one row per terminal of each terminal block). Marks follow the wire_marking rules of the view (id), by default the first view that declares them.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Wire list, wire markers and cable schedule
Only reads 6Show 6 read-only tools
  • describeReturn a text outline of an electrical diagram: installation, full tree of the panel with stable ids, ratings and cables, links, interlocks, boards and findings summary.No findings

    Why it is in this group

    • The name "describe" says "describe": a word for reading.
    Description, as the server wrote it
    Return a text outline of an electrical diagram: installation, full tree of the panel with stable ids, ratings and cables, links, interlocks, boards and findings summary. Use it to read a document and find the node ids before apply_patch.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Outline of an electrical diagram
  • get_exampleReturn an example installation document by name.Reads private dataNo findings

    Why it is in this group

    • The name "get_example" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "document": it reads documents.
    Description, as the server wrote it
    Return an example installation document by name. Use it as a starting point for a similar installation, then edit it with apply_patch; list_examples gives the names.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Get an example installation
  • get_reference_cardReturn the reference card of the uniwire format for electrical diagrams: document skeleton, node types (breakers, RCDs, cables, loads, transformers, PV...) and their fields, enums,…Reads private dataNo findings

    Why it is in this group

    • The name "get_reference_card" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "document": it reads documents.
    Description, as the server wrote it
    Return the reference card of the uniwire format for electrical diagrams: document skeleton, node types (breakers, RCDs, cables, loads, transformers, PV...) and their fields, enums, links, pitfalls, examples. Read it once before writing a document; type_info gives the fields of one type in detail.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Reference card of the uniwire format
  • list_examplesList the 53 example installations (dwellings, shops, offices, workshops, PV, EV charging, UPS, MV/LV substations, PLCs): name, title, language, profiles, earthing, system.No findings

    Why it is in this group

    • The name "list_examples" says "list": a word for reading.
    Description, as the server wrote it
    List the 53 example installations (dwellings, shops, offices, workshops, PV, EV charging, UPS, MV/LV substations, PLCs): name, title, language, profiles, earthing, system.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List the example installations
  • list_typesList the node types of the format (type, category, label), optionally for one category.No findings

    Why it is in this group

    • The name "list_types" says "list": a word for reading.
    Description, as the server wrote it
    List the node types of the format (type, category, label), optionally for one category. Use it to find the type name of a device or load before writing a node; type_info then gives its fields.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List the node types
  • normalizeReturn the resolved form of a document: templates ('use') applied, every node and link id assigned, numbers in canonical form.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "document": it reads documents.
    Description, as the server wrote it
    Return the resolved form of a document: templates ('use') applied, every node and link id assigned, numbers in canonical form. Use it to read a document exactly as the rules and drawings see it, or to get stable ids before apply_patch; it does not apply the electrical rules (see check).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Normalized document

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 outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
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 20, 2026, 19:12 UTC, unchanged since Oct 29, 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
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

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

    Matched text

    https://mcp.uniwire.sh/mcp: tools/list returned 14 tools to an anonymous client, including type_info (write), validate (write), check (write), apply_patch (write), render (write) and 3 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 9 to 8

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "type_info" 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 "type_info" says "type": a word for a change.

    What this check looks for
  • The server marks "validate" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

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

    What this check looks for

History

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

  1. Tools1 changed.~1 changedView diff
    • Changed:wiringChanges thingsdescriptioninputSchema
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 8.View diff
    • Tools that change things, listed without credentials: 9 to 8
  3. Tools14 changed.~14 changedView diff
    • Changed:apply_patchChanges thingsinputSchema
    • Changed:bomChanges thingsdescriptioninputSchema
    • Changed:checkChanges thingsdescriptioninputSchema
    • Changed:describeOnly readsdescriptioninputSchema
    • Changed:get_exampleOnly readsdescriptioninputSchema
    • Changed:get_reference_cardOnly readsdescriptioninputSchema
    • Changed:list_examplesOnly readsdescription
    • Changed:list_typesOnly readsdescriptioninputSchema
    • Changed:normalizeOnly readsdescriptioninputSchema
    • Changed:renderChanges thingsdescriptioninputSchema
    • Changed:type_infoChanges thingsdescriptioninputSchema
    • Changed:validateChanges thingsdescriptioninputSchema
    • Changed:viewer_linkChanges thingsdescriptioninputSchema
    • Changed:wiringChanges thingsinputSchema

Install

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

claude mcp add --transport http uniwire https://mcp.uniwire.sh/mcp
claude mcp add --transport http uniwire https://mcp.uniwire.sh/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__uniwire__get_reference_card",
      "mcp__uniwire__list_types",
      "mcp__uniwire__describe",
      "mcp__uniwire__list_examples",
      "mcp__uniwire__get_example",
      "mcp__uniwire__normalize"
    ],
    "ask": [
      "mcp__uniwire__type_info",
      "mcp__uniwire__validate",
      "mcp__uniwire__check",
      "mcp__uniwire__apply_patch",
      "mcp__uniwire__render",
      "mcp__uniwire__viewer_link",
      "mcp__uniwire__wiring",
      "mcp__uniwire__bom"
    ],
    "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 uniwire. Review it before you use it.

Capability tags behind 8 rules
  • mcp__uniwire__get_reference_card private-data
  • mcp__uniwire__validate untrusted-input
  • mcp__uniwire__check untrusted-input
  • mcp__uniwire__apply_patch untrusted-input
  • mcp__uniwire__render untrusted-input
  • mcp__uniwire__viewer_link untrusted-input
  • mcp__uniwire__get_example private-data
  • mcp__uniwire__normalize private-data

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/io.github.uniwire-dev/uniwire/verify?hash=56a556dcd35fec85f680db1fe33e735d8362874a04879ff7b690451d9a662e36" | jq -e '.changed == false'

Pinned hash 56a556dcd35f, from Nov 21, 2026, 23:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.uniwire-dev/uniwire/changes.xml

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

Badge

Anlyon Radar badge for io.github.uniwire-dev/uniwire
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.uniwire-dev/uniwire.svg)](https://radar.anlyon.com/servers/io.github.uniwire-dev/uniwire)

Source: MCP Registry · repository. Synced Nov 21, 2026, 23:17 UTC.

uniwire MCP server: questions and answers

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

Is the uniwire MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 8 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 uniwire MCP server delete data?

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

Can the uniwire 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 uniwire MCP server have?

14 tools: 8 write, 6 read. type_info, validate, check, apply_patch, render, viewer_link, wiring, bom and 6 more.

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

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

Does the uniwire MCP server send data to outside services?

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

Has the uniwire MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.