Zovo Barcode Maker MCP server
io.github.theluckystrike/barcode-makertheluckystrikestreamable-httpv1.0.1Scanned
EAN, UPC & Code 128 barcodes
2 tools: 1 change things and 1 only read.
- 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
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.
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 Barcode Maker MCP server can do
The Zovo Barcode Maker MCP server is published by the GitHub account theluckystrike. It has 2 tools. It can create or change data (1 tool: generate_barcode), but cannot delete data. 1 tool 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.1.
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
generate_barcodeUse this when the user wants a barcode generator: a UPC or EAN-13 barcode for a product, a Code 128 barcode for a SKU or label, GS1-128 with (01) GTIN, (17) expiry and (10) lot, Co…1 finding
Why it is in this group
- The name "generate_barcode" 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_barcode" 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_barcode" says "generate": a word for a change.
Description, as the server wrote it Use this when the user wants a barcode generator: a UPC or EAN-13 barcode for a product, a Code 128 barcode for a SKU or label, GS1-128 with (01) GTIN, (17) expiry and (10) lot, Code 39, an ITF-14 carton code, or a book ISBN barcode. Computes or verifies the check digit (explains a wrong one), applies GS1 quiet zones and sizes, and returns SVG and PNG download links plus calculated print dimensions. One barcode per request; Code 128 up to 80 characters, Code 39 up to 60 characters, and GS1-128 up to 48 data characters including separator FNC1 characters. Does not issue or register GS1 numbers (real UPC/EAN numbers must be licensed from GS1), does not scan images or look up products. Do not use for QR codes.
Annotations the server declares
- title: Generate barcode
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
Only reads 1Show 1 read-only tool
validate_barcode_numberUse this when the user asks whether a UPC, EAN, GTIN-8/12/13/14, SSCC, ISBN-10/13 or ISSN number is valid, what its check digit should be, or wants to convert ISBN-10 to ISBN-13, U…No findings
Why it is in this group
- The name "validate_barcode_number" says "validate": a word for reading.
Description, as the server wrote it Use this when the user asks whether a UPC, EAN, GTIN-8/12/13/14, SSCC, ISBN-10/13 or ISSN number is valid, what its check digit should be, or wants to convert ISBN-10 to ISBN-13, UPC-E to UPC-A, or UPC-A to EAN-13/GTIN-14. Explains the check-digit arithmetic, gives the corrected number and the GS1 prefix meaning. Does not tell who owns a number, whether it is registered with GS1, or what product it is; does not look anything up online.
Annotations the server declares
- title: Validate barcode number
- 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 20, 2026, 19:26 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
- 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.
What this check looks forMatched text
https://barcode-maker.zovo.one/mcp: tools/list returned 2 tools to an anonymous client, including generate_barcode (write)
Findings
Matches of fixed checks, with the text they matched.
- Warngenerate_barcode
The server marks "generate_barcode" 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_barcode" 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.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http barcode-maker https://barcode-maker.zovo.one/mcpclaude mcp add --transport http barcode-maker https://barcode-maker.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": [
"mcp__barcode-maker__validate_barcode_number"
],
"ask": [
"mcp__barcode-maker__generate_barcode"
],
"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 barcode-maker. 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/barcode-maker/verify?hash=2b4c57cb5c02347a0fd3a294028dfca29e5f8aa9cd806975133fb4ec1673a299" | jq -e '.changed == false'Pinned hash 2b4c57cb5c02, from Nov 8, 2026, 12:18 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/barcode-maker/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/barcode-maker)Source: MCP Registry. Synced Oct 22, 2026, 06:19 UTC.
Zovo Barcode Maker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Zovo Barcode Maker MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 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 Barcode 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 Barcode 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 Barcode Maker MCP server have?
- 2 tools: 1 write, 1 read. generate_barcode and validate_barcode_number.
Does the Zovo Barcode Maker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Zovo Barcode 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 Barcode Maker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.