Skip to content

Zovo JSON to Spreadsheet MCP server

io.github.theluckystrike/json-to-exceltheluckystrikestreamable-httpv1.0.0Scanned

Turn a JSON file or pasted JSON into an Excel workbook and a CSV, right in the chat.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • 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 Zovo JSON to Spreadsheet MCP server can do

The Zovo JSON to Spreadsheet MCP server is published by the GitHub account theluckystrike. It has 2 tools. It can create or change data (1 tool: json_to_excel), but cannot delete data. 1 tool only reads.

1 tool reads private data (inspect_json).

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 8, 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.

2 tools

Changes things 1Claude Code: ask
  • json_to_excelUse this when the user wants to convert JSON to Excel or CSV, turn an API response or a JSON export into a spreadsheet, or flatten nested JSON into columns.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
    Use this when the user wants to convert JSON to Excel or CSV, turn an API response or a JSON export into a spreadsheet, or flatten nested JSON into columns. Takes one attached .json file or pasted json_text, an optional records_path (e.g. data.items) and orient (records, columns, index), and how to handle lists (scalar_arrays join or rows, object_arrays sheet or json). Returns an .xlsx and a .csv download (a ZIP of CSVs when there are linked sheets), the rows, columns and cells written, the numbers kept as text, formula-like text, and a check that each cell was read back from both files. Does not accept JSON with comments, trailing commas or JSON Lines, and does not turn date text into Excel dates. Do not use for Excel to JSON or for editing a JSON file.

    Annotations the server declares

    • title: JSON to Excel
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • inspect_jsonUse this when the user asks what a JSON file contains, which keys or nesting it has, how many records it holds, or why it does not parse, before converting it.Reads private dataNo findings

    Why it is in this group

    • The name "inspect_json" says "inspect": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • private-dataThe input names a file (input.file), and the tool reads: it reads files.
    Description, as the server wrote it
    Use this when the user asks what a JSON file contains, which keys or nesting it has, how many records it holds, or why it does not parse, before converting it. Takes the same file or json_text, records_path and orient as json_to_excel and returns the record count, the key paths with their types and fill rate, nesting depth, the lists inside the records, duplicate keys, an estimate of sheets, columns and cells, and suggestions (for example a records_path). Invalid JSON is reported with its line and column. Does not make a file and does not change the JSON.

    Annotations the server declares

    • title: Inspect JSON structure
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

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

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 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 15, 2026, 13:24 UTC, unchanged since Nov 8, 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
  • WarnThe whole server

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

    Matched text

    https://json-to-excel.zovo.one/mcp: tools/list returned 2 tools to an anonymous client, including json_to_excel (write)

    What this check looks for

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 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http json-to-excel https://json-to-excel.zovo.one/mcp
claude mcp add --transport http json-to-excel https://json-to-excel.zovo.one/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__json-to-excel__inspect_json"
    ],
    "ask": [
      "mcp__json-to-excel__json_to_excel"
    ],
    "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 json-to-excel. Review it before you use it.

Capability tags behind 1 rule
  • mcp__json-to-excel__inspect_json 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.theluckystrike/json-to-excel/verify?hash=1c61f2899bc42baf8779b05d4421bd2c33eb59312ae885bbbabf32e64c9f733f" | jq -e '.changed == false'

Pinned hash 1c61f2899bc4, from Nov 8, 2026, 02:19 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.theluckystrike/json-to-excel/changes.xml

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

Badge

Anlyon Radar badge for io.github.theluckystrike/json-to-excel
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/json-to-excel.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/json-to-excel)

Source: MCP Registry. Synced Nov 8, 2026, 03:18 UTC.

Zovo JSON to Spreadsheet MCP server: questions and answers

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

Is the Zovo JSON to Spreadsheet MCP server safe?

No scan can promise that. What its definitions show: 2 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 Zovo JSON to Spreadsheet MCP server delete data?

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

Can the Zovo JSON to Spreadsheet 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 Zovo JSON to Spreadsheet MCP server have?

2 tools: 1 write, 1 read. json_to_excel and inspect_json.

Does the Zovo JSON to Spreadsheet MCP server need sign-in or OAuth?

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

Does the Zovo JSON to Spreadsheet MCP server send data to outside services?

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

Has the Zovo JSON to Spreadsheet MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.