MaxMind minFraud MCP by usefulapi
io.usefulapi/maxmind-minfraudusefulapi.iostreamable-httpv1.40.4Scanned
MCP server for MaxMind minFraud — score transactions for fraud risk from your AI assistant.
4 tools: 1 can delete or cancel things and 3 do something that can't be undone.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 3
- 3 findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the MaxMind minFraud MCP by usefulapi can do
The MaxMind minFraud MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: minfraud_report_transaction) and do things that cannot be undone, such as sending, paying or publishing (minfraud_score, minfraud_insights and minfraud_factors). None of its tools only reads.
3 tools can send data out of your system (minfraud_score, minfraud_insights and minfraud_factors).
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.40.4.
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.
4 tools
Deletes or cancels 1Claude Code: deny
minfraud_report_transactionWRITE — submits fraud feedback to MaxMind.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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).
Annotations the server declares
- title: Report a transaction outcome
- destructiveHint: true
Can't be undone 3Claude Code: ask
minfraud_factorsThe most detailed assessment: everything in Insights PLUS risk_score_reasons and per-factor subscores explaining WHY the score is what it is.Can send data out1 finding
Why it is in this group
- The input carries an amount (input.order.amount) and a currency, so it moves money.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.billing.phone_number): what the tool writes goes there.
Findings
- Warn
The server marks "minfraud_factors" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The input carries an amount (input.order.amount) and a currency, so it moves money.
Description, as the server wrote it 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.
Annotations the server declares
- title: minFraud Factors (risk reasons + subscores)
- readOnlyHint: true
minfraud_insightsScore a transaction AND get detailed risk insights: IP geolocation, email/address/device attributes, and per-component risk on top of the risk_score.Can send data out1 finding
Why it is in this group
- The input carries an amount (input.order.amount) and a currency, so it moves money.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.billing.phone_number): what the tool writes goes there.
Findings
- Warn
The server marks "minfraud_insights" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The input carries an amount (input.order.amount) and a currency, so it moves money.
Description, as the server wrote it 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.
Annotations the server declares
- title: minFraud Insights (detailed risk)
- readOnlyHint: true
minfraud_scoreScore a transaction for fraud risk.Can send data out1 finding
Why it is in this group
- The input carries an amount (input.order.amount) and a currency, so it moves money.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.billing.phone_number): what the tool writes goes there.
Findings
- Warn
The server marks "minfraud_score" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The input carries an amount (input.order.amount) and a currency, so it moves money.
Description, as the server wrote it 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.
Annotations the server declares
- title: minFraud risk score
- readOnlyHint: 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 untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- 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.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://maxmind-minfraud.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://maxmind-minfraud.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
- Warnminfraud_score
The server marks "minfraud_score" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The input carries an amount (input.order.amount) and a currency, so it moves money.
The server marks "minfraud_insights" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The input carries an amount (input.order.amount) and a currency, so it moves money.
- Warnminfraud_factors
The server marks "minfraud_factors" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The input carries an amount (input.order.amount) and a currency, so it moves money.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://maxmind-minfraud.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://maxmind-minfraud.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http maxmind-minfraud https://maxmind-minfraud.usefulapi.io/mcpclaude mcp add --transport http maxmind-minfraud https://maxmind-minfraud.usefulapi.io/mcpRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__maxmind-minfraud__minfraud_score",
"mcp__maxmind-minfraud__minfraud_insights",
"mcp__maxmind-minfraud__minfraud_factors"
],
"deny": [
"mcp__maxmind-minfraud__minfraud_report_transaction"
]
}
}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 maxmind-minfraud. Review it before you use it.
Capability tags behind 3 rules
- mcp__maxmind-minfraud__minfraud_score outbound
- mcp__maxmind-minfraud__minfraud_insights outbound
- mcp__maxmind-minfraud__minfraud_factors outbound
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/io.usefulapi/maxmind-minfraud/verify?hash=455c85474fa5086bedeb696d9155141f1d141a4a167f499fc081a4bd6725588c" | jq -e '.changed == false'Pinned hash 455c85474fa5, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/maxmind-minfraud/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/maxmind-minfraud)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
MaxMind minFraud MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MaxMind minFraud MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 3 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 MaxMind minFraud MCP by usefulapi delete data?
- Yes. 1 tool can delete, cancel or revoke something: minfraud_report_transaction.
Can the MaxMind minFraud MCP by usefulapi do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: minfraud_score, minfraud_insights and minfraud_factors.
What tools does the MaxMind minFraud MCP by usefulapi have?
- 4 tools: 1 destructive, 3 irreversible. minfraud_report_transaction, minfraud_score, minfraud_insights and minfraud_factors.
Does the MaxMind minFraud MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the MaxMind minFraud MCP by usefulapi send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): minfraud_score, minfraud_insights and minfraud_factors.
Has the MaxMind minFraud MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.