Stipple — AI Text Detection

sh.stipplePublished by stipple.shOfficial publisherv0.1.7Updated Nov 2, 2026

Is this prose AI-written? A probability with the tells behind it. Free to start, no key.

The publisher's own server: Stipple - Government Tenders and Grants

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Stipple's hosted MCP server exposes a detect_ai_text tool that estimates the probability a piece of prose was written by an AI, with the linguistic tells…

What you can do
  • Estimate whether prose was AI-generated, returning a probability plus the linguistic tells behind it, and abstaining on non-prose text.
  • Submit an essay, cover letter, article, review, application or report, or a link to one, and ask whether an AI wrote it.
  • The same hosted server also offers document authenticity checks, field extraction, identity and screening tools, tender search and reference verification, though this listing declares only the AI-text tool.
When to use it
Useful when someone shares prose and asks whether it was AI-written or human-written, for example reviewing submissions, applications or published articles. It gives a style-based signal, not a verdict.
Requirements
A remote Streamable HTTP endpoint at the www host of stipple.sh; no install, signup or API key is required for the anonymous free tier. An optional free API key can be sent as an Authorization Bearer header for a private credit allowance.
Before you install
The result is a probability based on style, not proof of authorship, so it should not be treated as calibrated truth or used as the sole basis for a decision about a person. Submitting documents sends their text to a third-party service; identical content is cached by hash. Some other tools on the same server are described as paid.

Installation

In SourceWeft

  1. Open Stipple — AI Text Detection in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/sh.stipple%2Fopenwarrant-aitext/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "stipple-ai-text-detection": {
      "type": "http",
      "url": "https://www.stipple.sh/mcp-aitext"
    }
  }
}

README

Stipple MCP server

Documents in. Answers your agents can act on.

Stipple is a hosted MCP server for document work: forensic authenticity signals, structured field extraction, Australian identity checks, adverse-media and sanctions screening, AU/NZ government tender search, AI-written-text detection, and citation verification for research reports.

No install, no signup — an anonymous free tier works immediately.

Connect

bash
claude mcp add --transport http stipple https://www.stipple.sh/mcp

Or in any MCP client config:

json
{ "mcpServers": { "stipple": { "type": "http", "url": "https://www.stipple.sh/mcp" } } }
  • Endpoint: https://www.stipple.sh/mcp (Streamable HTTP)
  • Always the www. host — the apex domain redirects, and a POST through the redirect fails for non-browser clients.
  • Auth: none required. An optional free API key (POST /v1/keys) gives a private credit allowance; send it as Authorization: Bearer stp_....

Tools (13)

ToolWhat it doesWhat it is NOT
verify_documentForensic authenticity inspection of a PDF/image (URL or base64): risk_band + inspection_quality + evidenceA fraud verdict — it is a signal with the evidence behind it
extract_fieldsStructured fields from a document: ad-hoc field lists, templates (payslip, tax invoice, bank statement, receipt, contract), tables, per-value grounding, redaction, layout, chunking, splittingA judgment — values are what the document shows; absences come back in not_found
verify_identityAustralian identity check over a document set: AFP 100-point or AUSTRAC safe-harbour, with exactly what is missingA forgery check — pair with verify_document
check_packDoes a document set satisfy a checklist (named scheme or ad-hoc requirements)?Approval — presence of the right types, not genuineness
screen_adverse_mediaAdverse media + corroboration-gated sanctions/PEP screening of a person or organisationA determination — "review", never "guilty"; "nothing found" is not a clean record
find_tendersFree. Search open AU/NZ government tenders—
match_tendersRank open tenders against what a company's own website says it does, with why[] and gaps[]A win probability
tender_sourcesFree. Where tender data comes from, and why a search can be empty—
detect_ai_textProbability a document's prose is AI-written, with the linguistic tells; abstains on non-proseCalibrated truth — and style, not authenticity
verify_referencesFor a report: citations resolve and match, internal arithmetic recomputes, unsupported claims flaggedA truth verdict — it reports verification coverage
check_documentHas this exact file (sha256) been inspected already? Skips a paid call—
get_warrantFetch a stored result bundle (JSON or Markdown)—
submit_feedbackThumbs up/down on a rating—

Prompts (8)

Guided workflows shipped with the server: Verify a document's authenticity · What kind of document is this? · Run a 100-point identity check · Screen a person for adverse media · Find tenders my company could bid for · Was this written by AI? · Fact-check a report URL · Fact-check pasted text.

How results read

Every inspection reports two independent axes: risk_band (how authentic the document looks) and inspection_quality (how completely it could be inspected). A clean phone photo of a real payslip is commonly low risk + limited quality — "nothing looks tampered, but we couldn't read everything". Low coverage is not risk.

Identical documents are cached by content hash — resubmitting the same bytes returns the stored result instantly and free.

Credits

Anonymous callers share a free weekly allowance per IP. A free API key gets its own allowance and metering. Tender search and source listing cost nothing. Details: stipple.sh/pricing.

Also available

  • REST API — the same engines at /v1/*; OpenAPI contract at /openapi.json
  • Agent docs — /agents.md (short form /llms.txt)
  • Scoped servers — /mcp-aitext (AI-text detection only) and /mcp-verify (reference verification only), for installs that want a single tool

Operated by Stipple AI Pty Ltd · Privacy · Terms

Source: README.md at commit b0cc70c

Tools

1

detect_ai_text

Detect AI-written prose

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) link to a page or PDF — fetched server-side, the cheapest call), OR `bytes_b64` (a base64 PDF/file, plus `filename` for routing). Returns `{probability, lean, tells, reasoning, applicable}`. HONEST SCOPE: the probability is the model's CONFIDENCE, not a calibrated truth — it can false-flag templated/coached or non-native-English writing. It works on PROSE only: for a form/table/numeric document (payslip, statement) it returns `applicable: false` and abstains, because AI-text detection false-positives badly there — use `verify_document` (the authenticity engine) for those, and `verify_references` to check a doc's citations/claims.

Parametersurltextfilenamebytes_b64

Version history

1
  1. v0.1.7LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Stipple integrations