FFraud

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

使うべきか

品質と安全性

A
説明の品質
96%
スキーマの完全性
100%
命名の品質
80%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

検出事項(1)

  • LOWTool 'ip_reports' description lacks action verbip_reports 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,252トークン数(ツール定義)
~643 B一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 0.98%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "mcp": {
      "url": "https://ffraud.com/api/mcp"
    }
  }
}

リモートエンドポイント

https://ffraud.com/api/mcpstreamable-http

できること

ツール一覧

ツール(7)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢site_check(site, fresh)

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.

入力スキーマ

{
  "type": "object",
  "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."
    }
  },
  "required": [
    "site"
  ]
}
🟢ip_check(ips)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "ips": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 20,
      "description": "IPv4 or IPv6 addresses. One is the common case."
    }
  },
  "required": [
    "ips"
  ]
}
🟢email_check(email)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "A full email address, e.g. [email protected]"
    }
  },
  "required": [
    "email"
  ]
}
🟢domain_check(domain)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "A bare domain, e.g. mailinator.com (no scheme, no path)"
    }
  },
  "required": [
    "domain"
  ]
}
🟢ip_reports(ip)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "ip": {
      "type": "string",
      "description": "The IPv4 or IPv6 address to read reports for."
    }
  },
  "required": [
    "ip"
  ]
}
⚪request_api_key(email, agent)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "The person's own email address; the approval email goes there."
    },
    "agent": {
      "type": "string",
      "description": "Your name as the person knows you, e.g. \"Claude Code\". The email shows it."
    }
  },
  "required": [
    "email"
  ]
}
🟡claim_api_key(signup_id, claim_token)

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.

入力スキーマ

{
  "type": "object",
  "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."
    }
  },
  "required": [
    "signup_id",
    "claim_token"
  ]
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 7 件