# Spoolis (npm · @spoolis/mcp)

Verify work against acceptance criteria; signed receipts attest what passed and was earned.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `spoolis.com`: 79/100, [markdown](https://verifymcp.io/servers/com-spoolis-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-spoolis-mcp/api-mcp)
- npm · `@spoolis/mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-spoolis-mcp/spoolis-mcp.md), [page](https://verifymcp.io/servers/com-spoolis-mcp/spoolis-mcp)

## Channel facts

- Registry: `npm`
- Package: `@spoolis/mcp`
- Version: `0.1.5`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2245 tokens (~124/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Spoolis MCP server?

Spoolis runs locally as an npm package, launched with npx -y @spoolis/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-spoolis-mcp -- npx -y @spoolis/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-spoolis-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@spoolis/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-spoolis-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@spoolis/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-spoolis-mcp -- npx -y @spoolis/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-spoolis-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@spoolis/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-spoolis-mcp --command npx --arg -y --arg @spoolis/mcp
```

### Hermes

```yaml
mcp_servers:
  com-spoolis-mcp:
    command: "npx"
    args: ["-y", "@spoolis/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-spoolis-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@spoolis/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-spoolis-mcp -t stdio -c npx -a -y @spoolis/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-spoolis-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@spoolis/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 74, +1)

- [security] Stability: 0.97 → pass

### 2026-09-22 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 72, +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.

### 2026-09-18 (score 71, +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.

### 2026-09-16 (score 70, +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.

### 2026-09-14 (score 69, +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.

### 2026-09-12 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 53, −14)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.53 → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.4 → 0.1.5

## MCP tools (18)

### `verify_result` (~382 tokens)

Result verification

Get a signed, durable, portable Outcome Receipt: a verdict artifact, per unit for unitized work, another system can fetch and independently verify. Spoolis makes it by verifying returned work against explicit acceptance criteria. Use when an agent, vendor, or tool reports work as done and the next action depends on whether the delivery actually met the agreed criteria. This runs in one call using exactly one of inline conditions or a locally registered recipe slug and hash, creating an inspectable unilateral Spool, the versioned acceptance policy. The maximum amount field is optional for verification-only runs. Omit it when nobody is paying; the earned amount is then zero and the receipt omits committed value. The maximum amount field is required when unit is present because unit math needs the cap. Recipe verification uses the hosted conditions exactly as written and fails closed when the hash differs. The external provider does not accept conditions in Spoolis. For a batch delivery where items can pass, fail, or remain uncertain individually, pass unit (its unit count matching the item count) AND evidence type dataset with exactly one row per delivered item, keeping a field present with a null value when it is missing; that returns distinct per-unit verdicts and earned value only for passing units. Text evidence with unit is batch-only and settles all-or-nothing. For a keyless production alternative, use POST /api/v1/verify/x402. Sandbox dataset evidence is limited to 100 records. Works in the no-key sandbox.

Input parameters:

- `conditions` (string|array)
- `evidence` (object, required)
- `gated_action` (string)
- `gated_action_note` (string)
- `idempotency_key` (string)
- `max_amount_cents` (integer)
- `recipe` (object)
- `settlement` (string)
- `unit` (object)

### `run_sandbox_scenario` (~264 tokens)

Sandbox scenario

Evaluate Spoolis without a key or account: run a seeded synthetic scenario through a real demo Spool (the agreement object), verification, and a signed demo Outcome Receipt. Use to observe which units may continue after verification and inspect seeded truth only after the Outcome exists. Scenarios: data_enrichment runs a synthetic company-enrichment delivery with configurable defect and adversarial rates and returns per-unit verdicts with partial earned value; external_judge_two_consumers walks a signed external evaluator judgment, bound to the agreement and evidence, through one shared Outcome consumed independently by billing and workflow, then shows tamper rejection and missing-unit uncertainty; qualified_meetings runs ten vendor-reported meetings through buyer acceptance criteria and returns seven accepted, two rejected, and one uncertain with a signed receipt; production_migration verifies local delivery checks plus buyer-owned billing telemetry through the external evaluator path, then shows deploy blocking and remediation. This persists only run parameters and aggregate results; modeled economics are labeled modeled. Works in the no-key sandbox.

Input parameters:

- `adversarial_case_count` (integer)
- `defect_rate` (number)
- `modeled_cost_per_unit` (number)
- `record_count` (integer)
- `scenario` (string, required)
- `seed` (string)

### `compile_spool` (~96 tokens)

Spool draft

Turn purchase intent into a proposed DRAFT Spool (the agreement object) with explicit acceptance criteria and earned-value rules. Use before both parties confirm terms; do not use for one-call unilateral result verification. This creates a persisted draft to inspect, then accept_spool confirms it, amend_spool changes conditions or unitization, and abandon_spool discards it. Works in the no-key sandbox.

Input parameters:

- `source` (string, required)

### `create_spool` (~216 tokens)

Spool creation

Create a production Spool (the agreement object) from structured terms and acceptance criteria. Use when both parties will participate in the agreement lifecycle; do not use for one-call unilateral verification. This persists a proposed agreement and may send the counterparty invite reported in the response handoff block. The type field defaults to the person or business service path, while agent selects the agent settlement rail. Conditions may declare verification_method third_party with an external_judge so verification consumes your own evaluator's bound result instead of Spoolis judging those conditions. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.

Input parameters:

- `agreement` (object)
- `conditions` (array, required)
- `deliverable` (object, required)
- `dispute_policy` (object)
- `economics` (object)
- `gated_action` (string)
- `gated_action_note` (string)
- `parties` (array, required)
- `terms` (array, required)
- `type` (string)
- `value` (object, required)

### `get_spool` (~98 tokens)

Spool details

Read a Spool (the agreement object), including hash-covered evidence requirements, dispute policy, and salted unit identity configuration. Use for status checks; it has no side effects. A party named in who_may_dispute can supersede an issued receipt through POST /api/v1/receipts/{receipt_id}/supersede. There is no review queue or UI. Works in the no-key sandbox.

Input parameters:

- `id` (string, required)

### `get_receipt_status` (~55 tokens)

Outcome Receipt status

Check whether an Outcome Receipt is still current or has been superseded, before acting on it. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.

Input parameters:

- `receipt_id` (string, required)

### `create_counterparty_invite` (~101 tokens)

Counterparty invite

Create a 15-minute, single-use grant that lets the other party join a Spool (the agreement object). Use when a counterparty needs scoped access without signing in; do not use as payment authority. This creates a credential that expires after use or 15 minutes. Requires the initiator's full-scope key. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.

Input parameters:

- `id` (string, required)

### `propose_spool` (~77 tokens)

Spool proposal

Move a draft Spool (the agreement object) into the proposed state so the counterparty can review it. Use after the acceptance criteria are ready; this changes agreement state and does not accept terms or settle payment. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.

Input parameters:

- `id` (string, required)

### `accept_spool` (~78 tokens)

Spool acceptance

Confirm the compiled contract by accepting a proposed Spool (the agreement object). Use only after reviewing its terms and acceptance criteria; this records agreement acceptance but does not verify fulfillment or settle payment. Production agent agreements require the current quote digest. Works in the no-key sandbox.

Input parameters:

- `id` (string, required)
- `quote_digest` (string)

### `amend_spool` (~93 tokens)

Spool amendment

Change acceptance criteria or unit-based earned-value rules on a proposed Spool (the agreement object). Use before acceptance when the draft does not match the intended purchase; this replaces proposal details and does not accept or verify the work. Works in the no-key sandbox.

Input parameters:

- `add_conditions` (array)
- `id` (string, required)
- `remove_condition_ids` (array)
- `unitization` (object)

### `abandon_spool` (~62 tokens)

Spool abandonment

Abandon an active Spool (the agreement object) before payment is committed. Use when the initiator no longer wants to proceed; this ends the agreement and cannot verify work or settle value. Works in the no-key sandbox.

Input parameters:

- `id` (string, required)

### `decline_spool` (~69 tokens)

Spool decline

Decline a proposed Spool (the agreement object). Use when the counterparty rejects its terms; this ends the proposal without accepting it, verifying work, or settling payment. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.

Input parameters:

- `id` (string, required)

### `cancel_spool` (~70 tokens)

Spool cancellation

Cancel a Spool (the agreement object) that should not continue. Use only when cancellation is an allowed action; this changes lifecycle state and does not verify fulfillment or settle payment. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.

Input parameters:

- `id` (string, required)

### `commit_payment` (~90 tokens)

Payment commitment

Ask the configured settlement adapter to authorize and, where supported, hold the maximum value for a Spool (the agreement object). Use after terms are accepted when the selected payment path requires commitment; this may create a payment authorization or hold, but does not verify work or determine earned value. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.

Input parameters:

- `id` (string, required)

### `submit_evidence` (~117 tokens)

Evidence submission

Attach fulfillment evidence to an acceptance criterion in a Spool (the agreement object). Use after work is delivered and before verification; this persists evidence but does not decide whether it passes or what was earned. Works in the no-key sandbox.

Input parameters:

- `claim_class` (string)
- `condition_id` (string, required)
- `id` (string, required)
- `metadata` (object)
- `on_behalf_of` (string)
- `provenance` (string)
- `source` (string, required)
- `type` (string, required)

### `verify_spool` (~210 tokens)

Spool verification

Issue a signed, durable, portable Outcome Receipt from this Spool, the versioned acceptance policy. The receipt is a verdict artifact, per unit for unitized work, another system can fetch and independently verify. Spoolis makes it by evaluating submitted evidence against the acceptance criteria and determining what was earned. Use after evidence is attached; this records the verdict and required evidence as present, missing, stale, unavailable, or provenance unsatisfied. Missing required evidence defaults to uncertain. Conditions with verification_method third_party keep your own judge: verification consumes the declared external evaluator's result, bound to this agreement and evidence per its declared proof requirement, instead of Spoolis judging those conditions itself. Unitized receipts may include salted public unit identities. Sandbox dataset evidence is limited to 100 records. Canonical recipe: compile -> verify -> Outcome Receipt -> verifyReceipt -> optional status check -> consumer acts on earned. Works in the no-key sandbox.

Input parameters:

- `confirmations` (array)
- `id` (string, required)

### `complete_spool` (~72 tokens)

Completed Spool

Read a Spool (the agreement object) whose outcome is already completed. Use for compatibility when a completed result is expected; it has no side effects and does not run verification or settlement. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.

Input parameters:

- `id` (string, required)

### `get_spool_events` (~61 tokens)

Spool event history

Read the canonical audit history for a Spool (the agreement object), including agreement, fulfillment, verification, and settlement events. Use to reconstruct what happened; it has no side effects. Works in the no-key sandbox.

Input parameters:

- `id` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-spoolis-mcp/spoolis-mcp#diagnostics

## Score history

- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 72
- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 69
- 2026-09-14: 69
- 2026-09-13: 68
- 2026-09-12: 68
- 2026-09-11: 53
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 66
- 2026-09-07: 66
- 2026-09-06: 65
- 2026-09-05: 65
- 2026-09-04: 64
- 2026-09-03: 49
- 2026-09-02: 64
- 2026-09-01: 63
- 2026-08-31: 63
- 2026-08-30: 62
- 2026-08-29: 62
- 2026-08-28: 61
- 2026-08-27: 61
- 2026-08-26: 45

## Common questions

### What is the Spoolis MCP server?

Spoolis is an MCP server listed in the public MCP registry as com.spoolis/mcp. Verify work against acceptance criteria; signed receipts attest what passed and was earned. This page covers its npm package (@spoolis/mcp).

### Is the Spoolis MCP server safe to use?

Spoolis scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 Spoolis MCP server expose?

Spoolis exposes 18 tools: verify_result, run_sandbox_scenario, compile_spool, create_spool, get_spool, and 13 more. Their descriptions and schemas cost roughly 2,211 tokens of context every time the server is loaded.

### Is the Spoolis MCP server still maintained?

Spoolis 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 Spoolis MCP server under?

Spoolis declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@spoolis/mcp
- Socket report: https://socket.dev/npm/package/@spoolis/mcp
- Website: https://spoolis.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-spoolis-mcp/spoolis-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-spoolis-mcp/spoolis-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-spoolis-mcp/spoolis-mcp