AXF
NPM · @SMARTERGPT/AXF · SCANNED SEP 24
Agent eXoskeleton Framework control plane for workspace-native agent capabilities over MCP.
Available components
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 Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to Guffawaffle/axf). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 425 tokens (~425/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 76% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the AXF MCP server?
AXF runs locally as an npm package, launched with npx -y @smartergpt/axf. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @smartergpt/axf
claude mcp add dev-smartergpt-axf -- npx -y @smartergpt/axf
{
"mcpServers": {
"dev-smartergpt-axf": {
"command": "npx",
"args": [
"-y",
"@smartergpt/axf"
]
}
}
} {
"servers": {
"dev-smartergpt-axf": {
"command": "npx",
"args": [
"-y",
"@smartergpt/axf"
]
}
}
} codex mcp add dev-smartergpt-axf -- npx -y @smartergpt/axf
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-smartergpt-axf": {
"type": "local",
"command": [
"npx",
"-y",
"@smartergpt/axf"
],
"enabled": true
}
}
} openclaw mcp add dev-smartergpt-axf --command npx --arg -y --arg @smartergpt/axf
mcp_servers:
dev-smartergpt-axf:
command: "npx"
args: ["-y", "@smartergpt/axf"] {
"McpServers": {
"dev-smartergpt-axf": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@smartergpt/axf"
]
}
}
} assistant mcp add dev-smartergpt-axf -t stdio -c npx -a -y @smartergpt/axf
{
"mcpServers": {
"dev-smartergpt-axf": {
"command": "npx",
"args": [
"-y",
"@smartergpt/axf"
]
}
}
} 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.
- 24 Sept 26 −2
- Stability: pass → 0.87 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −1
- Stability: pass → 0.90 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
- Package version: 1.1.0 → 2.1.3 functional
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 24 Sept 2026 · Analysed npm/@smartergpt/axf@2.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Guffawaffle/axf |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Guffawaffle/axf/.github/workflows/release.yml@refs/tags/v2.1.3 |
| Rekor log index | 2737925298 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e283cf6780d147c59f693eabf864db18f4d7f68ecba3f5d3126ed862465167317f2674f2f65fb2d791c2d6090336f51cc15ab3f5f265e3337020893c4 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node scripts/install-git-hooks.mjs |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
axf ~425
AXF capability router. Use this single MCP tool to guide, list, explain, inspect, and run AXF capabilities. Capabilities such as global.echo.say are not separate MCP tools. Prefer guide for bounded workflow entrypoints or list with compact/search for discovery. For known external delays, prefer one global.wait.timed invocation over repeated agent status checks; use global.wait.external when an exact typed observer exists. Always inspect before run, and use projectRoot/executionRoot when discovery and execution roots differ.
| Name | Type | Req | Description |
|---|---|---|---|
| allowAnyLifecycle | boolean | – | – |
| args | object | – | Capability arguments passed into AXF's existing validation and execution path. |
| compact | boolean | – | Return compact capability summaries instead of full manifests for operation=list. |
| executionRoot | string | – | Canonical AXF execution root override for runtime cwd and caller-facing execution. |
| executionWorkspace | string | – | Legacy AXF execution workspace override for runtime cwd and caller-facing execution. |
| includeDrafts | boolean | – | – |
| intent | string | – | Optional workflow intent filter for operation=guide. |
| limit | integer | – | Bound list or guide results. Compact response-detail lists default to 25; an explicit limit overrides that bound. |
| operation | string | yes | – |
| projectRoot | string | – | Canonical AXF project root override for manifest and adapter discovery. |
| query | string | – | Capability id, family, prefix, or search term for operation=explain. |
| registryWorkspace | string | – | Legacy AXF registry workspace override for manifest and adapter discovery. |
| responseDetail | string | – | Agent-facing response detail. compact is the deterministic context-efficient default; standard expands the result; diagnostic explicitly adds compatibility and execution metadata with sensitive frame… |
| search | string | – | Filter operation=list by id, summary, provider, owner, family, or manifest source. |
| sideEffects | string | – | – |
| target | object | – | Capability target for explain, inspect, or run. |
| workspace | string | – | Legacy AXF workspace root override that sets both project and execution roots. |
No output schema declared.
No examples provided.
What is the AXF MCP server?
AXF is an MCP server listed in the public MCP registry as dev.smartergpt/axf. Agent eXoskeleton Framework control plane for workspace-native agent capabilities over MCP. This page covers its npm package (@smartergpt/axf).
Is the AXF MCP server safe to use?
AXF scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. Its build provenance is signed and verified. 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 AXF MCP server expose?
AXF exposes 1 tool: axf. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.
Is the AXF MCP server still maintained?
AXF is still listed as active in the MCP registry. We last reached this channel on 24 September 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 AXF MCP server under?
AXF declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.