maxmind-minfraud
Server Details
MCP server for MaxMind minFraud — score transactions for fraud risk from your AI assistant.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
4 toolsminfraud_factorsminFraud Factors (risk reasons + subscores)Read-onlyInspect
The most detailed assessment: everything in Insights PLUS risk_score_reasons and per-factor subscores explaining WHY the score is what it is. Same request body as minfraud_score. API: POST /minfraud/v2.0/factors.
| Name | Required | Description | Default |
|---|---|---|---|
| No | |||
| event | No | ||
| order | No | ||
| device | No | Info about the device/connection. device.ip_address is the most important input. | |
| account | No | ||
| billing | No | ||
| payment | No | ||
| shipping | No | ||
| credit_card | No | ||
| custom_inputs | No | Custom inputs configured in your minFraud account. | |
| shopping_cart | No |
minfraud_insightsminFraud Insights (detailed risk)Read-onlyInspect
Score a transaction AND get detailed risk insights: IP geolocation, email/address/device attributes, and per-component risk on top of the risk_score. Same request body as minfraud_score. API: POST /minfraud/v2.0/insights.
| Name | Required | Description | Default |
|---|---|---|---|
| No | |||
| event | No | ||
| order | No | ||
| device | No | Info about the device/connection. device.ip_address is the most important input. | |
| account | No | ||
| billing | No | ||
| payment | No | ||
| shipping | No | ||
| credit_card | No | ||
| custom_inputs | No | Custom inputs configured in your minFraud account. | |
| shopping_cart | No |
minfraud_report_transactionReport a transaction outcomeDestructiveInspect
WRITE — submits fraud feedback to MaxMind. Report the real-world outcome of a transaction (e.g. it was a chargeback or confirmed fraud) so minFraud can improve future scoring. This mutates MaxMind's model of your traffic; it is not a read. Requires a tag and at least one identifier (ip_address, maxmind_id, minfraud_id, or transaction_id). API: POST /minfraud/v2.0/transactions/report (returns HTTP 204).
| Name | Required | Description | Default |
|---|---|---|---|
| tag | Yes | REQUIRED. The outcome you are reporting for this transaction. | |
| notes | No | Free-form notes about the transaction. | |
| ip_address | No | Identifier: the IP address of the reported transaction. | |
| maxmind_id | No | Identifier: the 8-character maxmind_id from a prior response. | |
| minfraud_id | No | Identifier: the minfraud_id (UUID) from a prior response. | |
| transaction_id | No | Identifier: your own transaction_id sent at scoring time. | |
| chargeback_code | No | The chargeback reason code, if tag=chargeback. |
minfraud_scoreminFraud risk scoreRead-onlyInspect
Score a transaction for fraud risk. Returns the overall risk_score (0.01–99), IP risk, disposition, and remaining query funds — the lightest, cheapest assessment. Send at least device.ip_address (plus email/billing/order for a better score). API: POST /minfraud/v2.0/score.
| Name | Required | Description | Default |
|---|---|---|---|
| No | |||
| event | No | ||
| order | No | ||
| device | No | Info about the device/connection. device.ip_address is the most important input. | |
| account | No | ||
| billing | No | ||
| payment | No | ||
| shipping | No | ||
| credit_card | No | ||
| custom_inputs | No | Custom inputs configured in your minFraud account. | |
| shopping_cart | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!