# io.usefulapi/maxmind-minfraud (remote · maxmind-minfraud.usefulapi.io)

MCP server for MaxMind minFraud — score transactions for fraud risk from your AI assistant.

- Trust score: 18/100 (low)
- Change this week: −43
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `maxmind-minfraud.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-maxmind-minfraud/maxmind-minfraud.md), [page](https://verifymcp.io/servers/io-usefulapi-maxmind-minfraud/maxmind-minfraud)

## Channel facts

- Endpoint: `https://maxmind-minfraud.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 429.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-maxmind-minfraud https://maxmind-minfraud.usefulapi.io/mcp
```

### Codex

```toml
[mcp_servers.io-usefulapi-maxmind-minfraud]
url = "https://maxmind-minfraud.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-maxmind-minfraud": {
      "type": "remote",
      "url": "https://maxmind-minfraud.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-maxmind-minfraud --url https://maxmind-minfraud.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-maxmind-minfraud:
    url: "https://maxmind-minfraud.usefulapi.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-maxmind-minfraud": {
      "type": "http",
      "url": "https://maxmind-minfraud.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 18, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified

### 2026-08-02 (score 66, +48)

- [security improvement] Authorization: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20

### 2026-08-01 (score 18, −47)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 65, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 61, +49)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (4)

### `minfraud_score` (~181 tokens)

minFraud risk score

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.

Input parameters:

- `account` (object)
- `billing` (object)
- `credit_card` (object)
- `custom_inputs` (object): Custom inputs configured in your minFraud account.
- `device` (object): Info about the device/connection. device.ip_address is the most important input.
- `email` (object)
- `event` (object)
- `order` (object)
- `payment` (object)
- `shipping` (object)
- `shopping_cart` (array)

### `minfraud_insights` (~168 tokens)

minFraud Insights (detailed risk)

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.

Input parameters:

- `account` (object)
- `billing` (object)
- `credit_card` (object)
- `custom_inputs` (object): Custom inputs configured in your minFraud account.
- `device` (object): Info about the device/connection. device.ip_address is the most important input.
- `email` (object)
- `event` (object)
- `order` (object)
- `payment` (object)
- `shipping` (object)
- `shopping_cart` (array)

### `minfraud_factors` (~165 tokens)

minFraud Factors (risk reasons + subscores)

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.

Input parameters:

- `account` (object)
- `billing` (object)
- `credit_card` (object)
- `custom_inputs` (object): Custom inputs configured in your minFraud account.
- `device` (object): Info about the device/connection. device.ip_address is the most important input.
- `email` (object)
- `event` (object)
- `order` (object)
- `payment` (object)
- `shipping` (object)
- `shopping_cart` (array)

### `minfraud_report_transaction` (~245 tokens)

Report a transaction outcome

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).

Input parameters:

- `chargeback_code` (string): The chargeback reason code, if tag=chargeback.
- `ip_address` (string): Identifier: the IP address of the reported transaction.
- `maxmind_id` (string): Identifier: the 8-character maxmind_id from a prior response.
- `minfraud_id` (string): Identifier: the minfraud_id (UUID) from a prior response.
- `notes` (string): Free-form notes about the transaction.
- `tag` (string, required): REQUIRED. The outcome you are reporting for this transaction.
- `transaction_id` (string): Identifier: your own transaction_id sent at scoring time.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-maxmind-minfraud/maxmind-minfraud#diagnostics

## Score history

- 2026-08-03: 18
- 2026-08-02: 66
- 2026-08-01: 18
- 2026-07-31: 65
- 2026-07-30: 60
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 61
- 2026-07-26: 12

## Links

- Remote endpoint: https://maxmind-minfraud.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-maxmind-minfraud/maxmind-minfraud/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-maxmind-minfraud/maxmind-minfraud/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-maxmind-minfraud/maxmind-minfraud