MCP server for terminal commands, file operations, and process management
Nothing to run from here
Stipple — Document Verification & Extraction is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
16
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Document forensics: tamper/AI checks, fields, tables, identity, screening, tenders, citations.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http stipple-document-verification-extraction-mcp https://www.stipple.sh/mcp
# 2 — ask your agent for something these tools do
# verify_document, check_document, get_warrant and 13 more
Stipple — Document Verification & Extraction costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
STAll 4 servers
stipple4 servers
4 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http stipple-document-verification-extraction-mcp https://www.stipple.sh/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Forensically 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 / real / authentic? has it been edited, doctored, or photoshopped? can I trust this fi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bytes_b64 | no | — | |
| url | no | — | |
| filename | string | no | — |
| fresh | boolean | no | — |
Cheap 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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | — |
Retrieve 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 findings, provenance — rather than the summary the original call returned. Use as_markdow
| Parameter | Type | Required | Notes |
|---|---|---|---|
| warrant_id | string | yes | — |
| as_markdown | boolean | no | — |
Record 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 engine learns from the outcome. Tell it what happened; it sharpens future inspections f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| warrant_id | string | yes | — |
| verdict | string | yes | — |
| note | no | — |
Extract 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_document; "what kind of document is this?" is options={"classify": true} right her
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | no | — | |
| bytes_b64 | no | — | |
| filename | string | no | — |
| fields | no | — | |
| template | no | — | |
| country | no | — | |
| max_pages | no | — | |
| options | no | — | |
| render_scale | no | — |
Run 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, and exactly what's still missing if not. USE THIS WHEN someone needs to verify a pers
| Parameter | Type | Required | Notes |
|---|---|---|---|
| documents | array | yes | — |
| scheme | string | no | — |
Check 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-page), then matched against the checklist's required slots. (For "is a document genui
| Parameter | Type | Required | Notes |
|---|---|---|---|
| documents | array | yes | — |
| scheme | no | — | |
| requirements | no | — |
Screen 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, bribery, sanctions, trafficking, enforcement action), or on a sanctions list? Pairs nat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | no | — | |
| dob | no | — | |
| country | no | — | |
| aliases | no | — | |
| employer | no | — | |
| role | no | — | |
| url | no | — | |
| bytes_b64 | no | — | |
| filename | string | no | — |
Estimate 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 the document ONE way: text (pasted markdown/plain prose), url (a public http(s)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | no | — | |
| url | no | — | |
| bytes_b64 | no | — | |
| filename | string | no | — |
Fact-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? fact-check this. did the AI make this up? Also use it proactively before relying on
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | no | — | |
| url | no | — | |
| bytes_b64 | no | — | |
| filename | string | no | — |
| deep | boolean | no | — |
Check 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 are excluded from matches), OR bytes_b64 (a base64 PDF/.docx/text file, plus `filena
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | no | — | |
| url | no | — | |
| bytes_b64 | no | — | |
| filename | string | no | — |
Search 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 opportunities". For "which of these could MY company actually bid for", use match_tenders instead — that read
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | no | — | |
| jurisdiction | no | — | |
| tier | no | — | |
| source | no | — | |
| category | no | — | |
| closing_before | no | — | |
| first_seen_after | no | — | |
| include_closed | boolean | no | — |
| kind | no | — | |
| limit | integer | no | — |
Rank 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 domain is fine, we resolve it — and we read their site, build a capability profile, an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_url | no | — | |
| example | no | — | |
| jurisdiction | no | — | |
| closing_before | no | — |
Every 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.txt refuses us, and sources that returned nothing on the last run and why.
No parameter schema on file.
What 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) or buyer_key (from a tender's buyer, or a previous answer). Returns `{buyer, expiring[], planne
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buyer | no | — | |
| buyer_key | no | — |
Signals: 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), planned_procurement (a buyer's stated plan with its quarter and spend band as published) or recur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | no | — | |
| jurisdiction | no | — | |
| buyer | no | — | |
| q | no | — | |
| window_before | no | — | |
| limit | integer | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Stipple — Document Verification & Extraction or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.1.
0.3.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Stipple — Document Verification & Extraction can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.