Spoolis by spoolis.com

MCP server · indexed, not reviewed

HostedLocalvendor's own

Not reviewed

No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.

How the index works

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

What the official MCP registry says

Facts

MCP registry
com.spoolis/mcp · 0.1.8
Endpoint
https://spoolis.com/api/mcp
Packages
npm @spoolis/mcp stdio
npm / week
45
Registry entry
updated 11 Sep 2026

From the official MCP registry, the package registries and our own checks. JSON · Markdown

Why it's listed

  • It's published in the registry under spoolis.com, a namespace the registry only gives to whoever proves they control that domain.

Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.

Tools it lists 32 · about 12,695 tokens of context · checked 58 minutes ago

ToolWhat it doesHint
verify_resultResult verificationGet 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…writes
run_sandbox_scenarioSandbox scenarioEvaluate 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…writes
compile_spoolSpool draftTurn 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…writes
create_spoolSpool creationCreate 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…writes
get_spoolSpool detailsRead 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…read-only
get_receipt_statusOutcome Receipt statusCheck whether an Outcome Receipt is still current or has been superseded, before acting on it. Returns state (current, superseded, unknown) and status (active, corrected, revoked). Production only: set SPOOLIS_API_KEY;…read-only
request_reviewReview requestRoute receipt units from a Spool (the agreement object) or its whole outcome to a named reviewer. Use when a human decision is required; this creates a review request and hosted link but does not decide it. Production…writes
get_reviewReview detailsRead the review request for a Spool (the agreement object). Use to poll its state; it has no side effects. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.read-only
decide_reviewReview decisionDecide a pending review for a Spool (the agreement object). Use after inspecting its evidence; this records confirmation or creates a dispute and does not settle payment. Production only: set SPOOLIS_API_KEY; not…writes
open_disputeDispute openingOpen a dispute for a Spool (the agreement object). Use inside its declared window; this records counter-evidence and marks policy-defined value as not currently final or payable. It does not restrict money. Production…writes
get_disputeDispute detailsRead a dispute for a Spool (the agreement object). Use to inspect claimed, accepted, disputed, final, and payable figures plus resolution state; it has no side effects. Production only: set SPOOLIS_API_KEY; not…read-only
list_discrepanciesDiscrepancy listRead discrepancies for a Spool (the agreement object). Use for inspecting differences; it has no side effects. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.read-only
open_discrepancyDiscrepancy openingOpen a discrepancy for a Spool (the agreement object). Use when expected and observed figures do not reconcile; this records the difference and does not assume either source is wrong. Production only: set…writes
resolve_discrepancyDiscrepancy resolutionResolve a discrepancy for a Spool (the agreement object). Use after authority determines the outcome; this records the resolution and does not initiate settlement. Production only: set SPOOLIS_API_KEY; not available in…writes
list_sourcesSource listRead source connections for a Spool (the agreement object). Use for source health inspection; it has no side effects. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.read-only
add_sourceSource additionAdd a source connection for a Spool (the agreement object). Use before ingestion; this creates a connection and does not ingest evidence. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.writes
sync_sourceSource syncSync a source for a Spool (the agreement object). Use after configuration; this creates an idempotent checkpointed job. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.writes
list_factsFact listRead typed facts for a Spool (the agreement object). Use to inspect observed evidence; it has no side effects. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.read-only
run_matchingMatching runRun matching for a Spool (the agreement object). Use after claims and facts exist; this records explainable results and discrepancies. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.writes
list_matchesMatch listRead matches for a Spool (the agreement object). Use to inspect outcomes and explanations; it has no side effects. Production only: set SPOOLIS_API_KEY; not available in the no-key sandbox.read-only
create_counterparty_inviteCounterparty inviteCreate 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…writes
propose_spoolSpool proposalMove 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.…writes
accept_spoolSpool acceptanceConfirm 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…writes
amend_spoolSpool amendmentChange 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…writes
abandon_spoolSpool abandonmentAbandon 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.writes
decline_spoolSpool declineDecline 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…writes
cancel_spoolSpool cancellationCancel 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…writes
commit_paymentPayment commitmentAsk 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…writes
submit_evidenceEvidence submissionAttach 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…writes
verify_spoolSpool verificationIssue 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.…writes
complete_spoolCompleted SpoolRead 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…writes
get_spool_eventsSpool event historyRead 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…read-only

What https://spoolis.com/api/mcp answered to tools/list, asked without credentials over MCP 2025-11-25. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.

How its tools read to an agent 0 errors · 38 warnings · 1 note

  • warnTC11abandon_spoolits one parameter, id, has no description
  • warnTC11accept_spoolnone of its 2 parameters has a description
  • warnTC11add_sourcenone of its 8 parameters has a description
  • warnTC11amend_spoolnone of its 4 parameters has a description
  • warnTC11cancel_spoolits one parameter, id, has no description
  • warnTC11commit_paymentits one parameter, id, has no description
  • warnTC11compile_spoolits one parameter, source, has no description
  • warnTC11complete_spoolits one parameter, id, has no description
  • warnTC11create_counterparty_inviteits one parameter, id, has no description
  • warnTC11create_spoolnone of its 12 parameters has a description
  • warnTC11decide_reviewnone of its 4 parameters has a description
  • warnTC11decline_spoolits one parameter, id, has no description
  • warnTC11get_disputeits one parameter, dispute_id, has no description
  • warnTC11get_receipt_statusits one parameter, receipt_id, has no description
  • warnTC11get_reviewits one parameter, review_id, has no description
  • warnTC11get_spoolits one parameter, id, has no description
  • warnTC11get_spool_eventsits one parameter, id, has no description
  • warnTC11list_discrepanciesits one parameter, id, has no description
  • warnTC11list_factsits one parameter, id, has no description
  • warnTC11list_matchesits one parameter, id, has no description
  • warnTC11open_discrepancynone of its 9 parameters has a description
  • warnTC11open_disputenone of its 4 parameters has a description
  • warnTC11propose_spoolits one parameter, id, has no description
  • warnTC11request_reviewnone of its 5 parameters has a description

The first 24 of 39; every finding is in the listing's JSON under mcpTools.check.

The checks from /check and anchor check, run each day on the list above: about 12,695 tokens of definitions. Not part of the score yet. Check your own server.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.