Spoolis MCP server
com.spoolis/mcpspoolis.comstreamable-httpv0.1.9Scanned
Verify AI work against criteria and get signed receipts. From Spoolis, guarantees for AI work.
32 tools: 1 can delete or cancel things, 1 do something that can't be undone, 21 change things and 9 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 5 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Spoolis MCP server can do
The Spoolis MCP server is published by spoolis.com, a domain the MCP Registry verified. It has 32 tools. It can delete or cancel things (1 tool: cancel_spool), do things that cannot be undone, such as sending, paying or publishing (commit_payment) and create or change data (21 tools: verify_result, run_sandbox_scenario, compile_spool, create_spool and 17 more). 9 tools only read.
3 tools bring in text other people can write (verify_result, get_review and verify_spool).
The fixed checks matched 5 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 0.1.9.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
32 tools
Deletes or cancels 1Claude Code: deny
cancel_spoolCancel a Spool (the agreement object) that should not continue.1 finding
Why it is in this group
- The name "cancel_spool" says "cancel": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "cancel_spool" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "cancel_spool" says "cancel": a word for removing or ending something.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Can't be undone 1Claude Code: ask
commit_paymentAsk the configured settlement adapter to authorize and, where supported, hold the maximum value for a Spool (the agreement object).No findings
Why it is in this group
- The name "commit_payment" says "commit": a word for a change.
- The name "commit_payment" also says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Changes things 21Claude Code: ask
abandon_spoolAbandon an active Spool (the agreement object) before payment is committed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
accept_spoolConfirm the compiled contract by accepting a proposed Spool (the agreement object).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
add_sourceAdd a source connection for a Spool (the agreement object).No findings
Why it is in this group
- The name "add_source" says "add": a word for a change.
Description, as the server wrote it Add 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
amend_spoolChange acceptance criteria or unit-based earned-value rules on a proposed Spool (the agreement object).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
compile_spoolTurn purchase intent into a proposed DRAFT Spool (the agreement object) with explicit acceptance criteria and earned-value rules.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
complete_spoolRead a Spool (the agreement object) whose outcome is already completed.1 finding
Why it is in this group
- The description's first verb is "read": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "complete_spool" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
create_counterparty_inviteCreate a 15-minute, single-use grant that lets the other party join a Spool (the agreement object).1 finding
Why it is in this group
- The name "create_counterparty_invite" says "create": a word for a change.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...se as payment authority. This creates a credential that expires after use or 15 minutes. R..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
create_spoolCreate a production Spool (the agreement object) from structured terms and acceptance criteria.No findings
Why it is in this group
- The name "create_spool" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
decide_reviewDecide a pending review for a Spool (the agreement object).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Decide 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 available in the no-key sandbox.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
decline_spoolDecline a proposed Spool (the agreement object).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
open_discrepancyOpen a discrepancy for a Spool (the agreement object).No findings
Why it is in this group
- The name "open_discrepancy" says "open": a word for a change.
Description, as the server wrote it Open 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 SPOOLIS_API_KEY; not available in the no-key sandbox.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
open_disputeOpen a dispute for a Spool (the agreement object).No findings
Why it is in this group
- The name "open_dispute" says "open": a word for a change.
Description, as the server wrote it Open 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 only: set SPOOLIS_API_KEY; not available in the no-key sandbox.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
propose_spoolMove a draft Spool (the agreement object) into the proposed state so the counterparty can review it.No findings
Why it is in this group
- The description's first verb is "move": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
request_reviewRoute receipt units from a Spool (the agreement object) or its whole outcome to a named reviewer.No findings
Why it is in this group
- The name "request_review" says "request": a word for a change.
Description, as the server wrote it Route 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 only: set SPOOLIS_API_KEY; not available in the no-key sandbox.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
resolve_discrepancyResolve a discrepancy for a Spool (the agreement object).1 finding
Why it is in this group
- The name "resolve_discrepancy" says "resolve": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "resolve_discrepancy" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "resolve_discrepancy" says "resolve": a word for reading.
Description, as the server wrote it Resolve 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 the no-key sandbox.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
run_matchingRun matching for a Spool (the agreement object).No findings
Why it is in this group
- The name "run_matching" says "run": a word for a change.
Description, as the server wrote it Run 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
run_sandbox_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.No findings
Why it is in this group
- The name "run_sandbox_scenario" says "run": a word for a change.
Description, as the server wrote it 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, external_judge_two_consumers, qualified_meetings, production_migration, review_and_dispute, and sources_and_matching. This persists only run parameters and aggregate results; modeled economics are labeled modeled. commercial_state opens and resolves a blocking discrepancy, proving the Outcome moves from uncertain back to accepted. Works in the no-key sandbox.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
submit_evidenceAttach fulfillment evidence to an acceptance criterion in a Spool (the agreement object).No findings
Why it is in this group
- The name "submit_evidence" says "submit": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
sync_sourceSync a source for a Spool (the agreement object).No findings
Why it is in this group
- The name "sync_source" says "sync": a word for a change.
Description, as the server wrote it Sync 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
verify_resultGet a signed, durable, portable Outcome Receipt: a verdict artifact, per unit for unitized work, another system can fetch and independently verify.Reads text others write1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "verify_result" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
verify_spoolIssue a signed, durable, portable Outcome Receipt from this Spool, the versioned acceptance policy.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Only reads 9Show 9 read-only tools
get_disputeRead a dispute for a Spool (the agreement object).No findings
Why it is in this group
- The name "get_dispute" says "get": a word for reading.
Description, as the server wrote it Read 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 available in the no-key sandbox.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_receipt_statusCheck whether an Outcome Receipt is still current or has been superseded, before acting on it.No findings
Why it is in this group
- The name "get_receipt_status" says "get": a word for reading.
Description, as the server wrote it Check 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; not available in the no-key sandbox.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_reviewRead the review request for a Spool (the agreement object).Reads text others writeNo findings
Why it is in this group
- The name "get_review" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_review" says "get" and "review": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "read" and "review": it reads comments, which other people can write.
Description, as the server wrote it Read 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_spoolRead a Spool (the agreement object), including hash-covered evidence requirements, dispute policy, and salted unit identity configuration.No findings
Why it is in this group
- The name "get_spool" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_spool_eventsRead the canonical audit history for a Spool (the agreement object), including agreement, fulfillment, verification, and settlement events.No findings
Why it is in this group
- The name "get_spool_events" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_discrepanciesRead discrepancies for a Spool (the agreement object).No findings
Why it is in this group
- The name "list_discrepancies" says "list": a word for reading.
Description, as the server wrote it Read 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_factsRead typed facts for a Spool (the agreement object).No findings
Why it is in this group
- The name "list_facts" says "list": a word for reading.
Description, as the server wrote it Read 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_matchesRead matches for a Spool (the agreement object).No findings
Why it is in this group
- The name "list_matches" says "list": a word for reading.
Description, as the server wrote it Read 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_sourcesRead source connections for a Spool (the agreement object).No findings
Why it is in this group
- The name "list_sources" says "list": a word for reading.
Description, as the server wrote it Read 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:47 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 23
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://spoolis.com/.well-known/oauth-protected-resource
- Authorization servers
- https://clerk.spoolis.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 23 tools that change things (1 destructive, 1 irreversible, 21 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://spoolis.com/api/mcp: tools/list returned 32 tools to an anonymous client, including cancel_spool (destructive), commit_payment (irreversible), verify_result (write), run_sandbox_scenario (write), compile_spool (write) and 18 more
Findings
Matches of fixed checks, with the text they matched.
- Warnverify_result
The server marks "verify_result" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "get": a word for reading.
The server marks "resolve_discrepancy" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "resolve_discrepancy" says "resolve": a word for reading.
- Warncancel_spool
The server marks "cancel_spool" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "cancel_spool" says "cancel": a word for removing or ending something.
- Warncomplete_spool
The server marks "complete_spool" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "read": a word for reading.
The description mentions "credential".
What this check looks forMatched text
description: "...se as payment authority. This creates a credential that expires after use or 15 minutes. R..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.9. Values in angle brackets are yours to fill in.
claude mcp add --transport http spoolis https://spoolis.com/api/mcpclaude mcp add --transport http spoolis https://spoolis.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__spoolis__get_spool",
"mcp__spoolis__get_receipt_status",
"mcp__spoolis__get_review",
"mcp__spoolis__get_dispute",
"mcp__spoolis__list_discrepancies",
"mcp__spoolis__list_sources",
"mcp__spoolis__list_facts",
"mcp__spoolis__list_matches",
"mcp__spoolis__get_spool_events"
],
"ask": [
"mcp__spoolis__verify_result",
"mcp__spoolis__run_sandbox_scenario",
"mcp__spoolis__compile_spool",
"mcp__spoolis__create_spool",
"mcp__spoolis__request_review",
"mcp__spoolis__decide_review",
"mcp__spoolis__open_dispute",
"mcp__spoolis__open_discrepancy",
"mcp__spoolis__resolve_discrepancy",
"mcp__spoolis__add_source",
"mcp__spoolis__sync_source",
"mcp__spoolis__run_matching",
"mcp__spoolis__create_counterparty_invite",
"mcp__spoolis__propose_spool",
"mcp__spoolis__accept_spool",
"mcp__spoolis__amend_spool",
"mcp__spoolis__abandon_spool",
"mcp__spoolis__decline_spool",
"mcp__spoolis__commit_payment",
"mcp__spoolis__submit_evidence",
"mcp__spoolis__verify_spool",
"mcp__spoolis__complete_spool"
],
"deny": [
"mcp__spoolis__cancel_spool"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as spoolis. Review it before you use it.
Capability tags behind 3 rules
- mcp__spoolis__verify_result untrusted-input
- mcp__spoolis__get_review untrusted-input
- mcp__spoolis__verify_spool untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.spoolis/mcp/verify?hash=0b5c96d6392f918d7eb6a1906b2a29a293ca24838577b92e67084aba45924189" | jq -e '.changed == false'Pinned hash 0b5c96d6392f, from Nov 14, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.spoolis/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.spoolis/mcp)Source: MCP Registry. Synced Oct 21, 2026, 18:05 UTC.
Spoolis MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Spoolis MCP server safe?
- No scan can promise that. What its definitions show: 32 tools, 23 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Spoolis MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_spool.
Can the Spoolis MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: commit_payment.
What tools does the Spoolis MCP server have?
- 32 tools: 1 destructive, 1 irreversible, 21 write, 9 read. cancel_spool, commit_payment, verify_result, run_sandbox_scenario, compile_spool, create_spool, request_review, decide_review and 24 more.
Does the Spoolis MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Spoolis MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Spoolis MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.