Stipple — AI Text Detection
REMOTE · WWW.STIPPLE.SH · SCANNED SEP 25
Is this prose AI-written? A probability with the tells behind it. Free to start, no key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 455 tokens (~455/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Stipple — AI Text Detection MCP server?
Stipple — AI Text Detection is a hosted endpoint at https://www.stipple.sh/mcp-aitext, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.stipple.sh
claude mcp add --transport http sh-stipple-openwarrant-aitext 'https://www.stipple.sh/mcp-aitext'
{
"mcpServers": {
"sh-stipple-openwarrant-aitext": {
"url": "https://www.stipple.sh/mcp-aitext"
}
}
} {
"servers": {
"sh-stipple-openwarrant-aitext": {
"type": "http",
"url": "https://www.stipple.sh/mcp-aitext"
}
}
} [mcp_servers.sh-stipple-openwarrant-aitext] url = "https://www.stipple.sh/mcp-aitext"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sh-stipple-openwarrant-aitext": {
"type": "remote",
"url": "https://www.stipple.sh/mcp-aitext",
"enabled": true
}
}
} openclaw mcp add sh-stipple-openwarrant-aitext --url 'https://www.stipple.sh/mcp-aitext' --transport streamable-http
mcp_servers:
sh-stipple-openwarrant-aitext:
url: "https://www.stipple.sh/mcp-aitext" {
"McpServers": {
"sh-stipple-openwarrant-aitext": {
"Transport": "http",
"Url": "https://www.stipple.sh/mcp-aitext"
}
}
} assistant mcp add sh-stipple-openwarrant-aitext -t streamable-http -u 'https://www.stipple.sh/mcp-aitext'
{
"mcpServers": {
"sh-stipple-openwarrant-aitext": {
"type": "http",
"url": "https://www.stipple.sh/mcp-aitext"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 591 → 455 ▲ functional
- 9 Sept 26 +7
- Judged manipulation: unverified → pass ▲ security
- Schema quality: unverified → good ▲ functional
- 8 Sept 26 −6
- Judged manipulation: pass → unverified ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 498 → 591 ▼ functional
- Schema quality: good → unverified ▼ functional
- 1 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 30 Aug 26 0
- Tool “detect_ai_text” changed its title: Detect AI-written prose cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://www.stipple.sh/mcp-aitext
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.stipple.sh | CN=WR3,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 71d7bab9e173bbd1067733485f73929 |
| SANs: www.stipple.sh | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.stipple.sh. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 55297 | 8 | Verified |
| stipple.sh. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.stipple.sh/mcp-aitext | Verified | 200 | |
| http (plaintext) | http://www.stipple.sh/mcp-aitext | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
detect_ai_text Detect AI-written prose ~304
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bytes_b64 | – | – | – |
| filename | string | – | – |
| text | – | – | – |
| url | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Stipple — AI Text Detection MCP server?
Stipple — AI Text Detection is an MCP server listed in the public MCP registry as sh.stipple/openwarrant-aitext. Is this prose AI-written? A probability with the tells behind it. Free to start, no key. This page covers its hosted endpoint (https://www.stipple.sh/mcp-aitext).
Is the Stipple — AI Text Detection MCP server safe to use?
Stipple — AI Text Detection scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Stipple — AI Text Detection MCP server expose?
Stipple — AI Text Detection exposes 1 tool: detect_ai_text. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.
Does the Stipple — AI Text Detection MCP server require authentication?
No. We connected to Stipple — AI Text Detection without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Stipple — AI Text Detection MCP server still maintained?
Stipple — AI Text Detection is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.