io.github.acfstandard/acf-mcp
NPM · ACF-MCP
Official ACF® MCP server: Agentic Commerce Framework® governance copilot for AI assistants.
Available components
Last scanned (6 hours ago)
Scores higher than 30% of npm servers
Category Security
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 Security80
- 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
- 58 of 154 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 3725 tokens (~40/item across 92 items; 13 tools + 79 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 13 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 57
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 5 Nov 2026 · Analysed npm/acf-mcp@2.0.1
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 154 packages
| Packages resolved | 154 |
|---|---|
| Stale | 58 |
| 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 →
acf.advisor ~118
When a user describes a real AI use case and needs a structured ACF® governance assessment in return: which principles fire, which autonomy level fits, which regulatory obligations apply, which fiches to mobilise in what order, what are the first operational actions, what are the operational risks. This is the conversion tool: from documentation library to governance advisor.
| Name | Type | Req | Description |
|---|---|---|---|
| case_description | string | yes | – |
| deployment_scale | string | – | – |
| jurisdiction | string | – | – |
| locale | string | – | – |
| sector | string | – | – |
No output schema declared.
No examples provided.
acf.assess-autonomy ~124
When deciding how much autonomy to grant an agent: should it propose, decide or execute? what triggers human review? what is the kill switch design?: get a first-pass assessment grounded in the 4 ACF® autonomy levels with explicit go/no-go criteria, gating thresholds, and uncertainty signalling for human review.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_description | string | yes | – |
| audit_requirements | string | yes | – |
| human_in_loop_cost | string | – | – |
| intended_actions | array | yes | – |
| locale | string | – | – |
| reversibility | string | yes | – |
No output schema declared.
No examples provided.
acf.assign-ddao-controls ~123
When a DDAO needs concrete controls assigned to an autonomous agent: what kill switches, what escalation thresholds, what audit trails, what documentation, who owns each control: get the ACF® control set scoped to the agent's autonomy level and risk class, with double vocabulary (plain-English recommended_controls + ACF-canonical ddao_controls) for external clarity.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_description | string | yes | – |
| autonomy_level | string | yes | – |
| budget_constraint | string | – | – |
| locale | string | – | – |
| risk_level | string | yes | – |
No output schema declared.
No examples provided.
acf.cite ~78
When writing a thesis, a regulatory filing, a board memo or an academic paper that needs to reference ACF®, produce a properly formatted citation in the requested style (APA, MLA, Chicago, ISO 690, BibTeX).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| style | string | – | – |
| uri | string | yes | – |
No output schema declared.
No examples provided.
acf.classify-agent ~214
When a system owner needs a first-pass governance qualification of an AI agent before go-live: what autonomy level it likely operates at, what risk class it likely carries, what regulations apply, what controls to put in place, who should sign off: get one structured preliminary assessment covering all five questions in a single call. Input kept deliberately simple (10 qualified fields); output is structured for human review, not for autonomous regulatory decision-making.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_act_triggers | array | – | – |
| decisions_taken | array | yes | – |
| description | string | yes | – |
| external_actions | string | yes | – |
| financial_exposure | string | yes | – |
| gpai_used | boolean | yes | – |
| human_approval_required | string | yes | – |
| jurisdiction | array | – | – |
| locale | string | – | – |
| name | string | yes | – |
| personal_data_level | string | yes | – |
| processing_purposes | array | – | – |
| sector | string | – | – |
| usage_audience | string | yes | – |
No output schema declared.
No examples provided.
acf.evaluate-agent-mandate ~123
When an existing agent mandate already exists (drafted or proposed for DDAO sign-off) and you need a first-pass audit before go-live or regulatory inspection: does it cover the decision perimeter, the escalation thresholds, the kill switch, the audit trail, the documentation duty?: get a structured preliminary verdict with strengths, gaps, required additions, and explicit gaps_to_validate for the human reviewer.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_purpose | string | yes | – |
| deployment_context | string | – | – |
| locale | string | – | – |
| mandate_text | string | yes | – |
No output schema declared.
No examples provided.
acf.fiche.lookup ~82
When facing a specific governance question (defining an agent's mandate, designing a kill switch, building a decision register…), retrieve the canonical ACF® methodological card that applies: with its example, its mapping to principles and its related cards.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| include_frontmatter | boolean | – | – |
| locale | string | – | – |
No output schema declared.
No examples provided.
acf.glossary.define ~72
When governance vocabulary becomes ambiguous (what is a DDAO? what does Decision Sovereignty exactly mean? what separates co-decision from supervised autonomy?), get the canonical ACF® definition and its connection to the rest of the doctrine.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| term | string | yes | – |
No output schema declared.
No examples provided.
acf.identify-governance-gaps ~107
When auditing your current AI governance setup: what does ACF® suggest you should have that you don't?: get a first-pass gap analysis across the 4 ACF® principles, prioritised by criticality, with remediation actions, quick wins, and explicit uncertainty signalling on which gaps were inferred vs declared.
| Name | Type | Req | Description |
|---|---|---|---|
| current_inventory | object | yes | – |
| current_processes | array | yes | – |
| locale | string | – | – |
| sector | string | – | – |
No output schema declared.
No examples provided.
acf.map-ai-act-obligations ~170
When a system has been preliminarily qualified as high-risk and you need the exhaustive list of AI Act obligations that apply: Art. 9 risk management, Art. 10 data, Art. 11 docs, Art. 12 logs, Art. 13 transparency, Art. 14 human oversight, Art. 15 robustness, GPAI Art. 51-55: get the full obligation set structured by lifecycle phase (pre-go-live / continuous / on-incident) with deadlines (incl. Digital Omnibus deferrals) and ACF® operational translation.
| Name | Type | Req | Description |
|---|---|---|---|
| annex | string | yes | – |
| gpai_used | boolean | – | – |
| locale | string | – | – |
| provider_or_deployer | string | yes | – |
| use_case | string | yes | – |
No output schema declared.
No examples provided.
acf.map-to-standards ~172
When a DDAO, an auditor or a compliance officer needs to know which articles of the major external standards (EU AI Act, GDPR, DORA, NIS2, ISO/IEC 42001) each ACF® methodological card connects to: and which ACF® cards a given external article relies on: get the reverse-index built from the same canonical mapping consumed by acf.regulation.article. Useful for cross-mapping audits, regulator filings, and ACF×AI Act conformity arguments. Pass a single fiche_id (e.g. ACF-07) for a focused view, or call without it for the complete inventory of the toolkit cards that the mapping references.
| Name | Type | Req | Description |
|---|---|---|---|
| fiche_id | string | – | – |
| locale | string | – | – |
| regulations | array | – | – |
No output schema declared.
No examples provided.
acf.regulation.article ~108
When a regulator, an auditor or a board references a specific article (AI Act Art. 9, GDPR Art. 35, DORA Art. 28, NIS2 Art. 21, ISO 42001 §6…), get the verified text and its operational translation into the ACF® framework: which principles it activates and which fiches operationalise it.
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | yes | – |
| locale | string | – | – |
| regulation | string | yes | – |
No output schema declared.
No examples provided.
acf.search ~80
When you don't know which ACF® resource is most relevant to the situation at hand (a question, a regulator request, a board challenge…), search the full ACF® corpus and rank candidate resources by relevance.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| locale | string | – | – |
| query | string | yes | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.acfstandard/acf-mcp server?
io.github.acfstandard/acf-mcp runs locally as an npm package, launched with npx -y acf-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 · acf-mcp
claude mcp add acfstandard-acf-mcp -- npx -y acf-mcp
What is the io.github.acfstandard/acf-mcp server?
io.github.acfstandard/acf-mcp is listed in the public MCP registry as io.github.acfstandard/acf-mcp. Official ACF® MCP server: Agentic Commerce Framework® governance copilot for AI assistants. This page covers its npm package (acf-mcp).
Is the io.github.acfstandard/acf-mcp server safe to use?
io.github.acfstandard/acf-mcp scores 59 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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.acfstandard/acf-mcp server expose?
io.github.acfstandard/acf-mcp exposes 13 tools: acf.search, acf.fiche.lookup, acf.regulation.article, acf.glossary.define, acf.cite, and 8 more. Their descriptions and schemas cost roughly 1,571 tokens of context every time the server is loaded.
Is the io.github.acfstandard/acf-mcp server still maintained?
io.github.acfstandard/acf-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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.acfstandard/acf-mcp server under?
io.github.acfstandard/acf-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.