MCP integration
One hosted MCP server gives your agent the full Stipple suite — document forensics, financial classification, AI-text detection, and citation fact-checking — as native tools. No install, no key required.
The server
Everything lives on https://www.stipple.sh/mcp (Streamable HTTP), listed in the official MCP registry as sh.stipple/openwarrant:
| Tool | What it does |
|---|---|
| verify_document | Forensic authenticity inspection — risk band, findings, shareable warrant. |
| classify_document | Financial document-type classification (payslip, invoice, bank statement, …) with country + confidence. |
| detect_ai_text | Probability a document's prose was AI-written, with the tells. |
| verify_references | Citations resolve & match, internal math recomputed, claims judged; returns a public permalink. |
| check_document · get_warrant · submit_feedback | Cache check, warrant retrieval, reviewer feedback. |
Claude Code
claude mcp add --transport http openwarrant https://www.stipple.sh/mcpClaude Desktop / Cursor / generic clients
Add to your client's MCP configuration:
{
"mcpServers": {
"openwarrant": { "type": "http", "url": "https://www.stipple.sh/mcp" }
}
}Scoped servers https://www.stipple.sh/mcp-aitext (AI-text only) and https://www.stipple.sh/mcp-verify (fact-check only) remain available for existing installs — new installs should just use /mcp.
Calling the tools
Every document tool accepts a public url — the cheapest call: one short string, no download or encoding. Inline base64 (bytes_b64) and raw text are also accepted.
# In any connected client, just ask:
"Fact-check this report: https://example.com/report.pdf"
"Did an AI write this? <pasted text>"
"What kind of document is this? <link or file>"
"Is this payslip genuine? <attached file>"verify_references returns a shareable permalink with every result, so an agent can hand its user a public fact-check record. Each server also publishes MCP prompts (ready-made starters like "Fact-check a report URL") that appear natively in clients that support them.
Limits & behavior
- Same per-IP rate limits as the REST API (the tools share one quota).
- Outbound URL fetches are SSRF-guarded: public http(s) hosts only, every redirect re-validated, size-capped.
- Transport is stateless Streamable HTTP with JSON responses — no session affinity required.