Zindex MCP server

• Registry nameai.zindex/zindexverified in the MCP registry

The registry name sits under zindex.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-20
• Tools9
• Server calls itselfzindex
• Server version6.9.2+build.2024
• Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 553 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer440 ms
• Space in an agent's context≈ 2,283 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsA · 91 of 100
• Typed results3 of 9 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 5 of 9

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• diagram_find

  Lists this workspace's diagrams, latest change first, with id, key, title and latest revision. query matches the title, key or brief, ignoring case.

• diagram_get

  Reads a diagram by id or key. The default outline: a header (id, title, revision, time, hash), the brief, recent versions, one element per line nested by container, and edges as 'id: from -> to'. view 'dsp' returns the scene JSON…

• diagram_validate

  Checks a DSP scene or Mermaid text without saving it. Returns ok, errors and warnings, each with a code, the element if any, and a one-line fix.

• diagram_create

  Saves a new diagram from a DSP scene or Mermaid text; returns its id, revision 1, content hash and chain hash. key is your stable name for it, unique in the workspace: your repeat with the same key and content returns the existing…

• diagram_edit

  Changes a saved diagram as a new revision; old ones stay. Give baseRevision (the revision you last read), a one-line message, and ops (typed operations, https://zindex.ai/schemas/ops.schema.json), mermaid (the whole diagram edited from…

• diagram_render

  SVG and PNG links to a saved diagram's version, not the image, with hashes and engine version. A published diagram's links are permanent, with url for its page; others last 7 days. preview adds a PNG for you. scene or mermaid instead of…

• diagram_history

  Lists a diagram's versions, newest first, with time, who made it (by), client, message, chain hash and counts of elements added, changed and removed. compare (from and to: revision numbers or dates) returns what changed between two…

• diagram_delete

  Deletes a diagram with all its versions. undo restores it within 24 hours; after that it is gone. Asks the user to confirm.

• diagram_share

  publish makes a diagram readable by anyone at its link; unpublish makes it private. link makes a share link showing its images, not its scene, to anyone who has it; unlink revokes them all. report sends one version to Zindex support…