ambit-cli

MCPcommunity
v0.5.0UnknownMITUpdated 3d agonpmGitHub

What you, your agents, and your machines can jointly do — and where your own time is going.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
88Downloads/wk
2GitHub stars
2Forks
3d agoLast update
Package
AuthorUnknown
LicenseMIT
Version0.5.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface40 tools · none privileged
Security scan✓ Cleanv0.5.0 · todayHow well does this scan work?
EvalsNone
IndexedOct 4, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

40 tools · none privileged
Statically extracted from the published packagev0.5.0 · 8h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

statsCounts of capabilities: total, reached, verified and failing, and reached per domain.

Counts of capabilities: total, reached, verified and failing, and reached per domain.

No input schema was published for this tool.

contextThe session briefing as one block of prose, the text ambit_briefing returns with text: true.

The session briefing as one block of prose, the text ambit_briefing returns with text: true.

No input schema was published for this tool.

capFind capabilities by domain or name. Returns the ids the other tools take.

Find capabilities by domain or name. Returns the ids the other tools take.

No input schema was published for this tool.

decayCapabilities not touched for long enough to doubt, with days since the last config change.

Capabilities not touched for long enough to doubt, with days since the last config change.

No input schema was published for this tool.

combosCombos the graph can already support: every prerequisite in place, with a confidence.

Combos the graph can already support: every prerequisite in place, with a confidence.

No input schema was published for this tool.

diffPer domain, what was recently practiced, improved or regretted, from the last 50 outcomes.

Per domain, what was recently practiced, improved or regretted, from the last 50 outcomes.

No input schema was published for this tool.

healthDomain health scores.

Domain health scores.

No input schema was published for this tool.

bottlenecksThe capabilities the most others depend on: where an improvement pays most and a loss costs most.

The capabilities the most others depend on: where an improvement pays most and a loss costs most.

No input schema was published for this tool.

impactWhat would stop, and what would only lose a provider, if a capability went away.

What would stop, and what would only lose a provider, if a capability went away.

No input schema was published for this tool.

nearNear-miss combos: one or two prerequisites away, with high existing maturity.

Near-miss combos: one or two prerequisites away, with high existing maturity.

No input schema was published for this tool.

verifyRun 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.

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.

No input schema was published for this tool.

evidenceVerification history of one capability: what was tried, when, and whether it passed.

Verification history of one capability: what was tried, when, and whether it passed.

No input schema was published for this tool.

authorityWhich reached capabilities may run unattended and which need approval. Being able to act is not permission to. Pass detail: true for every grant.

Which reached capabilities may run unattended and which need approval. Being able to act is not permission to. Pass detail: true for every grant.

No input schema was published for this tool.

actionsThe actions a capability confers and whether each may be performed: read a repository yes, merge to its default branch no. Omit capId for all. To ask before acting, use ambit_can.

The actions a capability confers and whether each may be performed: read a repository yes, merge to its default branch no. Omit capId for all. To ask before acting, use ambit_can.

No input schema was published for this tool.

planWhat is missing for a capability, in the order it must be closed, and which steps need a person.

What is missing for a capability, in the order it must be closed, and which steps need a person.

No input schema was published for this tool.

goalRoute a goal, in words, to the capabilities that cover it: ranked, each with its plan delta.

Route a goal, in words, to the capabilities that cover it: ranked, each with its plan delta.

No input schema was published for this tool.

pathsThe ways to reach a capability compared by setup time, risk and lock-in: which steps are config changes that can be undone, and which are installers that cannot.

The ways to reach a capability compared by setup time, risk and lock-in: which steps are config changes that can be undone, and which are installers that cannot.

No input schema was published for this tool.

preferencesWhat each person prefers, and which plans would fight it (local or hosted, one-off or recurring). Pass who for one person.

What each person prefers, and which plans would fight it (local or hosted, one-off or recurring). Pass who for one person.

No input schema was published for this tool.

scopeWhat a scope covers and what it does not. For a target (repo:owner/name, device:nuc, svc:ollama): every grant, whether it covers the target, and the effective mode.

What a scope covers and what it does not. For a target (repo:owner/name, device:nuc, svc:ollama): every grant, whether it covers the target, and the effective mode.

No input schema was published for this tool.

affordancesThe domain of each capability, from the graph: institutional (needs an authority holder), economic (a budget), cognitive (a person), physical (a device).

The domain of each capability, from the graph: institutional (needs an authority holder), economic (a budget), cognitive (a person), physical (a device).

No input schema was published for this tool.

digestHow much work still runs through the human, and which interventions are reducible: recurring approvals and permission blocks are infrastructure shaped like a person. days: window (default 7).

How much work still runs through the human, and which interventions are reducible: recurring approvals and permission blocks are infrastructure shaped like a person. days: window (default 7).

No input schema was published for this tool.

workRecent work runs and what each cost: elapsed time, events, capabilities exercised, human interventions, resources.

Recent work runs and what each cost: elapsed time, events, capabilities exercised, human interventions, resources.

No input schema was published for this tool.

usageWhere effort went over a window in days (default 30): times exercised, duration and interventions per capability. unmapped: tools used that no node covers.

Where effort went over a window in days (default 30): times exercised, duration and interventions per capability. unmapped: tools used that no node covers.

