Konduto MCP server

Read from the package source without running it. The installed server may list more.

• add_to_allowlist

  Add a value to the Konduto allowlist (trusted). Future orders matching the value are auto-approved without full ML scoring. Use sparingly — allowlist overrides fraud signals.

• add_to_blocklist

  Add a value to the Konduto blocklist. Any future order matching the value is auto-declined. Useful for known-bad emails, IPs, tax IDs, or card BIN+last4 pairs observed in confirmed fraud.

• add_to_reviewlist

  Add a value to the Konduto reviewlist. Future orders matching the value are forced into manual review regardless of score. Useful for ambiguous signals that warrant human eyes.

• get_orderwrite action

  Retrieve the current analysis state of an order. Returns decision (approved / declined / review / not_analyzed), numeric score, and recommendation. Useful when the initial response was 'review' or when polling after async re-scoring.

• query_allowlist

  Check whether a value is currently on the Konduto allowlist. Konduto's public docs explicitly support email; other dimensions are accepted by symmetry with the blocklist contract but only email is guaranteed.

• query_blocklist

  Check whether a value is currently on the Konduto blocklist.

• query_reviewlist

  Check whether a value is currently on the Konduto reviewlist. Konduto's public docs explicitly support email; other dimensions are accepted by symmetry with the blocklist contract but only email is guaranteed.

• remove_from_allowlistwrite action

  Remove a value from the Konduto allowlist. Future orders matching the value will once again undergo full ML scoring.

• remove_from_blocklistwrite action

  Remove a value from the Konduto blocklist.

• remove_from_reviewlistwrite action

  Remove a value from the Konduto reviewlist. Future orders matching the value will be scored normally instead of being forced into review.

• report_chargeback

  Report a confirmed chargeback for an order. Convenience wrapper around update_order_status with status='fraud' — the primary feedback signal Konduto's ML model uses to retrain on similar buyers. Call this as soon as the chargeback dispute is confirmed (not when first received).

• report_order_approvedwrite action

  Report that an order was ultimately approved by the merchant. Convenience wrapper around update_order_status with status='approved'. Use after Konduto returned 'review' and a human approved the order, or when the merchant overrode a 'declined' recommendation.

• report_order_declinedwrite action

  Report that an order was ultimately declined by the merchant. Convenience wrapper around update_order_status with status='declined'. Use after manual review concluded the order should be rejected, or when the acquirer declined the payment.

• send_order_for_analysiswrite action

  Submit an order to Konduto for fraud analysis. Returns a decision (approved / declined / review / not_analyzed), a numeric score, and a recommendation. Include as much signal as possible — billing + shipping, ip, items, payment, and (crucially) the visitor id captured by Konduto's browser JS SDK — to maximize decision quality.

• update_allowlist_entrywrite action

  Update an existing allowlist entry — typically to extend or shorten the expiration window. Konduto's docs recommend short windows (1-2 days) for allowlist entries since they bypass ML scoring entirely.

• update_blocklist_entrywrite action

  Update an existing blocklist entry — typically used to extend or shorten the expiration window (expires_at) without removing and re-adding the entry. The (type, value) pair must already exist on the blocklist.

• update_order_statuswrite action

  Notify Konduto of the merchant's final status for an order. Feeds Konduto's ML model and is required for ongoing decision quality. Common transitions: new → approved, new → declined, approved → canceled, approved → fraud (when a chargeback is confirmed).

• update_reviewlist_entrywrite action

  Update an existing reviewlist entry — typically to extend or shorten the expiration window without removing and re-adding the entry.

• Code scan6 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 29 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 75% of 2,174 E-commerce servers

Tools

18

the typical E-commerce server has 6

Tools that change things

61%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

271

more than 95% of 1,047 E-commerce servers

Konduto: common questions

Is Konduto MCP server safe?

Mostly: it is graded B (82/100). Read the Konduto safety report

How do I install Konduto?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Konduto need an API key?

Yes. The registry entry asks for KONDUTO_API_KEY.

Is Konduto maintained?

The last commit was 67 days ago (2026-08-29). The latest release is v0.2.0-alpha.3.

What can I use instead of Konduto?

Servers from other publishers that do the same job: Finance MCP server, Polymarket Toolkit MCP server and Sv Number MCP server.

How does Konduto compare with other E-commerce MCP servers?

safety score 82/100 (higher than 75% of 2,174 E-commerce servers); tools 18 (the typical E-commerce server has 6); tools that change things 61% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.