font-metadata MCP server
io.github.lazymac2x/font-metadatalazymac2xstreamable-httpv1.0.0Scanned
Cloudflare Workers MCP server: font-metadata
6 tools: 3 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the font-metadata MCP server can do
The font-metadata MCP server is published by the GitHub account lazymac2x. It has 6 tools. It can create or change data (3 tools: generate_css, check_language_support and font_stack), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (get_font_info and list_fonts_by_category).
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 21, 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.
6 tools
Changes things 3Claude Code: ask
check_language_supportCheck which languages/scripts a font supports, or verify support for specific language codes.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.
Description, as the server wrote it Check which languages/scripts a font supports, or verify support for specific language codes.
font_stackGenerate a complete CSS font-stack with metric-compatible and system fallbacks for robust cross-platform rendering.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate a complete CSS font-stack with metric-compatible and system fallbacks for robust cross-platform rendering.
generate_cssGenerate ready-to-use CSS @import snippet for a single font or a heading+body font pairing.No findings
Why it is in this group
- The name "generate_css" says "generate": a word for a change.
Description, as the server wrote it Generate ready-to-use CSS @import snippet for a single font or a heading+body font pairing.
Only reads 3Show 3 read-only tools
get_font_infoGet detailed metadata for a specific web font including variants, subsets, tags, designer, year, and Google Fonts URL.Reads text others writeNo findings
Why it is in this group
- The name "get_font_info" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it Get detailed metadata for a specific web font including variants, subsets, tags, designer, year, and Google Fonts URL.
list_fonts_by_categoryList available web fonts filtered by category, tag, or search query.Reads text others writeNo findings
Why it is in this group
- The name "list_fonts_by_category" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it List available web fonts filtered by category, tag, or search query. Returns 100+ fonts across serif, sans-serif, monospace, display, and handwriting categories.
suggest_pairingsGet font pairing recommendations with CSS snippets, compatibility scores, and curated rationale from design experts.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get font pairing recommendations with CSS snippets, compatibility scores, and curated rationale from design experts.
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 outbound.
- 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 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:31 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
- 3
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.lazy-mac.com/.well-known/oauth-protected-resource/font-metadata/mcp
- 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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.lazy-mac.com/font-metadata/mcp: tools/list returned 6 tools to an anonymous client, including generate_css (write), check_language_support (write), font_stack (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 font-metadata https://api.lazy-mac.com/font-metadata/mcpclaude mcp add --transport http font-metadata https://api.lazy-mac.com/font-metadata/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__font-metadata__get_font_info",
"mcp__font-metadata__suggest_pairings",
"mcp__font-metadata__list_fonts_by_category"
],
"ask": [
"mcp__font-metadata__generate_css",
"mcp__font-metadata__check_language_support",
"mcp__font-metadata__font_stack"
],
"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 font-metadata. Review it before you use it.
Capability tags behind 2 rules
- mcp__font-metadata__get_font_info untrusted-input
- mcp__font-metadata__list_fonts_by_category untrusted-input
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.lazymac2x/font-metadata/verify?hash=2a02f298cf6dc9407b71b69dc66610a4f30aa8585e8aaece883a4fd929d6869d" | jq -e '.changed == false'Pinned hash 2a02f298cf6d, from Nov 21, 2026, 17: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.lazymac2x/font-metadata/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.lazymac2x/font-metadata)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:38 UTC.
font-metadata MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the font-metadata MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 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 font-metadata MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the font-metadata 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 font-metadata MCP server have?
- 6 tools: 3 write, 3 read. generate_css, check_language_support, font_stack, get_font_info, suggest_pairings and list_fonts_by_category.
Does the font-metadata MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the font-metadata MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the font-metadata MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.