No input schema was published for this tool.

run_beginStart a work run. Returns the run id every later telemetry call attaches to. The run stays open until run_end.

Start a work run. Returns the run id every later telemetry call attaches to. The run stays open until run_end.

No input schema was published for this tool.

run_endClose a work run with its outcome, and the value of that outcome in cents when known.

Close a work run with its outcome, and the value of that outcome in cents when known.

No input schema was published for this tool.

work_eventRecord one observation into a run. kind: event, use, intervention, resource or outcome. interventionKind: judgment, authority, knowledge, physical, clerical or exception.

Record one observation into a run. kind: event, use, intervention, resource or outcome. interventionKind: judgment, authority, knowledge, physical, clerical or exception.

No input schema was published for this tool.

economicsDeclared costs and goal values: attention value per hour, recurring and purchase costs, what each goal is worth.

Declared costs and goal values: attention value per hour, recurring and purchase costs, what each goal is worth.

No input schema was published for this tool.

goal_valueOne goal's economics (occurrence rate, success value, failure cost), matched by id or name.

One goal's economics (occurrence rate, success value, failure cost), matched by id or name.

No input schema was published for this tool.

opportunitiesRanked changes worth making, from recurring human burden in the ledger priced by attention. by: attention (default), cash, roi, reliability, frontier. budget (dollars): the best combination within it.

Ranked changes worth making, from recurring human burden in the ledger priced by attention. by: attention (default), cash, roi, reliability, frontier. budget (dollars): the best combination within it.

No input schema was published for this tool.

opportunityOne ranked opportunity in full: burden, proposed capability, acquisition, expected effect, payback, confidence.

One ranked opportunity in full: burden, proposed capability, acquisition, expected effect, payback, confidence.

No input schema was published for this tool.

canAsk before running a tool you have not used this session. yes: act. ask: put it to the person. no: do not retry it under another name. Also returns the reason, what is missing and the budget left. Probes nothing. A no files the deficit.

Ask before running a tool you have not used this session. yes: act. ask: put it to the person. no: do not retry it under another name. Also returns the reason, what is missing and the budget left. Probes nothing. A no files the deficit.

No input schema was published for this tool.

roiRealized ROI of an applied proposal: interventions, hours, attention dollars and reliability before and after, against its prediction. Writes the observation back.

Realized ROI of an applied proposal: interventions, hours, attention dollars and reliability before and after, against its prediction. Writes the observation back.

No input schema was published for this tool.

roi_summaryEvery applied proposal's observed hours and dollars saved per year, and forecast accuracy: the cumulative headline.

Every applied proposal's observed hours and dollars saved per year, and forecast accuracy: the cumulative headline.

No input schema was published for this tool.

catalogThe ways to acquire a capability (build, buy, subscribe, delegate, hire) compared by setup, one-time and recurring cost, privacy, verification and rollback.

The ways to acquire a capability (build, buy, subscribe, delegate, hire) compared by setup, one-time and recurring cost, privacy, verification and rollback.

No input schema was published for this tool.

auditThe audit trail: a run end to end, a proposal's steps, approval and result, or one person's approvals and interventions. target: run id, proposal id, human name, or days.

The audit trail: a run end to end, a proposal's steps, approval and result, or one person's approvals and interventions. target: run id, proposal id, human name, or days.

No input schema was published for this tool.

incidentsProbe the hosts the infrastructure manifest names and open an incident run per offline service, with the authority decision for recovery (restart ALLOW, CONFIRM or DENY).

Probe the hosts the infrastructure manifest names and open an incident run per offline service, with the authority decision for recovery (restart ALLOW, CONFIRM or DENY).

No input schema was published for this tool.

incident_resolveClose the open incident run for a service with its outcome. MTTR is the ledger's own elapsed time.

Close the open incident run for a service with its outcome. MTTR is the ledger's own elapsed time.

No input schema was published for this tool.

portfolioAcross imported federation receipts: burden that recurs in several environments, person-specific single points of failure, and (with budget) where spend gains most. Never merges.

Across imported federation receipts: burden that recurs in several environments, person-specific single points of failure, and (with budget) where spend gains most. Never merges.

No input schema was published for this tool.

sinceWhat entered the reachable frontier between two ISO timestamps (default: earliest observation to now), split into acquired and emerged through composition.

What entered the reachable frontier between two ISO timestamps (default: earliest observation to now), split into acquired and emerged through composition.

No input schema was published for this tool.

blockedRecord that a task was blocked by a missing capability. The same deficit hit repeatedly is infrastructure that should exist.

Record that a task was blocked by a missing capability. The same deficit hit repeatedly is infrastructure that should exist.

No input schema was published for this tool.

40 of 40 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

What you, your agents, and your machines can jointly do — and where your own time is going.

Keywords
ai-agentsmcpmcp-servermodelcontextprotocolclaude-codecursoropencodewindsurfclaude-desktopgemini-clicodex-clideveloper-toolsagent-infrastructurecapability-graphdependency-graphai-governancehuman-in-the-loopaudit-logclilocal-first
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-05 — observed resolution, not a publisher declaration.

0 packages resolved · 0 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

This package declares no runtime dependencies.