Feature Library MCP server
com.featurelibrary/partsfeaturelibrary.comstreamable-httpv0.3.2Scanned
Measured WebGPU and web UI parts with guides and pitfalls. Plan free; install licensed parts.
11 tools: 3 change things and 8 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
3 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 Feature Library MCP server can do
The Feature Library MCP server is published by featurelibrary.com, a domain the MCP Registry verified. It has 11 tools. It can create or change data (3 tools: install, check_look and check), but cannot delete data. 8 tools only read.
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, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 0.3.2.
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.
11 tools
Changes things 3Claude Code: ask
checkFree.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 Free. The rules version (its hash) and the catalogue version, the checks to run on the build before calling it done, the runnable checks (get_check) that prove the ones a checklist can’t, and, with a licence token, the account’s licences and the parts it owns. Pass evidence (what the checks returned, area by area) and it says whether the build may be called done, and what is missing.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
check_lookFree.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 Free. Runs the library’s own checker on how a build uses a look: each override is one of the look’s knobs, of its kind and in range; each switch is one of its options; and text contrast holds (WCAG AA) in each mode at the dials’ extremes with the overrides applied. Returns ok, the problems in sentences, the label the build may use ("In Splash", "Splash, tuned"; none for inspired) and, for a tuned build that passes, the stylesheet to load after the look’s.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
installLicensed (needs a licence token that owns the part).1 finding
Why it is in this group
- The name "install" says "install": 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 "install" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "install" says "install": a word for a change.
Description, as the server wrote it Licensed (needs a licence token that owns the part). Returns the part’s module/ files, each marked with the licence and this fetch, plus NOTICE.md where there is one and the licence; and first, save: a link and one shell command that write exactly those files to disk (use it: the files carry invisible markers that copying them out of the reply loses). The files also come as resources. Pin a version to be sure of what you get. Also takes a look id (e.g. splash, with a whole-library licence): the look’s stylesheet, its backdrop where it has one, the shared dials and the plain tokens, and the order to load them in. A look keeps the earlier versions builds were made with: pin one with version (its reply lists them).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 8Show 8 read-only tools
find_partsFree.No findings
Why it is in this group
- The name "find_parts" says "find": a word for reading.
Description, as the server wrote it Free. Ranks the library’s parts for a job described in words, with why each fits and what it costs on the target platform (median ms a frame at 1920×1080 on a measured machine and tier). Strong matches for the job come first (each part says match: strong or loose, and which of the job’s words it matched), then looser ones; when nothing plainly does the job, every result is loose and nothingFits says so: build that piece yourself rather than force a part to fit; within each, parts that fit the platform and budget lead, then those over the budget (overBudget), then those that need WebGPU on a platform without it (blocked). For an interface job, 3D, simulation and effects parts rank lower. Each part says what it runs in (runsIn): raw WebGPU passes, a three.js scene, a 2D canvas or the DOM; a three.js part needs a three.js app, so check it against your renderer before installing. When the words name a look or ask for one, the matching looks come back too. Search by the job, not by a name.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_briefFree.No findings
Why it is in this group
- The name "get_brief" says "get": a word for reading.
Description, as the server wrote it Free. The agent protocol (rules.md) to follow, in order, when building with the library’s parts. Also the resource feature-store://rules.md.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_checkFree.No findings
Why it is in this group
- The name "get_check" says "get": a word for reading.
Description, as the server wrote it Free. Scripts you run on your own build, in its page, for what a checklist can’t prove: layout-probe measures that nothing moves when the view changes state (column edges, row tops, controls that come and go) and that every focus ring shows whole. Without an id, the list with what each proves and how to run it; with an id, the script itself as text. Run them at every width you claim and pass the results to check({ evidence }).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_kitFree.No findings
Why it is in this group
- The name "get_kit" says "get": a word for reading.
Description, as the server wrote it Free. A tested set of parts for a kind of build (by kit id, or matched to the purpose in words), built on the foundations, with a tone applied when given: the parts with why, role, stack, needs and costs, the optional candidates, the glue you build yourself, what the library lacks, the tone’s settings and per-part knobs, and the looks that fit, at the level asked for (exact, tuned or inspired: what may change, what must stay); and the page shapes the purpose calls for (starting points for the page as a whole), or, when none fits, how to compose one.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_partThe free card always (summary, role, needs, costs, public API signatures, pitfall titles, pairs-with).No findings
Why it is in this group
- The name "get_part" says "get": a word for reading.
Description, as the server wrote it The free card always (summary, role, needs, costs, public API signatures, pitfall titles, pairs-with). With a licence token that owns the part: the licensed card too, with every pitfall in full, the guide, documented signatures, the module’s files and the changelog. Read every pitfall before building with it.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_playbookFree.No findings
Why it is in this group
- The name "get_playbook" says "get": a word for reading.
Description, as the server wrote it Free. The library’s playbooks: how parts are placed, moved, made accessible and kept fast, with the reason for every rule and a checklist. Without an id, the list (title, summary, the parts each covers); with an id, the playbook in full as markdown. get_kit and get_recipe name the playbooks that cover their parts: read those (playbooks) before wiring the parts; the ones under playbooksIfUsed only when the build uses that part or does that work.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_recipeLicensed (needs a licence token).No findings
Why it is in this group
- The name "get_recipe" says "get": a word for reading.
Description, as the server wrote it Licensed (needs a licence token). The wiring for a scenario: the kit that fits, the steps in order (tier, install, tokens, wiring between the parts, glue, what to build yourself, tone, checks), and for each part you own its pitfalls in full and its guide. Parts you don’t own are listed with their titles, to buy or replace.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_shapeFree.No findings
Why it is in this group
- The name "get_shape" says "get": a word for reading.
Description, as the server wrote it Free. The page shapes: starting points for a whole page by kind (app workspace, dashboard, product reveal, service landing, story, personal homepage, event, shop, game), each with its reader’s job, reading path, first screen, header, structure, phone, motion, what fits and what not to do. Without an id, the list; with an id, the shape in full; with "compose", the method for a page no shape fits, with a worked example. A shape is where to start, never a template: pick one or compose, and name it in your notes.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
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 19, 2026, 17:18 UTC, unchanged since Nov 19, 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
- 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 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://featurelibrary.com/mcp: tools/list returned 11 tools to an anonymous client, including install (write), check_look (write), check (write)
Findings
Matches of fixed checks, with the text they matched.
- Warninstall
The server marks "install" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "install" says "install": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:installChanges thingsdescriptioninputSchema
Tools1 changed.~1 changedView diff
- Changed:installChanges thingsdescription
Tools6 changed.~6 changedView diff
- Changed:checkChanges thingsinputSchema
- Changed:check_lookChanges thingsinputSchema
- Changed:find_partsOnly readsdescriptioninputSchema
- Changed:get_briefOnly readsinputSchema
- Changed:get_kitOnly readsinputSchema
- Changed:get_recipeOnly readsinputSchema
Install
Pinned to version 0.3.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http parts https://featurelibrary.com/mcpclaude mcp add --transport http parts https://featurelibrary.com/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__parts__find_parts",
"mcp__parts__get_kit",
"mcp__parts__get_part",
"mcp__parts__get_recipe",
"mcp__parts__get_playbook",
"mcp__parts__get_check",
"mcp__parts__get_shape",
"mcp__parts__get_brief"
],
"ask": [
"mcp__parts__install",
"mcp__parts__check_look",
"mcp__parts__check"
],
"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 parts. 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/com.featurelibrary/parts/verify?hash=74f7d01e6651bd56271ac423746924443b3af6b49d8d631175abe64318cccdd5" | jq -e '.changed == false'Pinned hash 74f7d01e6651, from Nov 21, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.featurelibrary/parts/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.featurelibrary/parts)Source: MCP Registry. Synced Nov 21, 2026, 16:17 UTC.
Feature Library MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Feature Library MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 3 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 Feature Library MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Feature Library 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 Feature Library MCP server have?
- 11 tools: 3 write, 8 read. install, check_look, check, find_parts, get_kit, get_part, get_recipe, get_playbook and 3 more.
Does the Feature Library MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Feature Library MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Feature Library MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.