_ registry / mcp streamable-http · checked 1h ago

value-verdicts

https://verdicts.anagramic.com

Registry code: a96f7ba348fca08c

api record

Safety checks to run before an agent pays an address or opens a link. Each returns verdict pass/caution/fail and proceed true/false. Do not proceed on fail.

endpoint
https://verdicts.anagramic.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is value-verdicts live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is value-verdicts free to use?
Yes — the hub reached it with no key and no payment.
What tools does value-verdicts have?
3 tools: address_check, payment_check, link_check.
Is value-verdicts safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
420ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • address_check unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "known": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional. Addresses you have paid or trust before (max 200). GET: comma-separated."
        },
        "address": {
          "type": "string",
          "description": "The address you are about to pay."
        },
        "network": {
          "enum": [
            "evm",
            "ethereum",
            "base",
            "polygon",
            "arbitrum",
            "optimism",
            "bsc",
            "avalanche",
            "solana",
            "bitcoin"
          ],
          "type": "string",
          "description": "Optional. Network you intend to use."
        },
        "_payment": {
          "type": "string",
          "description": "x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used."
        },
        "expected": {
          "type": "string",
          "description": "Optional. The address you were told to pay, e.g. from an invoice."
        }
      },
      "additionalProperties": false
    }
    arguments 44 lines
  • payment_check unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "paymentRequired"
      ],
      "properties": {
        "_payment": {
          "type": "string",
          "description": "x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used."
        },
        "maxPrice": {
          "type": "string",
          "description": "Optional. Your price limit in US dollars, e.g. \"0.05\"."
        },
        "knownPayees": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional. Payee addresses you have paid before (max 200). GET: comma-separated."
        },
        "requestedUrl": {
          "type": "string",
          "description": "Optional. The URL you called that returned the 402."
        },
        "paymentRequired": {
          "type": [
            "string",
            "object"
          ],
          "description": "The PAYMENT-REQUIRED header value (base64) or the 402 JSON body. GET: base64 only."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • link_check unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The link to check."
        },
        "_payment": {
          "type": "string",
          "description": "x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used."
        },
        "expectedBrand": {
          "type": "string",
          "description": "Optional. The brand this link claims to be, e.g. \"paypal\". Fails if the domain is not official."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a96f7ba348fca08c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a96f7ba348fca08c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a96f7ba348fca08c/badge.svg)](https://brick.blue/agent/a96f7ba348fca08c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.