Mcp Fraudlabspro

io.github.fraudlabsproPublished by GitHub account fraudlabsprov1.1.1Updated Oct 24, 2026

Fraud Prevention MCP server using FraudLabs Pro API.

VerifiedSTDIODesktop onlySecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Connects an assistant to FraudLabs Pro so it can screen orders and user events for fraud, fetch past results, and submit review feedback.

What you can do
  • Screen e-commerce orders using IP, email, amount, card BIN and billing/shipping country
  • Screen user events such as logins or registrations using email, IP, phone and name
  • Retrieve validation results for earlier order or user screenings
  • Send feedback on transactions (approve, reject, blacklist) to improve detection
When to use it
Useful when you want an assistant to check orders or account events for fraud risk inside a chat workflow, or to look up and act on earlier FraudLabs Pro screening results without leaving the client.
Requirements
A FraudLabs Pro API key (free Micro Plan available). Local install runs via uvx with Python 3.10+ and the FRAUDLABSPRO_API_KEY environment variable; the README also documents a hosted HTTP endpoint using an X-API-Key header, or an npx mcp-remote bridge that needs Node.js. Network access to the FraudLabs Pro API.
Before you install
The API key is a secret passed as FRAUDLABSPRO_API_KEY or an X-API-Key header; keep it out of shared configs. Screening sends order and customer details (email, IP, phone, names, card BIN, amounts, countries) to FraudLabs Pro. Feedback tools change transaction status (approve, reject, blacklist), which affects real fraud decisions.

Installation

In SourceWeft

  1. Open Mcp Fraudlabspro in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

FraudLabs Pro MCP Server

[mcp-fraudlabspro MCP server]

An MCP-compliant server that integrates the FraudLabs Pro fraud detection system into AI assistants like Claude Desktop. This server enables real-time screening of order transactions and user-related events (like logins or registrations) to identify and prevent fraudulent activities.

Features

  • Order Screening: Validate e-commerce orders using IP addresses, billing/shipping details, and credit card information.

  • User Screening: Analyze account-level events (registrations/logins) for suspicious patterns.

  • Transaction Management: Retrieve historical results for orders or user screenings.

  • Feedback Loop: Approve, Reject, or Blacklist transactions directly through the AI interface to improve the detection engine.

Prerequisites

  • Python 3.10+ installed (only needed for the local MCP server).
  • FraudLabs Pro API Key: Sign up for a Free Micro Plan API Key at FraudLabs Pro.

Installation

There are two ways to use this MCP server:

  • Cloud-hosted MCP server: Connect directly to the hosted FraudLabs Pro MCP server. Nothing needs to be installed locally.
  • Local MCP server: Download and run the server on your own machine.

Option 1: Cloud-hosted MCP server

Use this if you want to connect directly to the hosted server.

Method A: Direct HTTP connection

Use this if your MCP client supports remote servers over HTTP. No Node.js or npx is needed.

json
{  "mcpServers": {    "fraudlabspro": {      "type": "http",      "url": "https://mcp.fraudlabspro.com/",      "headers": {        "X-API-Key": "YOUR_API_KEY_HERE"      }    }  }}

If your client is configured from the command line, such as Claude Code, you can add the server with:

bash
claude mcp add --transport http fraudlabspro https://mcp.fraudlabspro.com/ --header "X-API-Key: YOUR_API_KEY_HERE"
Method B: Connection through npx

Use this if your MCP client only supports local (stdio) servers. The mcp-remote package runs locally and forwards requests to the hosted server. Node.js is required.

json
{  "mcpServers": {    "fraudlabspro": {      "command": "npx",      "args": [        "-y",        "mcp-remote@latest",        "https://mcp.fraudlabspro.com/",        "--header",        "X-API-Key:YOUR_API_KEY_HERE"      ]    }  }}

Restart your MCP client after saving the changes, and you should see the server appear in the tools menu.

Option 2: Local MCP server

  1. Install Dependencies Ensure you have the required libraries installed in your environment:
bash
pip install mcp httpx uv
  1. Configuration To use this server with an MCP client (such as Claude Desktop), add the following entry to your configuration file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
json
{  "mcpServers": {    "fraudlabspro": {      "command": "uvx",      "args": [        "mcp-fraudlabspro"      ],      "env": {        "FRAUDLABSPRO_API_KEY": "YOUR_API_KEY_HERE"      }    }  }}

Available Tools

📦 Order Management

ToolDescriptionKey Arguments
screen_orderScreen an order for fraud.ip, email, amount, bin_no, bill_country, ship_country
get_order_resultRetrieve the validation result for a previous order.transaction_id
feedback_orderUpdate order status (APPROVE, REJECT, BLACKLIST).transaction_id, action, note

👤 User Management

ToolDescriptionKey Arguments
screen_userScreen user events like logins or signups.email, ip, phone, first_name, last_name
get_user_resultRetrieve results for a previous user screening.user_transaction_id
feedback_userUpdate user event status based on manual review.user_transaction_id, action, reason

Development & Logging

The server uses FastMCP and sends logs through the MCP context. You can view logs in the Claude Desktop "Developer Console" to inspect outgoing payloads and API responses for debugging.

Common Error: If you receive "An API key is needed," ensure the FRAUDLABSPRO_API_KEY environment variable is correctly set in your configuration file and that you have restarted the MCP client.

License

See the LICENSE file.

Source: README.md at commit e0e161a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts