# LinkProof (remote · linkproof.zopip.com)

Pay-per-call (x402 USDC on Base) tools: verify URLs, verify citations, find Wayback archives.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `linkproof.bsptimber.workers.dev`: 67/100, [markdown](https://verifymcp.io/servers/dev-workers-bsptimber-linkproof-linkproof/linkproof.md), [page](https://verifymcp.io/servers/dev-workers-bsptimber-linkproof-linkproof/linkproof)
- remote · `linkproof.zopip.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-bsptimber-linkproof-linkproof/linkproof-2.md), [page](https://verifymcp.io/servers/dev-workers-bsptimber-linkproof-linkproof/linkproof-2)

## Channel facts

- Endpoint: `https://linkproof.zopip.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## 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-11-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1141 tokens (~114/item across 10 items; 10 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**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 43% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the LinkProof MCP server?

LinkProof is a hosted endpoint at https://linkproof.zopip.com/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 dev-workers-bsptimber-linkproof-linkproof 'https://linkproof.zopip.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-bsptimber-linkproof-linkproof": {
      "url": "https://linkproof.zopip.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-bsptimber-linkproof-linkproof": {
      "type": "http",
      "url": "https://linkproof.zopip.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-bsptimber-linkproof-linkproof]
url = "https://linkproof.zopip.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-bsptimber-linkproof-linkproof": {
      "type": "remote",
      "url": "https://linkproof.zopip.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-bsptimber-linkproof-linkproof --url 'https://linkproof.zopip.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-bsptimber-linkproof-linkproof:
    url: "https://linkproof.zopip.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-bsptimber-linkproof-linkproof": {
      "Transport": "http",
      "Url": "https://linkproof.zopip.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-bsptimber-linkproof-linkproof -t streamable-http -u 'https://linkproof.zopip.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-bsptimber-linkproof-linkproof": {
      "type": "http",
      "url": "https://linkproof.zopip.com/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-11-21 (score 67, +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-11-19 (score 66, +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-11-17 (score 65, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Tool coverage: 50% → 43%
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.1.0 → 1.3.0
- [functional] New tool “check_headers”
- [functional] New tool “email_auth”
- [functional] New tool “ics_parse”
- [functional] New tool “injection_scan”
- [functional] New tool “license_detect”
- [functional] New tool “site_policies”
- [functional] New tool “wiki_summary”

### 2026-11-16 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 63)

First indexed and scored.

## MCP tools (10)

### `verify_links` (~100 tokens)

Check up to 10 URLs before citing or sending them. Per URL: verdict (live, live_but_text_not_found, soft_404, parked, dead, blocked_or_rate_limited, unreachable), HTTP status, final URL, title, and optional check that an expected phrase appears. Price: 0.005 USDC per call (x402, Base).

Input parameters:

- `urls` (array, required): URL strings, or {url, expect} objects

### `verify_citations` (~112 tokens)

Verify up to 10 citations really exist and match the claimed title/authors/year, against Crossref, DataCite, arXiv and PubMed. Items: DOI, arXiv id, 'PMID: 123', free-text reference, or {doi|arxiv|pmid|title, authors, year}. Verdicts: verified, mismatch, not_found, error. Price: 0.01 USDC per call (x402, Base).

Input parameters:

- `citations` (array, required)

### `find_archive` (~88 tokens)

For up to 10 URLs (e.g. dead links), find the closest Internet Archive Wayback Machine snapshot, optionally nearest a date (YYYY, YYYY-MM or YYYY-MM-DD). Returns snapshot URL, capture time, captured status. Price: 0.005 USDC per call (x402, Base).

Input parameters:

- `date` (string): Default target date
- `urls` (array, required)

### `check_headers` (~101 tokens)

Inspect security headers for up to 5 URLs: HSTS, CSP, clickjacking protection, cookie flags (names only, never values), Server/X-Powered-By disclosure, HTTPS redirect, a simple letter grade and plain recommendations. HEAD is used first, with a small GET if needed. No TLS certificate handshake. Price: 0.01 USDC per call (x402, Base).

Input parameters:

- `urls` (array, required): URLs or domains to inspect

### `site_policies` (~121 tokens)

Fetch robots.txt, llms.txt, llms-full.txt, ai.txt and /.well-known/security.txt for up to 5 sites. Parses AI-crawler rules (GPTBot, ClaudeBot, Google-Extended, CCBot, PerplexityBot, …) and whether a given path is allowed, lists sitemap URLs, and parses security.txt contact/expiry. Price: 0.005 USDC per call (x402, Base).

Input parameters:

- `path` (string): Default path to test against robots.txt
- `urls` (array, required)

### `email_auth` (~110 tokens)

Check SPF, DMARC, MX and common DKIM selectors for up to 5 domains via DNS-over-HTTPS. Reports policy strength, common misconfigs (multiple SPF, SPF lookup limit, +all, p=none), a simple grade and recommendations. Mailbox existence is never probed. Not a deliverability or safety guarantee. Price: 0.01 USDC per call (x402, Base).

Input parameters:

- `domains` (array, required): Domains, or email addresses (only the domain is used)

### `injection_scan` (~108 tokens)

Rule-based scan of a text blob (max 50 KB) for prompt-injection patterns: instruction overrides, role hijack, hidden unicode, base64 payloads, tool/webhook exfil, markdown image exfil. Returns risk, matches with offsets, and a sanitized copy marked untrusted. Heuristic only; text is not stored. Price: 0.005 USDC per call (x402, Base).

Input parameters:

- `text` (string, required): Text to scan (max 50 KB)

### `wiki_summary` (~88 tokens)

Short Wikipedia extract for up to 3 titles or search queries (optional lang). Returns extract, URL, thumbnail, Wikidata id and CC BY-SA 4.0 attribution. Price: 0.005 USDC per call (x402, Base).

Input parameters:

- `items` (array)
- `lang` (string)
- `query` (string)
- `title` (string)

### `license_detect` (~107 tokens)

Identify a common SPDX license (MIT, Apache-2.0, GPL, LGPL, AGPL, BSD, MPL-2.0, ISC, Unlicense, CC0, …) from license text or a public LICENSE file URL. Returns confidence and key permissions/conditions. Not legal advice. Price: 0.003 USDC per call (x402, Base).

Input parameters:

- `text` (string): License text
- `url` (string): Public URL of a LICENSE file

### `ics_parse` (~123 tokens)

Parse iCalendar (ICS) text or a public .ics URL. Returns VEVENTs (summary, start/end in UTC/ISO, location) with RRULE expanded to at most 50 occurrences in a bounded window. Data is not stored. Price: 0.003 USDC per call (x402, Base).

Input parameters:

- `from` (string)
- `ics` (string): Raw ICS text
- `max_occurrences` (integer)
- `text` (string)
- `to` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-bsptimber-linkproof-linkproof/linkproof-2#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64
- 2026-11-15: 63

## Common questions

### What is the LinkProof MCP server?

LinkProof is an MCP server listed in the public MCP registry as dev.workers.bsptimber.linkproof/linkproof. Pay-per-call (x402 USDC on Base) tools: verify URLs, verify citations, find Wayback archives. This page covers its hosted endpoint (https://linkproof.zopip.com/mcp).

### Is the LinkProof MCP server safe to use?

LinkProof scores 67 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 LinkProof MCP server expose?

LinkProof exposes 10 tools: verify_links, verify_citations, find_archive, check_headers, site_policies, and 5 more. Their descriptions and schemas cost roughly 1,058 tokens of context every time the server is loaded.

### Does the LinkProof MCP server require authentication?

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

### Is the LinkProof MCP server still maintained?

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

### What did VerifyMCP test on the LinkProof MCP server?

VerifyMCP ran 12 checks on LinkProof, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about LinkProof: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://linkproof.zopip.com/mcp
- Website: https://linkproof.zopip.com/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-bsptimber-linkproof-linkproof/linkproof-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-bsptimber-linkproof-linkproof/linkproof-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-workers-bsptimber-linkproof-linkproof/linkproof-2.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-bsptimber-linkproof-linkproof/linkproof-2
