FraudKit is answering right now. Last checked 2 min ago. Last commit 15 Oct 2026.
Fraud risk score for signups and orders from email, IP, phone and user-agent
We read the source, 23 h ago · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
p = os.path.join(HERE, f"{name}.mmdb")
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
claude mcp add fraudkit --transport http https://fraudkit-fraud-risk-score-for-signups-orders.p.rapidapi.com/mcp
{
"mcpServers": {
"fraudkit": {
"url": "https://fraudkit-fraud-risk-score-for-signups-orders.p.rapidapi.com/mcp"
}
}
}
[mcp_servers.fraudkit]
url = "https://fraudkit-fraud-risk-score-for-signups-orders.p.rapidapi.com/mcp"
{
"mcpServers": {
"fraudkit": {
"url": "https://fraudkit-fraud-risk-score-for-signups-orders.p.rapidapi.com/mcp"
}
}
}
{
"mcpServers": {
"fraudkit": {
"url": "https://fraudkit-fraud-risk-score-for-signups-orders.p.rapidapi.com/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://fraudkit-fraud-risk-score-for-signups-orders.p.rapidapi.com/mcp | streamable-http | needs auth | 383 ms | 2 min ago |
Signup fraud checks: score emails and IPs, look up IPs and manage your blocklist.
Gives an AI agent a disposable email and a real UK phone number to test signup flows.
Phone numbers, SMS, 2FA capture, voice calls, and email for AI agents.
Create and manage waitlists from your AI agent: page, custom domain, emails, signups, broadcasts.
Give an agent its own inbox: send, receive, and pull signup codes from real email.
Give an AI agent a throwaway email and phone number to test signup/verification flows end to end.
Run LinkedIn and email outbound from Claude, ChatGPT, or any AI agent.
Signup sessions, browser continuity, email, SMS, and OTP/TOTP infrastructure for AI agents.
Answers built from our own checks of this server.