Skip to main content
L

Legiti

@codespar/mcp-legiti Β· v0.2.0-alpha.4

πŸ‡§πŸ‡· BrazilFraud & RiskAuth Β· API Keybeta18 tools2 env varsprereleasedeprecated on npm

BR ticketing-native fraud prevention (formerly Inspetor, SΓ£o Paulo). 4th fraud entry. Order evaluation + Collection API for events/accounts/auth tracking. Alpha on npm β€” public docs thinner than ClearSale/Konduto; tool shapes match docs-backend repo.

Deprecated on npm: No live endpoint: collection-prod.inspcdn.net does not resolve. See https://github.com/codespar/mcp-dev-latam/tree/main/packages/fraud/legiti

MIT Β· deprecated on npm

Limitations

  • v0.2.0-alpha.4 is a prerelease; npm has no stable release of this package.
Package
@codespar/mcp-legiti
Version
0.2.0-alpha.4 Β· prerelease
npm dist-tag
latest
Category
Fraud & Risk
Auth
API Key
Country
πŸ‡§πŸ‡· Brazil
License
MIT
Transport
stdio Β· streamable-http

Quickstart

Before you use it.

This package is deprecated on npm, so this page offers no install command or client config. No live endpoint: collection-prod.inspcdn.net does not resolve. See https://github.com/codespar/mcp-dev-latam/tree/main/packages/fraud/legiti

Environment variables2 variables
LEGITI_API_KEYLegiti API key (JWT-format bearer token). Use the sandbox key while testing β€” Legiti trains its ML models on every request, so test data hitting a production key pollutes the model.requiredsecret
LEGITI_BASE_URLLegiti API base URL. Defaults to https://collection-prod.inspcdn.net. Legiti issues customer-specific base URLs β€” override per contract.optional

Names read from the package code (@codespar/mcp-legiti@0.2.0-alpha.4). Descriptions and flags come from its manifest. Self-hosted, you hold the credentials.

Tools

What your agent can call.

18 tools, as the package's tools/list returns them.

evaluate_order

Submit an order to Legiti for real-time fraud evaluation via the v2 order endpoint. Returns a decision (approve / reject / manual) synchronously β€” response may take up to ~20s. Include as much context as possible: account, payment (tokenized card bin+last4), CPF, billing/shipping, and for ticketing flows the event_date_id / sale_items.

update_order

Notify Legiti of a status change on an existing order (e.g. payment captured, shipped, cancelled, refunded). Feeds the ML model β€” required for ongoing decision quality. Use mark_order_fraudulent for confirmed chargebacks instead.

mark_order_fraudulent

Report a confirmed chargeback / fraud outcome back to Legiti. This is Legiti's primary ML feedback channel β€” unreported chargebacks degrade future decision quality for similar buyers. Call this after the issuer confirms the chargeback, not on mere suspicion.

evaluate_sale

Legacy single-shot sale evaluation via POST /evaluation. Synchronous β€” returns { inspetor_decision: 'approve' | 'reject' | 'manual' }. Prefer evaluate_order (v2) for new integrations; use this when you only have the minimal required fields or for feature parity with older Legiti/Inspetor integrations.

track_account

Notify Legiti of an account lifecycle event (created / updated / deleted). Legiti's ML model treats the Account as a primary entity and needs every state change to score future sales accurately.

track_event

Notify Legiti of an Event (concert, show, match, session) lifecycle change. Events are primary entities in Legiti's ticketing-native model β€” scoring for ticket sales depends on up-to-date event metadata (date, venue, capacity, price tiers).

track_sale

Notify Legiti of a Sale state change (created / updated). For initial sale creation without asking for a decision, set request_evaluation=false on evaluate_order instead. Use this for post-creation updates that aren't status transitions (e.g. sale items added/removed before capture).

track_auth

Notify Legiti of an authentication or password event (login attempt, logout, password recovery request, password reset). Login/logout and password activity are strong signals for account-takeover fraud β€” feed every attempt, successful or failed.

track_login

Notify Legiti of a login attempt (successful or failed). Convenience wrapper over track_auth that hard-codes action='login'. Failed logins are critical signal for ATO (account-takeover) β€” feed every attempt, including the ones blocked by your auth layer.

track_logout

Notify Legiti of a logout event. Convenience wrapper over track_auth with action='logout'. Useful for session-duration features in ATO models.

track_signup

Notify Legiti of a new account creation. Convenience wrapper over track_account with action='create'. Send this at the moment the account is provisioned β€” Legiti uses signup recency as a fraud signal.

track_account_update

Notify Legiti of an account profile change (email, phone, CPF, address). Convenience wrapper over track_account with action='update'. Pass any fields that changed β€” omitted fields are not interpreted as cleared.

Names and descriptions come from the package's tools/list (@codespar/mcp-legiti@0.2.0-alpha.4). A kind (read, write, delete) is shown only when the package annotates its tools or each tool was verified one by one; neither exists for this server yet.

Compatibility

MCP is a protocol. Any client that speaks it can mount this server.

The CodeSpar runtime does not route this server. Mount it in your client over stdio Β· streamable-http.

Protocol

Any MCP client

stdio Β· streamable-http

Questions

Before you install.

How do I install the Legiti MCP server?

The npm package @codespar/mcp-legiti is deprecated, so this page shows no install command for it. The registry says: No live endpoint: collection-prod.inspcdn.net does not resolve. See https://github.com/codespar/mcp-dev-latam/tree/main/packages/fraud/legiti

What can my agent do with Legiti?

Legiti exposes 18 tools for fraud & risk. Your agent calls them directly; the full list is above.

How does Legiti authenticate, and how are credentials stored?

Legiti uses API Key. Self-hosted, you hold the credentials: the server reads them from its environment variables.

How does Legiti handle upstream API changes?

Every server is versioned independently on npm. This one is deprecated (see the notice above), so the page does not suggest pinning a version.

Is Legiti open source? How do I report a bug?

Yes. Legiti is MIT-licensed and published on npm as @codespar/mcp-legiti, source on GitHub (link in the Details panel). Report issues on the package repository; security issues go to security@codespar.dev, and we respond within 24 hours.

Pairs well with

Fraud & Risk Β· same category.

C

ClearSale

@codespar/mcp-clearsale Β· 18 tools

Brazilian fraud prevention pioneer (founded 2001). Order risk scoring, device fingerprinting, chargeback feedback. Alpha release on npm β€” endpoints pending validation against contract-gated ClearSale developer portal.

Open
K

Konduto

@codespar/mcp-konduto Β· 18 tools

BR fraud analytics β€” more API-first than ClearSale. Order analysis, blocklist/allowlist/review-list management, chargeback feedback via status updates. Bundle with ClearSale for score comparison or failover. Alpha on npm β€” 3 brief endpoints not in public docs; core verified against docs.konduto.com.

Open
S

Sift

@codespar/mcp-sift Β· 20 tools

Global ML-based fraud detection β€” events + scores + decisions + labels feedback. Alpha on npm β€” paths verified against SiftScience/sift-ruby SDK.

Open

Start in seconds.

This package is deprecated on npm; read the notice above before using it.

Legiti β€” MCP server Β· 18 tools | CodeSpar