MCP Legiti

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/codespar-mcp-legiti

About

Use cases: payments-billing, security-scanning

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

2 read · 16 write · 0 delete

Secrets

1 (API keys, tokens or passwords)

Install scripts

None found

Runs as

Node.js package

Tools (18)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

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

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

• get_decision

  Fetch the latest Legiti decision for an order. Returns the decision (approve / reject / manual), score, and the contributing reason codes. Useful for re-checking a sale after async re-scoring or for audit/UI display.

• mark_dispute_resolution

  Report the outcome of a chargeback dispute back to Legiti — i.e. whether the merchant won or lost the chargeback case after representation. Complements mark_order_fraudulent (which reports the chargeback itself). Disputes won are valuable counter-signal.

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

• 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_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.

• 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_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_event_view

  Notify Legiti that a user viewed an event/show page. Browse signal — feeds Legiti's session model so the eventual evaluate_order has context for 'did this buyer actually look at the show before buying tickets?'. Optional but recommended for ticketing flows.

• 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_password_recovery

  Notify Legiti of a password recovery request (the 'forgot password' click). Convenience wrapper over track_auth with action='password_recovery'. Recovery floods are a strong ATO signal.

• track_payment

  Notify Legiti of a payment-method-level event (authorization attempt, capture, refund, void). Distinct from track_sale, which is order-level. Use this when you process payments separately from sale state — e.g. multi-installment captures or refund flows.

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

Signals

Stars

274

Forks

51

Open issues

14

Weekly downloads

17

Last commit (this folder)

Sep 27, 2026 (1 month ago)

Last release

Sep 27, 2026 (1 month ago)

Last package publish

Sep 27, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.codespar/mcp-legiti

Version

0.2.0-alpha.4

Auth

API key

Packages

npm @codespar/mcp-legiti

License

MIT

Repository

github.com/codespar/mcp-dev-latam

First seen

Oct 24, 2026

Last checked

Oct 25, 2026

Source

Official MCP Registrygithub-graphql