# Stipple — AI Text Detection

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

- name: sh.stipple/openwarrant-aitext
- version: 0.1.7
- connection class: R0 (autonomous)
- trust: 89/100 flags: duplicate-repo
- quality: 82/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/sh.stipple%2Fopenwarrant-aitext
- tools: https://api.protogrid.dev/v1/servers/sh.stipple%2Fopenwarrant-aitext/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "openwarrant-aitext": {
      "type": "http",
      "url": "https://www.stipple.sh/mcp-aitext"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% ~updated-52d-ago -duplicate-repo(4 names)
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 82/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 79 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 1 of 1 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: detect_ai_text (destructiveHint, idempotentHint, openWorldHint)
- pass `tools.token_cost`: about 377 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 1, about 377 tokens to load them all
- tool set hash: 5009b1b72505032bf791188e00877ee6
- badge: [![protogrid quality](https://protogrid.dev/badge/sh.stipple/openwarrant-aitext.svg)](https://protogrid.dev/servers/sh.stipple/openwarrant-aitext)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://www.stipple.sh/mcp-aitext (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (1)

- `detect_ai_text`: 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.