Skip to content

LinkVet MCP server

dev.pages.linkvet/linkvetlinkvet.pages.devstreamable-httpv1.0.0Scanned

Verify a URL before citing it: live/404/blocked, final URL, title, price, dates, safe_to_cite.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 2
  • No findings

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the LinkVet MCP server can do

The LinkVet MCP server is published by linkvet.pages.dev, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: check_urls), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (check_url and check_urls); 2 tools can send data out of your system (check_url and check_urls).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 22, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • check_urlsBatch version of check_url: verify up to 25 URLs in one call (e.g.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Batch version of check_url: verify up to 25 URLs in one call (e.g. every link in an answer you are about to send). Returns one result per URL in input order.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • check_urlFetch a URL and verify it is live before you cite or share it.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "check_url" says "url": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Fetch a URL and verify it is live before you cite or share it. Returns status (live | 404 | blocked | timeout | error | invalid | blocked_ssrf), HTTP code, final URL after redirects, page title, detected price, published/modified dates, and safe_to_cite with a reason. Results are cached ~12h.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http linkvet https://linkvet.pages.dev/mcp
claude mcp add --transport http linkvet https://linkvet.pages.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__linkvet__check_url",
      "mcp__linkvet__check_urls"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as linkvet. Review it before you use it.

Capability tags behind 2 rules
  • mcp__linkvet__check_url untrusted-input, outbound
  • mcp__linkvet__check_urls untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.pages.linkvet/linkvet/verify?hash=683ee6df1e338621e8502ae169f4222b82afd141779ace88be59c42f81b2dc0e" | jq -e '.changed == false'

Pinned hash 683ee6df1e33, from Nov 22, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.pages.linkvet/linkvet/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.pages.linkvet/linkvet
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.pages.linkvet/linkvet.svg)](https://radar.anlyon.com/servers/dev.pages.linkvet/linkvet)

Source: MCP Registry. Synced Nov 22, 2026, 04:17 UTC.

LinkVet MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LinkVet MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LinkVet MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the LinkVet MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the LinkVet MCP server have?

2 tools: 1 write, 1 read. check_urls and check_url.

Does the LinkVet MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_url and check_urls.

Has the LinkVet MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 22, 2026.