studio MCP server
net.reogrid/studioreogrid.netstreamable-httpv0.1.2Scanned
Turn analyzed data into an Excel-like spreadsheet at a shareable URL: formulas, styles, filters.
4 tools: 1 do something that can't be undone and 3 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 studio MCP server can do
The studio MCP server is published by reogrid.net, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_sheet), but cannot delete data. 3 tools only read.
1 tool reads private data (get_schema); 1 tool can send data out of your system (publish_sheet).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 0.1.2.
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.
4 tools
Can't be undone 1Claude Code: ask
publish_sheetPublishes a ReoGridJsonDocument and returns a public URL.Can send data outNo findings
Why it is in this group
- The name "publish_sheet" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "publish_sheet" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Publishes a ReoGridJsonDocument and returns a public URL. Anonymous; rate-limited per IP. No expiry in Phase 1. The doc must conform to the schema returned by get_schema().
Only reads 3Show 3 read-only tools
get_feature_specReturns the full schema fragment for one advanced feature.No findings
Why it is in this group
- The name "get_feature_spec" says "get": a word for reading.
Description, as the server wrote it Returns the full schema fragment for one advanced feature. The argument must be an exact name from get_schema().featureNames — it is a fixed enumeration, not a free-text description of what you want to build.
get_schemaReturns the base ReoGridJsonDocument schema and an index of advanced features.Reads private dataNo findings
Why it is in this group
- The name "get_schema" 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 Returns the base ReoGridJsonDocument schema and an index of advanced features. The base schema already covers cell values, formulas, styling, borders and merges — those need no follow-up call. Call get_feature_spec(feature) only for a name listed in the returned features[] array, passing features[].name verbatim.
get_sheetFetches a previously published sheet by its short ID.No findings
Why it is in this group
- The name "get_sheet" says "get": a word for reading.
Description, as the server wrote it Fetches a previously published sheet by its short ID.
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 untrusted-input.
- Reads private data1
- 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 out1
- 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:16 UTC, unchanged since Oct 22, 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
- 1
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api-studio.reogrid.net/studio/mcp: tools/list returned 4 tools to an anonymous client, including publish_sheet (irreversible)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
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 0.1.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http studio https://api-studio.reogrid.net/studio/mcpclaude mcp add --transport http studio https://api-studio.reogrid.net/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__studio__get_schema",
"mcp__studio__get_feature_spec",
"mcp__studio__get_sheet"
],
"ask": [
"mcp__studio__publish_sheet"
],
"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 studio. Review it before you use it.
Capability tags behind 2 rules
- mcp__studio__get_schema private-data
- mcp__studio__publish_sheet outbound
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/net.reogrid/studio/verify?hash=c3e7ffe0e8b7ad4c18eb7d38a4cd8c8513c529cd97975511a4e9cac83380b316" | jq -e '.changed == false'Pinned hash c3e7ffe0e8b7, from Nov 18, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/net.reogrid/studio/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/net.reogrid/studio)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
studio MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the studio MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 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 studio MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the studio MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: publish_sheet.
What tools does the studio MCP server have?
- 4 tools: 1 irreversible, 3 read. publish_sheet, get_schema, get_feature_spec and get_sheet.
Does the studio MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the studio MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_sheet.
Has the studio MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.