io.github.mrfentmen/fea-mcp
NPM · @MRFENTMEN/FEA-MCP
FEA MCP: parse OpenType feature files, validate blocks, tags and braces.
Available components
Last scanned (16 hours ago)
Scores higher than 29% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 602 tokens (~43/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Nov 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@mrfentmen/fea-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
detect_files ~35
Find FEA files (.fea) in a directory tree.
| Name | Type | Req | Description |
|---|---|---|---|
| maxDepth | integer | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
diff ~59
Compare two FEA documents: added, removed and changed records.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | – |
| leftContent | string | – | – |
| leftPath | string | – | – |
| rightContent | string | – | – |
| rightPath | string | – | – |
No output schema declared.
No examples provided.
format_reference ~23
Return a compact FEA reference: structure, required fields and common pitfalls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_record ~49
Return one FEA record by id, with all parsed fields.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| cwd | string | – | – |
| id | string | yes | – |
| path | string | – | – |
No output schema declared.
No examples provided.
list_records ~48
List FEA record ids and kinds, with a limit.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| cwd | string | – | – |
| limit | integer | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
parse ~39
Parse FEA into records, fields and document metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| cwd | string | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
read_file ~49
Read a FEA file, optionally a line range.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | – |
| endLine | integer | – | – |
| path | string | yes | – |
| startLine | integer | – | – |
No output schema declared.
No examples provided.
sample ~17
Return a small but valid FEA example document.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search ~60
Search FEA records by plain text or regular expression.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| cwd | string | – | – |
| limit | integer | – | – |
| path | string | – | – |
| query | string | yes | – |
| regex | boolean | – | – |
No output schema declared.
No examples provided.
stats ~45
Numeric statistics for FEA fields across all records.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| cwd | string | – | – |
| field | string | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
summarize ~45
Summarize a FEA document: metadata, record counts and per-kind totals.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| cwd | string | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
to_json ~38
Export every parsed FEA record as JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| cwd | string | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
validate ~44
Validate FEA against its structural rules and report every issue with a line number.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| cwd | string | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
write_file ~51
Write a FEA file. Refuses to overwrite unless overwrite is true.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| cwd | string | – | – |
| overwrite | boolean | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.mrfentmen/fea-mcp server?
io.github.mrfentmen/fea-mcp runs locally as an npm package, launched with npx -y @mrfentmen/fea-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mrfentmen/fea-mcp
claude mcp add mrfentmen-fea-mcp -- npx -y @mrfentmen/fea-mcp
What is the io.github.mrfentmen/fea-mcp server?
io.github.mrfentmen/fea-mcp is listed in the public MCP registry as io.github.mrfentmen/fea-mcp. FEA MCP: parse OpenType feature files, validate blocks, tags and braces. This page covers its npm package (@mrfentmen/fea-mcp).
Is the io.github.mrfentmen/fea-mcp server safe to use?
io.github.mrfentmen/fea-mcp scores 58 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mrfentmen/fea-mcp server expose?
io.github.mrfentmen/fea-mcp exposes 14 tools: detect_files, read_file, write_file, parse, validate, and 9 more. Their descriptions and schemas cost roughly 602 tokens of context every time the server is loaded.
Is the io.github.mrfentmen/fea-mcp server still maintained?
io.github.mrfentmen/fea-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mrfentmen/fea-mcp server under?
io.github.mrfentmen/fea-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.mrfentmen/fea-mcp server?
VerifyMCP ran 15 checks on io.github.mrfentmen/fea-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.mrfentmen/fea-mcp: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.