favicon.zip MCP server
zip.favicon/faviconfavicon.zipstreamable-httpv1.0.0Scanned
Generate favicons (ICO, SVG, Apple touch, PWA, manifest) from SVG, text or emoji; check any site.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- 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.
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 favicon.zip MCP server can do
The favicon.zip MCP server is published by favicon.zip, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: generate_favicon), but cannot delete data. 2 tools only read.
2 tools bring in text other people can write (get_html_snippet and check_favicon); 1 tool can send data out of your system (check_favicon).
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 19, 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.
3 tools
Changes things 1Claude Code: ask
generate_faviconGenerates the complete modern favicon set (favicon.ico, icon.svg, apple-touch-icon.png, PWA icons, manifest.webmanifest, favicon-setup.md with the install snippet) from an SVG, an …No findings
Why it is in this group
- The name "generate_favicon" says "generate": a word for a change.
Description, as the server wrote it Generates the complete modern favicon set (favicon.ico, icon.svg, apple-touch-icon.png, PWA icons, manifest.webmanifest, favicon-setup.md with the install snippet) from an SVG, an emoji, or short text. Returns a download URL for favicon.zip plus the HTML head snippet to paste. Files follow current best practice: ICO with 16, 32, and 48px layers, a 96px Google Search icon, opaque apple-touch-icon, and a maskable icon with safe-zone padding.
Only reads 2Show 2 read-only tools
check_faviconFetches a URL, probes every icon it declares (root favicon.ico, SVG icon, apple-touch-icon, web manifest), and grades the setup against the modern set.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it Fetches a URL, probes every icon it declares (root favicon.ico, SVG icon, apple-touch-icon, web manifest), and grades the setup against the modern set. Follow up with generate_favicon to fix what is missing.
get_html_snippetReturns the modern minimal <head> snippet for favicons, plus placement guidance.Reads text others writeNo findings
Why it is in this group
- The name "get_html_snippet" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_html_snippet" says "get" and "html": it reads web pages, which anyone can write.
Description, as the server wrote it Returns the modern minimal <head> snippet for favicons, plus placement guidance. Use when the favicon files already exist and only the HTML wiring is needed.
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.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- 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:21 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://favicon.zip/mcp: tools/list returned 3 tools to an anonymous client, including generate_favicon (write)
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 favicon https://favicon.zip/mcpclaude mcp add --transport http favicon https://favicon.zip/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__favicon__get_html_snippet"
],
"ask": [
"mcp__favicon__generate_favicon",
"mcp__favicon__check_favicon"
],
"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 favicon. Review it before you use it.
Capability tags behind 2 rules
- mcp__favicon__get_html_snippet untrusted-input
- mcp__favicon__check_favicon untrusted-input, 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/zip.favicon/favicon/verify?hash=bdd9b1672de456c90546cbeb1f1bc5ff9502e6a79a886c6df681bb4d7ef570e0" | jq -e '.changed == false'Pinned hash bdd9b1672de4, from Nov 19, 2026, 14:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/zip.favicon/favicon/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/zip.favicon/favicon)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
favicon.zip MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the favicon.zip MCP server safe?
- No scan can promise that. What its definitions show: 3 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 favicon.zip MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the favicon.zip 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 favicon.zip MCP server have?
- 3 tools: 1 write, 2 read. generate_favicon, get_html_snippet and check_favicon.
Does the favicon.zip MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the favicon.zip 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): check_favicon.
Has the favicon.zip MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.