# check-claim (remote · check-claim.amdal-dev.workers.dev)

Check that a source really says what your claim says, before you publish. Verbatim, multi-path.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `check-claim.amdal-dev.workers.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/piiiico-check-claim/check-claim.md), [page](https://verifymcp.io/servers/piiiico-check-claim/check-claim)

## Channel facts

- Endpoint: `https://check-claim.amdal-dev.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## 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-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 282 tokens (~282/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**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the check-claim MCP server?

check-claim is a hosted endpoint at https://check-claim.amdal-dev.workers.dev/mcp, 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.

### Claude

```bash
claude mcp add --transport http piiiico-check-claim 'https://check-claim.amdal-dev.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "piiiico-check-claim": {
      "url": "https://check-claim.amdal-dev.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "piiiico-check-claim": {
      "type": "http",
      "url": "https://check-claim.amdal-dev.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.piiiico-check-claim]
url = "https://check-claim.amdal-dev.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "piiiico-check-claim": {
      "type": "remote",
      "url": "https://check-claim.amdal-dev.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add piiiico-check-claim --url 'https://check-claim.amdal-dev.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  piiiico-check-claim:
    url: "https://check-claim.amdal-dev.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "piiiico-check-claim": {
      "Transport": "http",
      "Url": "https://check-claim.amdal-dev.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add piiiico-check-claim -t streamable-http -u 'https://check-claim.amdal-dev.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "piiiico-check-claim": {
      "type": "http",
      "url": "https://check-claim.amdal-dev.workers.dev/mcp"
    }
  }
}
```

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-10-18 (score 66, +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-10-16 (score 65, +1)

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

### 2026-10-14 (score 64, +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-10-13 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 63)

First indexed and scored.

## MCP tools (1)

### `check_claim` (~260 tokens)

Check a claim against its source

Check whether a source really says what a claim says it says, before you publish the claim. Give the claim and the source (an http(s) URL or arxiv:<id>). Without a quote you get back the source sentences that best match the claim. With quote (a sentence copied verbatim from the source) and stance (supports|contradicts, your judgment), the tool fetches the source on independent paths (origin, reader, web archive; for arXiv: metadata and full text) and returns SUPPORTED or CONTRADICTED only if the quote is found verbatim on at least two of them, else UNVERIFIABLE. A quote that is not in the source is reported as QUOTE NOT IN SOURCE, with the nearest real sentences. No key needed.

Input parameters:

- `claim` (string, required): The sentence you want to check, as you would publish it.
- `quote` (string): Optional. The sentence from the source, copied verbatim, that bears on the claim.
- `source` (string, required): The source the claim rests on: an http(s) URL, or arxiv:<id>.
- `stance` (string): Optional, with quote. Whether that sentence supports or contradicts the claim (default supports).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/piiiico-check-claim/check-claim#diagnostics

## Score history

- 2026-10-18: 66
- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 63
- 2026-10-12: 63

## Common questions

### What is the check-claim MCP server?

check-claim is an MCP server listed in the public MCP registry as io.github.piiiico/check-claim. Check that a source really says what your claim says, before you publish. Verbatim, multi-path. This page covers its hosted endpoint (https://check-claim.amdal-dev.workers.dev/mcp).

### Is the check-claim MCP server safe to use?

check-claim scores 66 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 check-claim MCP server expose?

check-claim exposes 1 tool: check_claim. Their descriptions and schemas cost roughly 260 tokens of context every time the server is loaded.

### Does the check-claim MCP server require authentication?

No. We connected to check-claim without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the check-claim MCP server still maintained?

check-claim is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://check-claim.amdal-dev.workers.dev/mcp
- Repository: https://github.com/piiiico/check-claim
- Changelog RSS feed: https://verifymcp.io/servers/piiiico-check-claim/check-claim.xml
- Changelog JSON feed: https://verifymcp.io/servers/piiiico-check-claim/check-claim.json
- HTML version of this page: https://verifymcp.io/servers/piiiico-check-claim/check-claim