Skip to content

io.github.notifuturo/vouch

by notifuturo · remote · no sign-in to list tools · v0.1.1 · published by GitHub user notifuturo

Check if a counterparty is safe to pay: trust/risk score for AI agents. Scam/phishing screen.

Changes · 2
CompareRegistry entry

2 tools: 2 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http vouch https://vouch.futuronoti.workers.dev/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Changes things 2Claude Code: ask
  • vouch_reportReport a host as a scam/bad actor ('flag') or as trustworthy ('vouch'), improving Vouch's community reputation graph for everyone's future payment-trust checks.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.
    Description, as the server wrote it
    Report a host as a scam/bad actor ('flag') or as trustworthy ('vouch'), improving Vouch's community reputation graph for everyone's future payment-trust checks. Free.
  • vouch_scoreCheck whether a counterparty is SAFE TO PAY before sending money.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.
    Description, as the server wrote it
    Check whether a counterparty is SAFE TO PAY before sending money. Given a URL or host, returns a 0-100 trust score and risk band (low/medium/high/critical), detecting scams, phishing, and known-malicious endpoints via threat feeds, domain risk heuristics, and a community reputation graph. Call this before paying any merchant, API, agent, or x402 resource. Free — for the full explainable reasons AND a signed, verifiable attestation (proof of the check for audit/disputes), call the paid POST /v1/check endpoint via x402.

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.

Install

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

claude mcp add --transport http vouch https://vouch.futuronoti.workers.dev/mcp

Run in a terminal.

Claude Code permissions

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

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

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as vouch. Review it before you use it.