Skip to content
Misata Studio logo

Misata Studio MCP server

Which MCP servers are Misata Studio's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-15

← Back to Misata Studio

Whose server it is
  • Registry namestudio.misata/misataverified in the MCP registry

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

When we asked itchecked 2026-10-15
  • Stateanswerschecked 2026-10-15
  • Tools12
  • Server calls itselfMisata
  • Server version1.30.0
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet

    Once connected

    • Asks for a sign-in.

    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.

    Measured dailydaily checks: 15, the first on 2026-10-19
    • INITE MCP scoreafter a weeka score needs 7 daily checks: 15 so far
    • Answered73% of days11 of 15 daily checks
    • Median first answer242 ms

    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 (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). 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 →

    Tools it offers12 tools · read 2026-10-15
    • whoami

      Which account this connection is, and what it may do: signed in with a Studio MCP key or anonymous, the row cap, and whether a model key is available for plain-English requests.

    • plan_dataset

      See the tables, sizes and relationships the engine would build, before any rows exist. Free (no rows are made), so it is worth calling before generate_dataset on anything non-trivial: review what it understood and assumed, then adjust…

    • blueprint_guide

      The reference for the engine's full design language (the `blueprint` argument of generate_dataset, start_generation and validate_blueprint): roles, distributions, formulas that read parent columns and draw noise, per-group sequences (seq…

    • validate_blueprint

      Check a blueprint before generating it: every error said as what to change, the design traps it falls into (a column that will round away, a copy of a value not made yet, a window that counts nothing), its size against your row cap, and a…

    • generate_dataset

      Make a verified relational dataset and wait for it: every foreign key checked, dates correctly ordered, declared aggregates and rates exact, before anything is returned. Deterministic for a seed. Use this when you give a `schema` or `ddl`…

    • start_generation

      Start a generation in the background and return a job_id at once. Use it for any plain-English `request` (a model designs the tables, which takes minutes) — then call get_status(job_id) every 20-30 seconds until it says done. Arguments…

    • get_status

      Where a start_generation job is. While running: the stage it is in and how long it has run. When done: the same answer generate_dataset returns (dataset_id, verification, tables, certificate).

    • cancel_generation

      Stop a running start_generation job. It stops at the next stage boundary and keeps nothing.

    • get_certificate

      The full certificate for a dataset made by generate_dataset: every claim (stated vs actual), every requirement's status and evidence, realism findings, planted defects/anomalies if any, and the pattern charts. This is the whole answer…

    • query_dataset

      Read-only SQL over a dataset's own tables (one SELECT/WITH statement; every table name is a view over that dataset's own files — nothing else on the server is reachable this way). Args: dataset_id: from a prior generate_dataset call. sql…

    • export_dataset

      Export a generated dataset as a file. Returns a `download_url` the person can open (or you can fetch, e.g. with curl) for as long as the dataset is held, about 2 hours. Give the person the link rather than pasting file contents into the…

    • find_ready_dataset

      The ready-made datasets Misata publishes: free sample databases (direct download, public domain) and premium datasets with a full answer key (a free preview, then a one-off price). Check this first when someone wants sample, demo…

    How to connect

    Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

    {
      "mcpServers": {
        "misata": {
          "type": "http",
          "url": "https://api.misata.studio/mcp"
        }
      }
    }

    Add it

    Claude Code, in a terminal

    claude mcp add --transport http misata https://api.misata.studio/mcp

    Add to CursorAdd to VS Code

    claude.ai, ChatGPT and other clients: add https://api.misata.studio/mcp as a custom connector in the settings.

    Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.