Home / MCP registry index / com.spoolis/mcp
Spoolis
com.spoolis/mcp in the official MCP registry.
Endpoint https://spoolis.com/api/mcp.
The registry describes it as: Verify AI work against criteria and get signed receipts. From Spoolis, guarantees for AI work.
We read its 32 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
verify_result run_sandbox_scenario compile_spool create_spool get_spool get_receipt_status request_review get_review decide_review open_dispute get_dispute list_discrepancies open_discrepancy resolve_discrepancy list_sources add_source sync_source list_facts run_matching list_matches create_counterparty_invite propose_spool accept_spool amend_spool abandon_spool decline_spool cancel_spool commit_payment submit_evidence verify_spool complete_spool get_spool_events
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-spoolis-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.