@spoolis/mcp

MCPcommunitylive
v0.1.9com.spoolisMITUpdated 17d agonpm

Verify AI work against criteria and get signed receipts. From Spoolis, guarantees for AI work.

Endpoint healthlive
checked 14 days ago · 516ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). 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 →
42Downloads/wk
17d agoLast update
Reads these credentials
  • SPOOLIS_API_KEYAPI keyoptional

    Optional Spoolis API key. When set, the server uses authenticated production mode.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorcom.spoolis
LicenseMIT
Version0.1.9
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✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv0.1.2 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 25, 2026

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

Tools

10 tools · none privileged
Statically extracted from the published packagev0.1.2 · 1mo 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.

verify_resultVerify a result in one call, creating an inspectable unilateral Spool and signed Outcome Receipt. The external provider does not accept conditions in Spoolis. For a batch delivery where items can pass or fail individually, pass unit (its unit count matching the item count) AND evidence type dataset…

Verify a result in one call, creating an inspectable unilateral Spool and signed Outcome Receipt. The external provider does not accept conditions in Spoolis. For a batch delivery where items can pass or fail individually, pass unit (its unit count matching the item count) AND evidence type dataset…

No input schema was published for this tool.

compile_spoolCompile transaction intent into a proposed DRAFT. Inspect it, then use accept_spool to confirm, amend_spool to change conditions or unitization, or abandon_spool to discard it.

Compile transaction intent into a proposed DRAFT. Inspect it, then use accept_spool to confirm, amend_spool to change conditions or unitization, or abandon_spool to discard it.

No input schema was published for this tool.

create_spoolCreate a production Spool. The type field selects the provider path and defaults to service, the person or business path that requires payout setup before funding; the agent path pays an agent or software provider through the agent settlement rail. The response handoff block says how the counterpar…

Create a production Spool. The type field selects the provider path and defaults to service, the person or business path that requires payout setup before funding; the agent path pays an agent or software provider through the agent settlement rail. The response handoff block says how the counterpar…

No input schema was published for this tool.

get_spoolGet the canonical Spool, including raw status dimensions and allowed actions.

Get the canonical Spool, including raw status dimensions and allowed actions.

No input schema was published for this tool.

create_counterparty_inviteCreate a 15-minute, single-use counterparty grant for an active Spool. Requires the initiator's full-scope key.

Create a 15-minute, single-use counterparty grant for an active Spool. Requires the initiator's full-scope key.

No input schema was published for this tool.

accept_spoolConfirm the compiled contract by accepting its proposed Spool. Production agent Spools require the current quote digest.

Confirm the compiled contract by accepting its proposed Spool. Production agent Spools require the current quote digest.

No input schema was published for this tool.

amend_spoolAmend conditions or unitization on a proposed Spool before confirming it.

Amend conditions or unitization on a proposed Spool before confirming it.

No input schema was published for this tool.

submit_evidenceSubmit evidence for a Spool condition.

Submit evidence for a Spool condition.

No input schema was published for this tool.

verify_spoolRun verification; authenticated v1 returns the Outcome Receipt with its lower-level attestation when signing is configured, while sandbox returns a demo attestation and, for unitized verification, a signed demo Outcome Receipt with units and proportional earned value. Canonical recipe: compile -> v…

Run verification; authenticated v1 returns the Outcome Receipt with its lower-level attestation when signing is configured, while sandbox returns a demo attestation and, for unitized verification, a signed demo Outcome Receipt with units and proportional earned value. Canonical recipe: compile -> v…

No input schema was published for this tool.

get_spool_eventsGet the canonical event history for a Spool.

Get the canonical event history for a Spool.

No input schema was published for this tool.

10 of 10 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

Verify AI work against criteria and get signed receipts. From Spoolis, guarantees for AI work.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

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

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

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.