Skip to content

FFraud MCP server

com.ffraud/mcpffraud.comstreamable-httpv1.3.0Scanned

Check a website's security and any IP, email or domain for fraud. Free, no key needed.

7 tools: 7 change things.

Tools: 0 delete, 0 irreversible, 7 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 7
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the FFraud MCP server can do

The FFraud MCP server is published by ffraud.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (7 tools: site_check, ip_check, email_check, domain_check and 3 more), but cannot delete data. None of its tools only reads.

7 tools bring in text other people can write (site_check, ip_check, email_check and 4 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.3.0.

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.

7 tools

Changes things 7Claude Code: ask
  • claim_api_keyAfter request_api_key: picks up the API key once the person pressed Approve.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Pick up the approved key
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • domain_checkReputation for a domain: whether it hands out disposable mailboxes and whether it appears in the phishing dataset, with a risk level.Reads text others writeNo 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

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Domain check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • email_checkCheck 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 temp…Reads text others writeNo 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

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Email check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • ip_checkFraud 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.Reads text others writeNo 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

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: IP check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • ip_reportsThe community abuse reports filed against an IP: what it was reported for, when, and by how many distinct reporters.Reads text others writeNo 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

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: IP abuse reports
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • request_api_keyAsk FFraud for an API key for the person you work for.Reads text others writeNo findings

    Why it is in this group

    • The name "request_api_key" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get an FFraud API key
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • site_checkCheck 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, n…Reads text others writeNo 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

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Website security check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:18 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://ffraud.com/api/mcp: tools/list returned 7 tools to an anonymous client, including site_check (write), ip_check (write), email_check (write), domain_check (write), ip_reports (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http ffraud https://ffraud.com/api/mcp
claude mcp add --transport http ffraud https://ffraud.com/api/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__ffraud__site_check",
      "mcp__ffraud__ip_check",
      "mcp__ffraud__email_check",
      "mcp__ffraud__domain_check",
      "mcp__ffraud__ip_reports",
      "mcp__ffraud__request_api_key",
      "mcp__ffraud__claim_api_key"
    ],
    "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 ffraud. Review it before you use it.

Capability tags behind 7 rules
  • mcp__ffraud__site_check untrusted-input
  • mcp__ffraud__ip_check untrusted-input
  • mcp__ffraud__email_check untrusted-input
  • mcp__ffraud__domain_check untrusted-input
  • mcp__ffraud__ip_reports untrusted-input
  • mcp__ffraud__request_api_key untrusted-input
  • mcp__ffraud__claim_api_key untrusted-input

Pin

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://radar.anlyon.com/api/v1/servers/com.ffraud/mcp/verify?hash=067a1cd0d1cca5226e04e86a6b0bcb45f84abacdf872a61d2d630e24844a6bc1" | jq -e '.changed == false'

Pinned hash 067a1cd0d1cc, from Nov 18, 2026, 05:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.ffraud/mcp/changes.xml

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

Badge

Anlyon Radar badge for com.ffraud/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.ffraud/mcp.svg)](https://radar.anlyon.com/servers/com.ffraud/mcp)

Source: MCP Registry · repository. Synced Nov 18, 2026, 05:17 UTC.

FFraud MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FFraud MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the FFraud MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FFraud MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the FFraud MCP server have?

7 tools: 7 write. site_check, ip_check, email_check, domain_check, ip_reports, request_api_key and claim_api_key.

Does the FFraud MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the FFraud MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the FFraud MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.