VALUE Verdicts

io.github.5Darryl/value-verdicts5Darrylstreamable-httpv1.1.3Scanned 49 minutes ago

Safety checks before an agent pays: address poisoning, phishing links, x402 payment requests.

4 tools: 1 do something that can't be undone and 3 change things.

Reads private data · 0
Reads text others write · 0
Can send data out · 2
3 findings

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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.

4 tools

Can't be undone 1Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

payment_checkBefore you sign an x402 payment to another service: pass the 402 payment request you received and get one verdict on the whole thing.1 finding
Why it is in this group
- The name "payment_check" says "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "payment_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
  Matched text
  annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_check" says "payment": a word that usually means money moves, which cannot be taken back.
  What this check looks for
Description, as the server wrote it
Before you sign an x402 payment to another service: pass the 402 payment request you received and get one verdict on the whole thing. Checks the price against your limit, that the token is real USDC with the right signing name, the payee address (checksum, poisoning lookalikes, on-chain history), whether the request claims a different site than the one you called, and the site itself (lookalike domains, domain age). One call, one price. Price: $0.01 USDC per call after 25 free calls per day.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false

Changes things 3Creates or changes something that can be changed back.Claude Code: ask

address_checkBefore sending crypto: checks an EVM, Solana or Bitcoin address for a valid checksum, the right network, dead/burn/program addresses, a mismatch with the expected payee, and addres…No 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.
Description, as the server wrote it
Before sending crypto: checks an EVM, Solana or Bitcoin address for a valid checksum, the right network, dead/burn/program addresses, a mismatch with the expected payee, and address-poisoning lookalikes of addresses you already trust. Live on-chain lookup: has the address ever been used, is it a wallet, contract or program. Returns pass / caution / fail with reasons. Price: $0.01 USDC per call after 25 free calls per day.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
link_checkBefore opening a link or entering credentials: detects lookalike domains (homoglyphs, mixed alphabets, typosquats), brand impersonation in domains and subdomains, hidden destinatio…Can send data out2 findings
Why it is in this group
- The name "link_check" says "link": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Info
  The description mentions "credentials".
  Matched text
  description: "Before opening a link or entering credentials: detects lookalike domains (homoglyphs,..."
  What this check looks for
- Warn
  The server marks "link_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "link_check" says "link": a word for a change.
  What this check looks for
Description, as the server wrote it
Before opening a link or entering credentials: detects lookalike domains (homoglyphs, mixed alphabets, typosquats), brand impersonation in domains and subdomains, hidden destinations (user@host), unsafe schemes, and risky TLDs across 70+ commonly impersonated brands. Live lookups: does the domain exist (DNS) and how old is it (registration date), since most phishing domains are days old. The page itself is never visited. Price: $0.01 USDC per call after 25 free calls per day.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
x402_preflightBefore paying an x402 service: safely makes one unauthenticated HTTPS request, confirms the endpoint is live and returns a current 402 challenge, then checks its price, USDC token,…Can 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
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it
Before paying an x402 service: safely makes one unauthenticated HTTPS request, confirms the endpoint is live and returns a current 402 challenge, then checks its price, USDC token, payee and site. Never signs or settles a payment. HTTPS only; redirects and private/local targets are refused. Price: $0.01 USDC per call after 25 free calls per day.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false

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 or untrusted-input.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0: 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.; link_check
x402_preflight

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.

2 warn1 info

Warnlink_check
The server marks "link_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "link_check" says "link": a word for a change.
What this check looks for
Warnpayment_check
The server marks "payment_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
Matched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_check" says "payment": a word that usually means money moves, which cannot be taken back.
What this check looks for
Infolink_check
The description mentions "credentials".
Matched text
description: "Before opening a link or entering credentials: detects lookalike domains (homoglyphs,..."
What this check looks for

History

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

Nov 1, 2026Tools1 added.+1 addedView diff
- Added:x402_preflightChanges things

All changes to this server

Install

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

claude mcp add --transport http value-verdicts https://verdicts.anagramic.com/mcp

claude mcp add --transport http value-verdicts https://verdicts.anagramic.com/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__value-verdicts__address_check",
      "mcp__value-verdicts__link_check",
      "mcp__value-verdicts__payment_check",
      "mcp__value-verdicts__x402_preflight"
    ],
    "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 value-verdicts. Review it before you use it.

Capability tags behind 2 rules

mcp__value-verdicts__link_check outbound
mcp__value-verdicts__x402_preflight outbound

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://anlyon.dev/api/v1/servers/io.github.5Darryl/value-verdicts/verify?hash=ca1b4bebe7ac33de0a1ce5375ae76e8415f892b96b33f6627b2d643a0e9a5dae" | jq -e '.changed == false'

Pinned hash ca1b4bebe7ac, from Nov 1, 2026, 14:18 UTC.

Watch

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

https://anlyon.dev/servers/io.github.5Darryl/value-verdicts/changes.xml

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

Badge

[![anlyon.dev](https://anlyon.dev/badge/io.github.5Darryl/value-verdicts.svg)](https://anlyon.dev/servers/io.github.5Darryl/value-verdicts)

Source: MCP Registry. Synced Nov 1, 2026, 14:17 UTC.