io.github.zz-plant/ambit
NPM · AMBIT-CLI
Capability graph of your agent stack: what it can do, what to set up next, what breaks.
Available components
Last scanned (23 hours ago)
Scores higher than 76% of npm servers
Category Memory and Knowledge
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 29 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 3114 tokens (~51/item across 61 items; 60 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 15% 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 60 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 62 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 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.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed npm/ambit-cli@0.6.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 →
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 →
ambit_signals ~47
Failures seen in the window that no one recorded, by class and tool, including those no capability could be attributed to: a gap in the model.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | – |
No output schema declared.
No examples provided.
ambit_simulate ~41
The frontier as it would be if a capability were acquired, including what it unblocks. A preview: changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| capId | string | yes | – |
No output schema declared.
No examples provided.
ambit_since ~47
What entered the reachable frontier between two ISO timestamps (default: earliest observation to now), split into acquired and emerged through composition.
| Name | Type | Req | Description |
|---|---|---|---|
| until | string | – | – |
| when | string | – | – |
No output schema declared.
No examples provided.
ambit_skills ~21
Skills registered this way, and what each check last said.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ambit_spof ~32
Capabilities with exactly one provider, where redundancy is absent. Bottlenecks rank leverage; this ranks fragility.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ambit_stats ~25
Counts of capabilities: total, reached, verified and failing, and reached per domain.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ambit_usage ~55
Where effort went over a window in days (default 30): times exercised, duration and interventions per capability. unmapped: tools used that no node covers.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | – |
| unmapped | boolean | – | – |
No output schema declared.
No examples provided.
ambit_verify ~48
Run a capability's declared check and record the outcome: proof that it works, not that it is configured. Omit capId to run every declared check.
| Name | Type | Req | Description |
|---|---|---|---|
| capId | string | – | – |
No output schema declared.
No examples provided.
ambit_work ~36
Recent work runs and what each cost: elapsed time, events, capabilities exercised, human interventions, resources.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
ambit_work_event ~208
Record one observation into a run. kind: event, use, intervention, resource or outcome. interventionKind: judgment, authority, knowledge, physical, clerical or exception.
| Name | Type | Req | Description |
|---|---|---|---|
| achieved | string | – | – |
| action | string | – | – |
| activeSeconds | number | – | – |
| actor | string | – | – |
| capabilityId | string | – | – |
| costCents | number | – | – |
| detail | string | – | – |
| durationSeconds | number | – | – |
| eventKind | string | – | – |
| interventionKind | string | – | – |
| kind | string | yes | event | use | intervention | resource | outcome |
| objectiveMetric | number | – | – |
| objectiveName | string | – | – |
| quantity | number | – | – |
| resourceId | string | – | – |
| resourceKind | string | – | – |
| runId | string | yes | – |
| unit | string | – | – |
| valueCents | number | – | – |
| waitingSeconds | number | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.zz-plant/ambit MCP server?
io.github.zz-plant/ambit runs locally as an npm package, launched with npx -y ambit-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ambit-cli
claude mcp add zz-plant-ambit -- npx -y ambit-cli
What is the io.github.zz-plant/ambit MCP server?
io.github.zz-plant/ambit is an MCP server listed in the public MCP registry as io.github.zz-plant/ambit. Capability graph of your agent stack: what it can do, what to set up next, what breaks. This page covers its npm package (ambit-cli).
Is the io.github.zz-plant/ambit MCP server safe to use?
io.github.zz-plant/ambit scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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.zz-plant/ambit MCP server expose?
io.github.zz-plant/ambit exposes 60 tools: ambit_stats, ambit_context, ambit_cap, ambit_decay, ambit_combos, and 55 more. Their descriptions and schemas cost roughly 2,884 tokens of context every time the server is loaded.
Is the io.github.zz-plant/ambit MCP server still maintained?
io.github.zz-plant/ambit is still listed as active in the MCP registry. We last reached this channel on 4 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.zz-plant/ambit MCP server under?
io.github.zz-plant/ambit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.