Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LinkProof

REMOTE · LINKPROOF.BSPTIMBER.WORKERS.DEV · 2 COMPONENTS

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

+4 this week 67 Trust /100

Last scanned (22 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 43% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 17 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 50% → 43% ▼ functional
    • 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” functional
  • 15 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 63

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://linkproof.bsptimber.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bsptimber.workers.dev CN=YE1,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA384 62e9454d20f45c93726dccb8cf9c6cd68d3
SANs: *.bsptimber.workers.dev, bsptimber.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of linkproof.bsptimber.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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://linkproof.bsptimber.workers.dev/mcp Verified 200
http (plaintext) http://linkproof.bsptimber.workers.dev/mcp Inconclusive 405
MCP tools · 10 exposed · ~1,058 tokens

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 →

Tool Tokens
check_headers ~101

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).

NameTypeReqDescription
urlsarrayyesURLs or domains to inspect

No output schema declared.

No examples provided.

email_auth ~110

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).

NameTypeReqDescription
domainsarrayyesDomains, or email addresses (only the domain is used)

No output schema declared.

No examples provided.

find_archive ~88

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).

NameTypeReqDescription
datestring–Default target date
urlsarrayyes–

No output schema declared.

No examples provided.

ics_parse ~123

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).

NameTypeReqDescription
fromstring––
icsstring–Raw ICS text
max_occurrencesinteger––
textstring––
tostring––
urlstring––

No output schema declared.

No examples provided.

injection_scan ~108

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).

NameTypeReqDescription
textstringyesText to scan (max 50 KB)

No output schema declared.

No examples provided.

license_detect ~107

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).

NameTypeReqDescription
textstring–License text
urlstring–Public URL of a LICENSE file

No output schema declared.

No examples provided.

site_policies ~121

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).

NameTypeReqDescription
pathstring–Default path to test against robots.txt
urlsarrayyes–

No output schema declared.

No examples provided.

verify_citations ~112

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).

NameTypeReqDescription
citationsarrayyes–

No output schema declared.

No examples provided.

verify_links ~100

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).

NameTypeReqDescription
urlsarrayyesURL strings, or {url, expect} objects

No output schema declared.

No examples provided.

wiki_summary ~88

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).

NameTypeReqDescription
itemsarray––
langstring––
querystring––
titlestring––

No output schema declared.

No examples provided.

Install

How do I install the LinkProof MCP server?

LinkProof is a hosted endpoint at https://linkproof.bsptimber.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.

remote · linkproof.bsptimber.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-bsptimber-linkproof-linkproof 'https://linkproof.bsptimber.workers.dev/mcp'
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.bsptimber.workers.dev/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.