
Mcp Clearsale
io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Oct 24, 2026
MCP server for ClearSale — Brazilian fraud prevention, order risk scoring, device fingerprinting
Overview
Lets an assistant submit orders to ClearSale for Brazilian fraud scoring, retrieve decisions, and manage related KYC and case workflows.
- What you can do
- Wraps the ClearSale antifraud API in 18 tools covering the analyze-decide-feedback cycle: send_order_for_analysis submits an order, get_order_analysis and get_order_score return its state and 0-100 risk score, and update_order_status reports the merchant's final decision. It also supports device fingerprint sessions, behavior event tracking, CPF/CNPJ and address validation, score lookups by document or contact, OTP/KBA challenges, chargeback notifications, and fraud investigation cases.
- When to use it
- Use it when an assistant needs to work with ClearSale fraud decisions for Brazilian ecommerce orders, for example to submit orders for analysis, poll or report order outcomes, or look up risk signals for a document or contact. It is aimed at merchants already contracted with ClearSale rather than general-purpose use.
- Requirements
- Runs locally over stdio via the npm package @codespar/mcp-clearsale (Node.js required; npx @codespar/mcp-clearsale). Needs a ClearSale-issued bearer token in CLEARSALE_API_KEY, and optionally CLEARSALE_BASE_URL, which defaults to the production API and can be pointed at a contract-issued staging URL. Network access to ClearSale is required; there is no public sandbox.
Installation
In SourceWeft
- Open Mcp Clearsale in the dashboard and add it to a workspace.
- 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
@codespar/mcp-clearsale
MCP server for ClearSale — Brazilian fraud prevention.
ClearSale pioneered fraud analytics in Brazil (founded 2001, São Paulo) and remains the default antifraud layer for most major BR ecommerce. This is the first entry in the CodeSpar fraud category — no other server in the catalog does fraud scoring. Future entries (Konduto, Legiti, Sift, Cybersource) will follow the same analyze → decide → feedback shape.
Tools (18)
Install
Environment
Authentication
Server-side Bearer token:
ClearSale issues the token via the developer portal or through your commercial contract. There is no public sandbox — staging URLs are provisioned per contract; override CLEARSALE_BASE_URL to point at it.
Typical flow
- On page load, the merchant calls
create_device_fingerprint_sessionand embeds ClearSale's browser JS using the returnedsession_token. - At checkout, the merchant calls
send_order_for_analysiswith the samesession_idplus full order, payment, items, and billing/shipping data. - The response carries a decision:
APROVADO(ship it),REPROVADO(block), orEM_ANALISE(pollget_order_analysisor wait for a webhook). - Once the order lifecycle completes, call
update_order_statuswith the final merchant decision — this is required for ongoing model quality. - If a chargeback arrives later, call
create_chargeback_notificationso ClearSale can tune its model.
Run
Category
fraud — first server in this CodeSpar category. Fraud servers share a common shape (analyze → decide → feedback) distinct from payments, which makes cross-provider swaps (ClearSale ↔ Konduto ↔ Legiti) more straightforward than cross-acquirer swaps.
Enterprise
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
License
MIT
Source: packages/fraud/clearsale/README.md at commit d0a519a
Tools
0Version history
1- v0.2.0-alpha.3LatestSep 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