Misata Studio: verified synthetic data MCP server
studio.misata/misatamisata.studiostreamable-httpv1.0.0Scanned
Hosted: plan and build multi-table test and demo data, export 25 formats, with checks shown.
13 tools: 1 can delete or cancel things, 7 change things and 5 only read.
- Reads private data · 2
- Reads text others write · 3
- Can send data out · 0
- 5 findings
Sign-in required, OAuth metadata published. Remote posture
Anlyon alternative
8 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Misata Studio: verified synthetic data MCP server can do
The Misata Studio: verified synthetic data MCP server is published by misata.studio, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (1 tool: cancel_generation) and create or change data (7 tools: plan_dataset, blueprint_guide, generate_dataset, start_generation and 3 more). 5 tools only read.
2 tools read private data (query_dataset and find_ready_dataset); 3 tools bring in text other people can write (generate_dataset, start_generation and find_ready_dataset).
The fixed checks matched 5 findings (long-description, annotation-conflict and credentials-mention). Each one comes with the text it matched.
Last scanned Oct 21, 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.
13 tools
Deletes or cancels 1Claude Code: deny
cancel_generationStop a running start_generation job.1 finding
Why it is in this group
- The name "cancel_generation" says "cancel": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "cancel_generation" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "cancel_generation" says "cancel": a word for removing or ending something.
Description, as the server wrote it Stop a running start_generation job. It stops at the next stage boundary and keeps nothing.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Changes things 7Claude Code: ask
blueprint_guideThe reference for the engine's full design language (the `blueprint` argument of generate_dataset, start_generation and validate_blueprint): roles, distributions, formulas that rea…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 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, lag, cumsum, ar1 drift, random walk), aggregates, event windows, cause-and-effect, lifecycles, with patterns, and an index of chapters. Read it before writing a blueprint. Args: topic: a chapter's id from the index (or several, comma-separated) for that chapter in full, with a world that builds as written: JSON payloads (webhooks, audit trails), threads of messages, one party's duplicate records, running balances, rosters made from demand, a source system's raw drops and schema changes, planted problems for an eval. Empty for the reference.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_answersThe dataset's ground truth: every number it is held to, and the business's standard numbers (MRR, churn, billed revenue, win rate...), by month, worked out when it was made.1 finding
Why it is in this group
- The input takes a statement or command to run (input.sql), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_answers" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.sql), which can change anything it can reach.
Description, as the server wrote it The dataset's ground truth: every number it is held to, and the business's standard numbers (MRR, churn, billed revenue, win rate...), by month, worked out when it was made. Use it to test whatever answers questions about the data -- an agent, a dashboard, a cube, a text-to-SQL model -- and to say exactly why a wrong answer is wrong. Call it four ways: 1. dataset_id alone: the key's numbers (`kpis`: id, title, unit, months) and `questions` to ask, drawn from the key ("What is MRR at each month's end for 2025-07?"), each with an id. Their answers are not shown. 2. answers={question_id: number}: each answer graded within its tolerance; a wrong one is named as the usual misreading it equals (voided invoices counted, churn over every account), when it is one. 3. values with kpi: numbers computed anywhere (ClickHouse, a semantic layer, a BI tile), as one number, a {"2025-07": 123.4, ...} series by month, or [[month, value], ...]. Says whether they are that KPI (a tile is read as its latest month, the year to date, ...), and what they are instead when not. 4. sql (and kpi): a query over this dataset's own tables (DuckDB, as query_dataset), run here; a wrong one is told which KPI it computes, or the one change after which it returns the key. The values are plain numbers, so an answer from any engine is checked the same way; export_dataset(format="demo", dialect="clickhouse") hands over the same data and key to load into ClickHouse.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
export_datasetExport a generated dataset as a file.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...this server never holds a database credential itself. `demo` is t..."
Description, as the server wrote it 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 chat. Args: dataset_id: from a prior generate_dataset call. format: data: csv, parquet, jsonl, json, avro, xlsx, feather, orc, sqlite, duckdb, sql. code and docs: dbt, notebook, dictionary, dbml, mermaid, prisma, sqlalchemy, typescript, jsonschema, expectations, django, openapi, mockapi. `sql` is schema.sql (DDL with keys) + data.sql (COPY/INSERT) — the way to seed a real database: run the returned SQL through your own database connection, since this server never holds a database credential itself. `demo` is the handover for a demo or an eval: the database with a one-step loader, the ER diagram, answer_key.json (every number by month), questions.jsonl and the proof of each request. dialect: for `sql`: postgres, mysql, sqlite, mssql, oracle, bigquery, snowflake, clickhouse (MergeTree tables; above 500k rows, typed Parquet with load.sql). For `demo`: postgres (psql) or clickhouse (Parquet loaded with clickhouse-client). inline: also return the file itself as `base64` (only for files under a few MB). Use it when you must write the file yourself and cannot fetch a URL. Returns: filename, content_type, bytes, download_url, expires_at (unix seconds), and `base64` when `inline` and small enough.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
generate_datasetMake a verified relational dataset and wait for it: every foreign key checked, dates correctly ordered, declared aggregates and rates exact, before anything is returned.Reads text others write1 finding
Why it is in this group
- The name "generate_dataset" says "generate": 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.
Findings
- Info
The description is 4,141 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...rest (patterns, realism scorecard, every proof chart)."
Description, as the server wrote it 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` (seconds). For a plain-English `request` the engine designs the tables with a model, which can take several minutes: call start_generation instead and poll get_status, so the call does not sit open and time out. Args: request: Plain-English description (needs an LLM key unless `schema`/`ddl` is also given). With no key, design it yourself instead: blueprint_guide, then `blueprint` below. schema: A Misata schema dict for exact structural control. No key needed for structure. Its `numbers` (revenue by month, churn, MRR, shares, averages) are held exactly: see the server instructions. A column's `moves_with` ({"column": "customers.income", "strength": 0.6}) pairs it with another number of its row or its parent's, by rank, each keeping its own values. ddl: CREATE TABLE statements. No key needed for structure. Beside it, schema={"numbers": [...], "window": {...}} holds the story's numbers on these tables. seed: Reproducibility seed — the same request/schema and seed always produce the same rows. research: Ground realistic numbers (prices, growth rates) in real published facts via a web search. Off by default (an anonymous caller's request should not trigger external calls unless asked for); needs a key regardless of `schema`/`ddl`. blueprint: The engine's full design language (blueprint_guide has the reference): readings around a parent's nominal, drift, autocorrelation, cause-and-effect, event windows, exact aggregates. Use it whenever the data must behave like the real process. No key needed; run validate_blueprint on it first. story: A built-in shape held to exact numbers, the way Studio's plan screen states them. No key needed; built by code in seconds. {"pack": "saas_sales", "window": {"start": "2024-09", "end": "2026-08"}, "curves": [{"lever": "mrr_curve", "points": {"2024-09": 50000, "2026-08": 200000}}], "rates": [{"lever": "monthly_logo_churn", "value": 0.02, "events": [{"name": "Q3 churn spike", "start": "2025-07-01", "end": "2025-09-30", "multiplier": 2.5}]}]}. Shapes: saas_sales, ecommerce, fintech, healthcare. Every stated number is held exactly and read back in SQL; get_certificate has the answer key. `numbers` sets plain sizes and shares ({"customers": 3000, "products": 400, "return_rate": 0.06}). With no model key the shape's content is generic (ecommerce sells electronics, books, toys): write it yourself as `content`, e.g. {"catalog": [{"name": "Linen Duvet Cover", "category": "Bedding", "brand": "Fernhill", "price": 89.0}, ...]} (30-100 items in this business's own categories, at its real prices). Returns: dataset_id: pass this to get_certificate / query_dataset / export_dataset. passed: whether every check held. A dataset that did not pass is still returned, with `certificate.findings` saying what failed — inspect before trusting it. verification: a short, plain-language account of what was checked and what held — show it to the person as the proof, in place of asking them to take the data on trust. tables: {name: {columns, preview_rows (first 20), total_rows}} — the preview only; every row is in the stored dataset, reachable by query_dataset/export_dataset. certificate: the short form (claims, requirements, findings). get_certificate returns the rest (patterns, realism scorecard, every proof chart).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
plan_datasetSee the tables, sizes and relationships the engine would build, before any rows exist.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 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 your request or schema before spending a real call. Args: request: Plain-English description (needs an LLM key, unless `schema`/`ddl` is also given — then it is still used to ground realism, e.g. locale and what columns mean). schema: A Misata schema dict (see the server instructions for the format). No key needed for structure. ddl: CREATE TABLE statements. No key needed for structure. Returns: route: "chat" (not a dataset request — see `reply`), "design" (the model designed the tables) or "pack" (matched a built-in shape). tables: name, estimated rows, columns, foreign keys for each table the engine would build. understanding: what the engine read the request as (business, archetype, assumptions). requirements: every specific thing the request asked for, so you can see what was understood.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
query_datasetRead-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).Reads private data1 finding
Why it is in this group
- The name "query_dataset" says "query": a word for reading.
- The input takes a statement or command to run (input.sql), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe description's first sentence says "read" and "sql": it reads databases.
- private-dataThe name says "query" and the input takes a statement (input.sql): it reads databases.
Findings
- Warn
The server marks "query_dataset" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "query_dataset" says "query": a word for reading.
Description, as the server wrote it 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: a single SELECT (or WITH ... SELECT) statement. No semicolons, file paths, or statements that write or read outside the dataset (checked before running). limit: rows returned (capped at 5000). Returns: columns, rows, truncated (whether more rows existed than `limit`).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
start_generationStart a generation in the background and return a job_id at once.Reads text others writeNo findings
Why it is in this group
- The name "start_generation" says "start": 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 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 are the same as generate_dataset. Returns: job_id, status "running". get_status gives the stage and, when finished, the dataset.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 5Show 5 read-only tools
find_ready_datasetThe 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).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "find_ready_dataset" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "database": it reads databases.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, practice or teaching data for a common scenario (retail, e-commerce, SaaS, manufacturing SPC, predictive maintenance, insurance claims, fraud/AML, clinical, network security): handing over a dataset that already exists is instant. If none fits their tables, generate one instead. Args: query: what the person needs, in their words. Only orders the list (closest first); every dataset is still returned, so judge the fit yourself from the tables and summary. Returns: datasets: [{slug, kind (free|premium), title, summary, rows, tables, page_url, and download_url (free) or free_preview_url + buy_url + price_usd (premium)}].
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_certificateThe 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…No findings
Why it is in this group
- The name "get_certificate" says "get": a word for reading.
Description, as the server wrote it 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 key, not the trimmed form generate_dataset returns.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_statusWhere a start_generation job is.No findings
Why it is in this group
- The name "get_status" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_blueprintCheck 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 …No findings
Why it is in this group
- The name "validate_blueprint" says "validate": a word for reading.
Description, as the server wrote it 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 small preview run (a few thousand rows) with the verifier's findings and sample rows, so you can see the data behave before the real call. Free. Returns: valid, errors (fix these), warnings (read these), planned (sizes the stated numbers set; "keep_size" on a table keeps its row_count), estimated_rows, row_cap, preview: {passed, findings, tables: {name: first rows}} when `preview`.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whoamiWhich 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.No findings
Why it is in this group
- The name "whoami" says "whoami": a word for reading.
Description, as the server wrote it 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.
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 outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- 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.
Looked at Nov 20, 2026, 19:19 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
- 503
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.misata.studio/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://clerk.misata.studio
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
The probe stopped: initialize answered HTTP 503.
Posture changes
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 503
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
The server marks "cancel_generation" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "cancel_generation" says "cancel": a word for removing or ending something.
- Warncheck_answers
The server marks "check_answers" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.sql), which can change anything it can reach.
- Warnquery_dataset
The server marks "query_dataset" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "query_dataset" says "query": a word for reading.
- Infogenerate_dataset
The description is 4,141 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...rest (patterns, realism scorecard, every proof chart)."
- Infoexport_dataset
The description mentions "credential".
What this check looks forMatched text
description: "...this server never holds a database credential itself. `demo` is t..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 503; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 8 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 503
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http misata https://api.misata.studio/mcpclaude mcp add --transport http misata https://api.misata.studio/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__misata__whoami",
"mcp__misata__validate_blueprint",
"mcp__misata__get_status",
"mcp__misata__get_certificate",
"mcp__misata__find_ready_dataset"
],
"ask": [
"mcp__misata__plan_dataset",
"mcp__misata__blueprint_guide",
"mcp__misata__generate_dataset",
"mcp__misata__start_generation",
"mcp__misata__check_answers",
"mcp__misata__query_dataset",
"mcp__misata__export_dataset"
],
"deny": [
"mcp__misata__cancel_generation"
]
}
}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 misata. Review it before you use it.
Capability tags behind 4 rules
- mcp__misata__generate_dataset untrusted-input
- mcp__misata__start_generation untrusted-input
- mcp__misata__query_dataset private-data
- mcp__misata__find_ready_dataset private-data, untrusted-input
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/studio.misata/misata/verify?hash=eec1fbf30c18a1975d9577af6d39fa9bdde3fff6320de749f80b5ea00b33f55a" | jq -e '.changed == false'Pinned hash eec1fbf30c18, from Oct 21, 2026, 19:20 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/studio.misata/misata/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/studio.misata/misata)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
Misata Studio: verified synthetic data MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Misata Studio: verified synthetic data MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 8 of which can change, send or delete something, and 5 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 Misata Studio: verified synthetic data MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_generation.
Can the Misata Studio: verified synthetic data 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 Misata Studio: verified synthetic data MCP server have?
- 13 tools: 1 destructive, 7 write, 5 read. cancel_generation, plan_dataset, blueprint_guide, generate_dataset, start_generation, check_answers, query_dataset, export_dataset and 5 more.
Does the Misata Studio: verified synthetic data MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Misata Studio: verified synthetic data MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Misata Studio: verified synthetic data MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.