Zovo Cryptogram Maker MCP server
io.github.theluckystrike/cryptogramtheluckystrikestreamable-httpv1.0.0Scanned
Make printable cryptogram puzzles with answers from your own quotes, for a class, a club newsletter.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- 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 Zovo Cryptogram Maker MCP server can do
The Zovo Cryptogram Maker MCP server is published by the GitHub account theluckystrike. It has 2 tools. It can create or change data (2 tools: generate_cryptograms and solve_cryptogram), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
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 2Claude Code: ask
generate_cryptogramsUse this when the user wants printable cryptogram puzzles (cryptogram maker, cryptoquote puzzles, cryptogram puzzles printable with answers, large print cryptograms) from their own…1 finding
Why it is in this group
- The name "generate_cryptograms" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "generate_cryptograms" 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 "generate_cryptograms" says "generate": a word for a change.
Description, as the server wrote it Use this when the user wants printable cryptogram puzzles (cryptogram maker, cryptoquote puzzles, cryptogram puzzles printable with answers, large print cryptograms) from their own quotes or phrases. Convert pasted quotes or a photo of a list into puzzles[] with quote and author fields; text is only a fallback. Each puzzle gets its own substitution key in which no letter stands for itself; optional hint letters, a letter-count helper grid and large print; the PDF ends with an answer key. Only A-Z letters are enciphered; accented letters and other alphabets stay as written. If the user gives no quotes, pick suitable public-domain quotes first. Does not make symbol ciphers or solve puzzles (use solve_cryptogram).
Annotations the server declares
- title: Generate printable cryptograms
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
solve_cryptogramUse this when the user is stuck on a cryptogram or cryptoquote (cryptoquote help, cryptogram solver) and gives the enciphered text.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 is stuck on a cryptogram or cryptoquote (cryptoquote help, cryptogram solver) and gives the enciphered text. Returns up to 3 candidate readings ranked against an English word list of about 25,000 words, the letter key for the top reading, the letters still open, and a confidence of high, medium or low with the reason. Pass letters already known (a printed clue) in known_letters. Short texts, names and rare words lower the confidence, and the tool says so; report that confidence to the user. English only; does not solve number or symbol ciphers, Caesar shifts with a shown key, or today's newspaper puzzle without its text.
Annotations the server declares
- title: Suggest cryptogram solutions
- 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 private-data or untrusted-input or outbound.
- Reads private data0
- 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.
Looked at Nov 15, 2026, 13:23 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
- 2
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://cryptogram.zovo.one/mcp: tools/list returned 2 tools to an anonymous client, including generate_cryptograms (write), solve_cryptogram (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "generate_cryptograms" 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 "generate_cryptograms" says "generate": a word for a change.
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 cryptogram https://cryptogram.zovo.one/mcpclaude mcp add --transport http cryptogram https://cryptogram.zovo.one/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": [],
"ask": [
"mcp__cryptogram__generate_cryptograms",
"mcp__cryptogram__solve_cryptogram"
],
"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 cryptogram. Review it before you use it.
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/cryptogram/verify?hash=61c36604dd4a75717888e13396163b2b4eac266114a031db059c2e17b2f78304" | jq -e '.changed == false'Pinned hash 61c36604dd4a, 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/cryptogram/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/cryptogram)Source: MCP Registry. Synced Nov 8, 2026, 03:17 UTC.
Zovo Cryptogram Maker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Zovo Cryptogram Maker MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 1 finding 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 Cryptogram Maker 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 Cryptogram Maker 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 Cryptogram Maker MCP server have?
- 2 tools: 2 write. generate_cryptograms and solve_cryptogram.
Does the Zovo Cryptogram Maker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Zovo Cryptogram Maker 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 Cryptogram Maker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.