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

ffraud

https://ffraud.com

Registry code: a27fe6c43a3328e1

api record

FFraud's open fraud database. site_check checks a whole website's security in seconds and returns every finding with the exact fix; ip_check scores any IP for VPN, proxy, Tor, datacenter and abuse history; email_check catches disposable and blacklisted addresses; domain_check reads a domain's phishing and throwaway-mailbox record; ip_reports returns the community evidence behind a score. All free and keyless; a free key raises site_check's hourly allowance. To get one without a browser: request_api_key emails the person an Approve button, and after their click claim_api_key returns the key…

endpoint
https://ffraud.com/api/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 ffraud live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is ffraud free to use?
Yes — the hub reached it with no key and no payment.
What tools does ffraud have?
7 tools: domain_check, ip_check, email_check, ip_reports, request_api_key, claim_api_key, site_check.
Is ffraud 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
599ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 3 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
1

through this hub

calls served
1

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 7 tools
7 never probed 0 of 7 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.

  • domain_check unknown 8h ago

    Reputation for a domain: whether it hands out disposable mailboxes and whether it appears in the phishing dataset, with a risk level. One unauthenticated lookup, no key.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "A bare domain, e.g. mailinator.com (no scheme, no path)"
        }
      }
    }
    arguments 12 lines
  • ip_check unknown 8h ago

    Fraud intelligence for any IPv4 or IPv6 address: a 0-100 fraud score, risk band, and whether it is a VPN, proxy, Tor node, relay, datacenter host or mobile connection. Also returns the owning network (ASN, ISP, organisation), geolocation, reverse DNS, abuse history and how much of its /24 subnet is flagged. Free, no key. Use it before trusting a signup, a checkout or an API caller.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ips"
      ],
      "properties": {
        "ips": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 20,
          "description": "IPv4 or IPv6 addresses. One is the common case."
        }
      }
    }
    arguments 16 lines
  • email_check unknown never probed

    Check an email address before you let it create an account: whether it is disposable or throwaway, a role address, on a community blacklist, or tied to a domain that hands out temporary mailboxes. Free, no key.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "A full email address, e.g. [email protected]"
        }
      }
    }
    arguments 12 lines
  • ip_reports unknown 8h ago

    The community abuse reports filed against an IP: what it was reported for, when, and by how many distinct reporters. Use it when you want the evidence behind a score rather than the score alone.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ip"
      ],
      "properties": {
        "ip": {
          "type": "string",
          "description": "The IPv4 or IPv6 address to read reports for."
        }
      }
    }
    arguments 12 lines
  • request_api_key unknown never probed

    Ask FFraud for an API key for the person you work for. FFraud emails them one Approve button, and nothing is created until they press it. Returns signup_id and claim_token: tell the person to open the email from FFraud and press Approve, then call claim_api_key with both. Use it only when the person wants a key and gave you their own email address.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "agent": {
          "type": "string",
          "description": "Your name as the person knows you, e.g. \"Claude Code\". The email shows it."
        },
        "email": {
          "type": "string",
          "description": "The person's own email address; the approval email goes there."
        }
      }
    }
    arguments 16 lines
  • claim_api_key unknown never probed

    After request_api_key: picks up the API key once the person pressed Approve. Answers status "pending" while they have not (wait about 5 seconds and call again, or remind them to check their inbox), "approved" with api_key exactly once (keep it: send it in the X-API-Key header, store it as FFRAUD_API_KEY), or "denied", "expired" or "delivered" when it is over.

    mcp-tool

    {
      "type": "object",
      "required": [
        "signup_id",
        "claim_token"
      ],
      "properties": {
        "signup_id": {
          "type": "string",
          "description": "The signup_id request_api_key returned."
        },
        "claim_token": {
          "type": "string",
          "description": "The claim_token request_api_key returned."
        }
      }
    }
    arguments 17 lines
  • site_check unknown 35h ago

    Check a whole website's security in seconds: the TLS certificate (trusted by browsers, expiry, the names it covers), the security headers (HSTS, Content-Security-Policy, framing, nosniff, referrer and permissions policies), cookie flags, whether http:// moves to https://, the domain's mail records (SPF, DMARC, MX), whether the domain or the addresses serving it are on phishing or abuse lists, and the bot protection the home page loads. Returns a 0-100 score, a grade from A to F, every finding with the exact fix to apply (header lines, DNS records, server settings), and what passed. Reads only what any visitor sees. Free, no key: 20 fresh checks an hour per address, 300 per account with a free key; a site checked in the last ten minutes costs nothing.

    mcp-tool

    {
      "type": "object",
      "required": [
        "site"
      ],
      "properties": {
        "site": {
          "type": "string",
          "description": "The site's domain or any URL of it, e.g. example.com or https://example.com/login"
        },
        "fresh": {
          "type": "boolean",
          "description": "true after the site was changed, to check it again now instead of reading the answer kept for ten minutes. A site is checked at most once a minute."
        }
      }
    }
    arguments 16 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 a27fe6c43a3328e1.

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

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
1
ok
1
failed
0
success rate
100%
median latency
1,688ms
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
—

1 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.