# OpenWarrant — Reference Verification (remote · www.stipple.sh)

Fact-check citations: resolve, match, support claims; math rechecked. No API key — URL in.

- Trust score: 63/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.stipple.sh`: 63/100 (this document), [markdown](https://verifymcp.io/servers/sh-stipple-openwarrant-verify/mcp-verify.md), [page](https://verifymcp.io/servers/sh-stipple-openwarrant-verify/mcp-verify)

## Channel facts

- Endpoint: `https://www.stipple.sh/mcp-verify`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 538 tokens (~538/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.sh-stipple-openwarrant-verify]
url = "https://www.stipple.sh/mcp-verify"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sh-stipple-openwarrant-verify": {
      "type": "remote",
      "url": "https://www.stipple.sh/mcp-verify",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sh-stipple-openwarrant-verify --url https://www.stipple.sh/mcp-verify --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sh-stipple-openwarrant-verify:
    url: "https://www.stipple.sh/mcp-verify"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (1)

### `verify_references` (~405 tokens)

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 any AI-written document.

    Provide the document ONE way: `url` (a public http(s) link to a PDF or web page — fetched
    server-side, the cheapest call: no need to download or encode anything), `text` (pasted
    markdown/plain prose), OR `bytes_b64` (a base64 PDF; URLs are read from the PDF's link
    annotations, so they're exact). Default (fast): provenance (is it a ChatGPT deep-research
    export?), citation resolution (live / archived / dead, papers matched against arXiv/Crossref
    to catch 'real ID, wrong paper'), and internal MATH (recompute the doc's own arithmetic).
    Set `deep=true` to also fetch each cited source and judge whether it SUPPORTS or CONTRADICTS
    the claim (slower, ~a minute).

    Returns a trust summary, per-item tables, and a shareable `permalink` to the public
    fact-check record. HONEST BOUNDARY: this reports verification COVERAGE, not truth —
    'supported' means evidence-backed (not necessarily true) and 'unsupported' means no evidence
    found (not necessarily false). It tells a reviewer WHERE to look; it does not bless the
    document, and it never affects the fraud risk band.

Input parameters:

- `bytes_b64`
- `deep` (boolean)
- `filename` (string)
- `text`
- `url`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sh-stipple-openwarrant-verify/mcp-verify#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 59
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://www.stipple.sh/mcp-verify
- Repository: https://github.com/Sketchjar/openwarrant
- Changelog RSS feed: https://verifymcp.io/servers/sh-stipple-openwarrant-verify/mcp-verify/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/sh-stipple-openwarrant-verify/mcp-verify/changelog.json
- HTML version of this page: https://verifymcp.io/servers/sh-stipple-openwarrant-verify/mcp-verify