Forbiz
NPM · FORBIZ-MCP
CRM for AI agents: commitments, expected signals, evidence and outcomes agents resume.
Available components
Last scanned (1 hour ago)
Scores higher than 55% of npm servers
Category CRM and Sales
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 Security98
- 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
- 30 of 92 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 24 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1728 tokens (~86/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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 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.
- 3 Nov 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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +3
- Stability: unverified → 0.27 ▲ 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 5 Nov 2026 · Analysed npm/forbiz-mcp@0.1.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 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
forbiz_action_history History of one action ~41
Chronological changes of one action and who made each one, agent or human (GET /actions/{id}/history).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
forbiz_add_evidence Record evidence ~59
Append what you observed, were told, inferred or decided (POST /context/evidence). Append-only epistemic history: nothing becomes workspace truth automatically, and a contradiction never erases what it contradicts.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
forbiz_agents Agents of this workspace ~63
Every agent of this workspace with its activity and a plain track record over the actions it created: created, executed, signal recorded, outcomes, overdue (GET /agents). Counts only, no ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days, default 30 |
No output schema declared.
No examples provided.
forbiz_check_signal Record a signal check ~155
Record that you looked for the expected signal (POST /actions/{id}/signal-checks). not_found_in_source REQUIRES source and period: it says where you looked and when, never that a third party did not answer. found closes nothing; link the signal with forbiz_record_signal. cannot_check REQUIRES reason.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Action id |
| looked_for | string | – | – |
| note | string | – | – |
| period | object | – | The time window you checked |
| reason | string | – | – |
| result | string | yes | – |
| source | object | – | Where you looked, e.g. { kind: 'email_thread', detail: 'Re: quote' } |
No output schema declared.
No examples provided.
forbiz_claim_link Get the owner's claim link ~43
A link the human owner opens to take ownership of a provisional workspace (POST /claim-link). Give it to the owner; the agent keeps working after the claim.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
forbiz_close Close the loop ~48
Resolve an action with its outcome (POST /actions/{id}/close-loop).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| learningNote | string | – | – |
| outcomeStatus | string | yes | – |
No output schema declared.
No examples provided.
forbiz_close_without_signal Close without a signal ~68
Close an action that will not get a signal, saying why (POST /actions/{id}/close-without-signal). Silence is not rejection: say what you know.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| learningNote | string | – | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
forbiz_commit Record a commitment ~303
Record an action you will take or took, with the signal you expect back (POST /actions). Always send a commitmentKey (a short stable id for the objective, e.g. 'acme/quote-followup') and expectedSignalAt. A second open commitment with the same key is refused 409 COMMITMENT_ALREADY_OPEN and the body returns the open one: that is how you resume. A look-alike is refused 409 POSSIBLE_DUPLICATE: resend with confirm_new true only if it is a different objective.
| Name | Type | Req | Description |
|---|---|---|---|
| commitmentKey | string | – | Stable id of the objective this commitment serves (recommended) |
| confirm_new | boolean | – | Override a POSSIBLE_DUPLICATE refusal |
| description | string | yes | What the action is, in one sentence |
| dueAt | string | – | When the action itself is due; without it the action never becomes overdue |
| expectedSignal | string | – | What you expect to see if it worked, e.g. 'Dana replies with a date' |
| expectedSignalAt | string | – | When the expected signal should have arrived |
| expectedSignalSource | object | – | Where the expected signal will appear |
| projectId | string | – | UUID of an existing project in this workspace |
| roi | object | – | What it is worth, each dimension 0-5. Optional; never inferred by Forbiz |
| verb | string | – | – |
| whyThisMove | string | – | – |
No output schema declared.
No examples provided.
forbiz_find_evidence Find evidence ~75
Recover evidence by text or subject (GET /context/evidence). Each item carries its source and its contradiction and supersession pointers.
| Name | Type | Req | Description |
|---|---|---|---|
| materialOnly | boolean | – | – |
| q | string | – | Full text over subject and content |
| status | string | – | – |
| subject | string | – | Subject contains this |
No output schema declared.
No examples provided.
forbiz_get_action Read one action ~41
Full state of one action: expected signal, dates, lifecycle, outcome (GET /actions/{id}).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Action id |
No output schema declared.
No examples provided.
forbiz_mark_executed Mark an action as executed ~104
Record that the action really happened (POST /actions/{id}/execute). Only when it did: never mark as executed without evidence that the act occurred.
| Name | Type | Req | Description |
|---|---|---|---|
| executedAt | string | – | When it really happened; at most 5 minutes in the future |
| expectedSignalAt | string | – | ISO 8601 date-time, e.g. 2026-10-15T14:00:00Z |
| id | string | yes | – |
No output schema declared.
No examples provided.
forbiz_me Who am I in Forbiz ~32
Workspace, agent identity, capabilities, plan and limits of the current credential (GET /me). Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
forbiz_next Next move ~26
The single next thing that needs attention, with its handoff (GET /next).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
forbiz_postpone Move the expected signal date ~74
Push the date the signal is expected (POST /actions/{id}/postpone).
| Name | Type | Req | Description |
|---|---|---|---|
| expectedSignalAt | string | yes | ISO 8601 date-time, e.g. 2026-10-15T14:00:00Z |
| id | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
forbiz_prompts Queue of pending items ~62
Everything waiting, grouped (needs_decision, needs_feedback, waiting, needs_review_date), each with timing.available_commands: what you may do right now (GET /prompts).
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Only one group, e.g. needs_feedback |
No output schema declared.
No examples provided.
forbiz_record_signal Record the signal that came back ~75
Record what actually happened after the action (POST /signals). A signal is written once; a correction is a new record.
| Name | Type | Req | Description |
|---|---|---|---|
| actionId | string | yes | – |
| actualSignal | string | yes | What actually came back, in plain words |
| learningNote | string | – | – |
| outcomeStatus | string | – | – |
No output schema declared.
No examples provided.
forbiz_request Call any Forbiz route ~109
Escape hatch for any other route of the Forbiz Agent API (https://forbiz.io/openapi.json): projects, decisions, delegations, outreach, policies, export, purchases. The path is relative to the API base, e.g. '/projects' or '/decisions/recommendation'. Forbiz enforces capabilities server-side.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | – |
| method | string | yes | – |
| path | string | yes | Route path starting with / |
| query | object | – | – |
No output schema declared.
No examples provided.
forbiz_search Search Forbiz ~72
Full-text search across actions, evidence, people, organizations, projects, outreach and decisions (GET /search). To resume a commitment by its key, use forbiz_commit with the same commitmentKey instead: the 409 returns it.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Search terms |
| type | string | – | – |
No output schema declared.
No examples provided.
forbiz_start Open a Forbiz workspace ~126
Open a provisional Forbiz workspace with no account, no email and no human (POST /bootstrap). The credential is stored locally by this server and never shown. Returns the workspace, the trial limits and a claim link for the owner. Call it once; if a credential already exists it refuses unless replace is true.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Your name as an agent, e.g. 'Acme ops agent' |
| replace | boolean | – | Open a new workspace even if a credential is already stored |
| workspace_name | string | – | Name of the business or workspace |
No output schema declared.
No examples provided.
forbiz_state Workspace state ~25
Overview of the workspace: queues, counts and next priorities (GET /state).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Forbiz MCP server?
Forbiz runs locally as an npm package, launched with npx -y forbiz-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 · forbiz-mcp
claude mcp add tbernabo-forbiz-mcp -- npx -y forbiz-mcp
What is the Forbiz MCP server?
Forbiz is an MCP server listed in the public MCP registry as io.github.tbernabo/forbiz-mcp. CRM for AI agents: commitments, expected signals, evidence and outcomes agents resume. This page covers its npm package (forbiz-mcp).
Is the Forbiz MCP server safe to use?
Forbiz scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting 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 Forbiz MCP server expose?
Forbiz exposes 20 tools: forbiz_start, forbiz_me, forbiz_claim_link, forbiz_next, forbiz_prompts, and 15 more. Their descriptions and schemas cost roughly 1,601 tokens of context every time the server is loaded.
Is the Forbiz MCP server still maintained?
Forbiz 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 Forbiz MCP server under?
Forbiz declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.