All servers · Scraping & browsing · Research & knowledge · Payments & accounting
Stipple — Document Verification & Extraction
sh.stipple/openwarrant · v0.3.1
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Can write (some tools are not declared read-only) |
| Capabilities declared | experimental, prompts, resources, tools |
| Tool definitions | 16 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Document forensics: tamper/AI checks, fields, tables, identity, screening, tenders, citations.
Connect
streamable-http · https://www.stipple.sh/mcp
claude mcp add --transport http openwarrant https://www.stipple.sh/mcp{
"mcpServers": {
"openwarrant": {
"url": "https://www.stipple.sh/mcp"
}
}
}Tools as reported by the server
verify_documentForensically inspect a document (PDF or image) for authenticity: tampering signs, AI-generation indicators, arithmetic reconciliation (financial docs), and provenance. USE THIS WHEN someone shares a payslip, bank statement, invoice, receipt, ID, certificate, or contract and asks: is this genuine / rcheck_documentCheap cache-check: has this exact document already been inspected? Hash the file yourself (sha256, lowercase hex) and call this before verify_document to skip a redundant (paid) inspection. Returns {cached, warrant_id, permalink}.get_warrantRetrieve a stored warrant by id (e.g. 'warrant_<hex>') — the full bundle as JSON, or a human-readable Markdown report when as_markdown=True. USE THIS WHEN you have a warrant_id from an earlier verify_document / check_document call and need the FULL evidence — every signal that fired, per-page findinsubmit_feedbackRecord thumbs up/down on a warrant's rating (the engine's precision-flywheel label source). verdict must be 'up' or 'down'; note is optional free text. USE THIS WHEN the ground truth became known after a verify_document call — e.g. the document was later confirmed genuine or fraudulent — so the engiextract_fieldsExtract structured FIELDS from a document (PDF or image) with a vision model. USE THIS WHEN you need specific values OUT of a document — a payslip's gross/net, an invoice's total/ABN, a form's checkboxes, a table's cells — rather than a yes/no about the document. (For "is this genuine?" use verify_dverify_identityRun an Australian identity check over a SET of identity documents. A vision model reads each document (which ID it is, which fields it shows — name/photo/address/signature — and its issue date); a deterministic engine then tallies them against a scheme and reports whether identity is established, ancheck_packCheck whether a SET of documents satisfies a checklist — completeness, cheaply. USE THIS WHEN you have an application / onboarding pack and need "do we have the required documents, and what's still missing?" Each document is CLASSIFIED (one cheap page-1 read — never full field extraction or multi-pascreen_adverse_mediaScreen a person or organisation for ADVERSE MEDIA and SANCTIONS exposure (KYC/AML). PEP lists are not screened: `sanctions.flags.pep` is always false and `sanctions.note` says so. USE THIS WHEN onboarding or due-diligence asks: does this subject appear in negative news (fraud, money laundering, bribdetect_ai_textEstimate the PROBABILITY that a document's text was AI-GENERATED (LLM-written prose). USE THIS WHEN someone shares prose — an essay, cover letter, article, review, application, or report (or a link to one) — and asks: did an AI / ChatGPT write this? is this human-written? detect AI text. Provide theverify_referencesFact-check a document's REFERENCES and CLAIMS — built for AI-generated reports whose citations must be checked before they're trusted. USE THIS WHEN someone shares a report, article, whitepaper, or deep-research export (or a link to one) and asks: is this accurate / legit? are these citations real?check_source_overlapCheck whether text OVERLAPS text published on the public web — a plagiarism-style check: does this text appear elsewhere? was this copied? find the source of this text. Provide the document ONE way: `text` (pasted prose), `url` (a public http(s) link — fetched server-side; that page and its host arefind_tendersSearch open tenders across Australia; New Zealand rows only when you ask for them (jurisdiction=NZ). FREE, within the weekly cap. USE THIS WHEN someone asks what public-sector work is open: "any council drainage tenders in Victoria", "what's closing this month in NSW", "show me federal IT opportunitmatch_tendersRank open tenders against what a company actually does. Free, inside the weekly cap. USE THIS WHEN someone asks which opportunities suit a specific business: "what could we bid for", "is there anything for a civil contractor in Victoria", "find work for acme.com.au". Give `company_url` — a plain domtender_sourcesEvery source we search, what it is allowed to do, and what the last run returned. FREE. USE THIS WHEN someone asks where the data comes from, whether a particular portal is covered, or why a search came back empty. It is the honesty surface: it names sources behind login walls, sources whose robots.buyer_awardsWhat a buyer has awarded, what is ending, and what they plan. FREE. USE THIS WHEN someone asks about a specific buyer before a bid: "who holds Transport for NSW's work", "what is ending soon at Queensland Health", "what does this agency usually pay". Give `buyer` (the organisation name as published)find_signalsSignals: what may be tendered before it is. FREE. USE THIS WHEN someone asks what is coming: "which contracts in Queensland end in the next six months", "what is planned for ICT next quarter", "what is expiring for this buyer". `kind` is one of contract_expiry (a contract ending, with its incumbent)
Repository · Website · JSON · Text for agents · Registry updated 2026-08-29