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

counterparty-check

https://counterparty-check-production.up.railway.app

Registry code: c51b8d3e1f6d4f7f

api record

Call check_counterparty before sending money to a payee you have not verified, and whenever payment details change. Pass everything you know in "context" (first payment, changed bank details, how the request arrived, urgency, the vendor domain on file). Treat a "block" verdict as do-not-pay and a "review" verdict as needing a human.

endpoint
https://counterparty-check-production.up.railway.app/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 counterparty-check live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is counterparty-check free to use?
No — it asks for a key or a login before it will serve.
What tools does counterparty-check have?
4 tools: check_balance, verify_receipt, screen_sanctions, check_counterparty.
Is counterparty-check 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
347ms

last good check

priced tools
0

of 4 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

_ what it can do 4 tools
4 auth-required 4 of 4 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.

  • check_balance auth-required 1h ago

    Show the remaining prepaid balance on the API key used for this connection. Free.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • verify_receipt auth-required never probed

    Confirm that a receipt returned by a previous check is authentic and unaltered. Free.

    mcp-tool

    {
  "type": "object",
  "required": [
    "receipt"
  ],
  "properties": {
    "receipt": {
      "type": "object",
      "description": "The full \"receipt\" object from a check response"
    }
  }
}
    arguments 12 lines
  • screen_sanctions auth-required 1h ago

    Screen a payee name (and optional crypto wallet) against OFAC sanctions lists and embargoed jurisdictions. Faster and cheaper than check_counterparty but does not detect fraud patterns. Costs $0.05.

    mcp-tool

    {
  "type": "object",
  "required": [
    "counterparty"
  ],
  "properties": {
    "context": {
      "type": "object",
      "properties": {
        "payer_domain": {
          "type": "string",
          "description": "Your own company's domain, to catch internal impersonation"
        },
        "requester_email": {
          "type": "string",
          "description": "Who asked for this payment"
        },
        "previous_payment": {
          "type": "object",
          "properties": {
            "iban": {
              "type": "string"
            },
            "crypto_address": {
              "type": "string"
            },
            "routing_number": {
              "type": "string"
            }
          },
          "description": "Details used for the last payment to this payee, to detect changes"
        },
        "known_good_domain": {
          "type": "string",
          "description": "The vendor's domain on file from past dealings"
        },
        "requested_urgency": {
          "type": "boolean",
          "description": "The request pressed for fast payment"
        },
        "bank_details_changed": {
          "type": "boolean",
          "description": "The payee asked to change where money goes"
        },
        "change_requested_via": {
          "enum": [
            "email",
            "phone",
            "portal",
            "in_person",
            "chat",
            "other"
          ],
          "type": "string"
        },
        "first_payment_to_payee": {
          "type": "boolean"
        }
      },
      "description": "What the paying agent knows about how this payment came about. Each field sharpens fraud detection."
    },
    "payment": {
      "type": "object",
      "properties": {
        "iban": {
          "type": "string"
        },
        "amount": {
          "type": "number",
          "minimum": 0
        },
        "method": {
          "enum": [
            "ach",
            "wire",
            "card",
            "crypto",
            "check",
            "other"
          ],
          "type": "string"
        },
        "currency": {
          "type": "string"
        },
        "swift_bic": {
          "type": "string"
        },
        "crypto_address": {
          "type": "string",
          "description": "Receiving wallet address"
        },
        "crypto_network": {
          "type": "string",
          "description": "e.g. base, ethereum, solana, bitcoin, tron"
        },
        "routing_number": {
          "type": "string",
          "description": "US ABA routing number"
        }
      }
    },
    "counterparty": {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "description": "Legal or trading name of the payee"
        },
        "email": {
          "type": "string",
          "maxLength": 254,
          "description": "Email address the payee invoices or writes from"
        },
        "address": {
          "type": "string",
          "maxLength": 500,
          "description": "Payee street address"
        },
        "country": {
          "type": "string",
          "maxLength": 60,
          "description": "ISO 3166-1 alpha-2 code or country name"
        },
        "website": {
          "type": "string",
          "maxLength": 300,
          "description": "Payee website domain or URL"
        }
      }
    }
  }
}
    arguments 137 lines
  • check_counterparty auth-required 1h ago

    Run a full pre-payment risk check on a payee: OFAC sanctions (names and wallets), domain age and email authentication, lookalike domains (vendor impersonation, brand typo-squats, executive impersonation), routing/IBAN/SWIFT/wallet validation, and business-email-compromise signals. Returns verdict proceed/review/block, a 0-100 risk score, explained findings, and a signed receipt. Costs $0.25 from the API key balance. Fill in "context" with everything you know about how the payment request arrived; it materially improves fraud detection.

    mcp-tool

    {
  "type": "object",
  "required": [
    "counterparty"
  ],
  "properties": {
    "context": {
      "type": "object",
      "properties": {
        "payer_domain": {
          "type": "string",
          "description": "Your own company's domain, to catch internal impersonation"
        },
        "requester_email": {
          "type": "string",
          "description": "Who asked for this payment"
        },
        "previous_payment": {
          "type": "object",
          "properties": {
            "iban": {
              "type": "string"
            },
            "crypto_address": {
              "type": "string"
            },
            "routing_number": {
              "type": "string"
            }
          },
          "description": "Details used for the last payment to this payee, to detect changes"
        },
        "known_good_domain": {
          "type": "string",
          "description": "The vendor's domain on file from past dealings"
        },
        "requested_urgency": {
          "type": "boolean",
          "description": "The request pressed for fast payment"
        },
        "bank_details_changed": {
          "type": "boolean",
          "description": "The payee asked to change where money goes"
        },
        "change_requested_via": {
          "enum": [
            "email",
            "phone",
            "portal",
            "in_person",
            "chat",
            "other"
          ],
          "type": "string"
        },
        "first_payment_to_payee": {
          "type": "boolean"
        }
      },
      "description": "What the paying agent knows about how this payment came about. Each field sharpens fraud detection."
    },
    "payment": {
      "type": "object",
      "properties": {
        "iban": {
          "type": "string"
        },
        "amount": {
          "type": "number",
          "minimum": 0
        },
        "method": {
          "enum": [
            "ach",
            "wire",
            "card",
            "crypto",
            "check",
            "other"
          ],
          "type": "string"
        },
        "currency": {
          "type": "string"
        },
        "swift_bic": {
          "type": "string"
        },
        "crypto_address": {
          "type": "string",
          "description": "Receiving wallet address"
        },
        "crypto_network": {
          "type": "string",
          "description": "e.g. base, ethereum, solana, bitcoin, tron"
        },
        "routing_number": {
          "type": "string",
          "description": "US ABA routing number"
        }
      }
    },
    "counterparty": {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "description": "Legal or trading name of the payee"
        },
        "email": {
          "type": "string",
          "maxLength": 254,
          "description": "Email address the payee invoices or writes from"
        },
        "address": {
          "type": "string",
          "maxLength": 500,
          "description": "Payee street address"
        },
        "country": {
          "type": "string",
          "maxLength": 60,
          "description": "ISO 3166-1 alpha-2 code or country name"
        },
        "website": {
          "type": "string",
          "maxLength": 300,
          "description": "Payee website domain or URL"
        }
      }
    }
  }
}
    arguments 137 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 c51b8d3e1f6d4f7f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c51b8d3e1f6d4f7f/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/c51b8d3e1f6d4f7f/badge.svg)](https://brick.blue/agent/c51b8d3e1f6d4f7f?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
80%

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.