MCP Legiti

Name: MCP Legiti
Author: codespar

作者：codespar版本 0.2.0-alpha.4i★ –i在你的电脑上运行

注册名称io.github.codespar/mcp-legiti

安装

概览

作者提供的说明（英文原文）

DEPRECATED: no live endpoint (collection-prod.inspcdn.net does not resolve)

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：LEGITI_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： LEGITI_API_KEY, LEGITI_BASE_URL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "legiti": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-legiti"
      ],
      "env": {
        "LEGITI_API_KEY": "your-value",
        "LEGITI_BASE_URL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add legiti --env LEGITI_API_KEY=your-value --env LEGITI_BASE_URL=your-value -- npx -y @codespar/mcp-legiti

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "legiti": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-legiti"
      ],
      "env": {
        "LEGITI_API_KEY": "your-value",
        "LEGITI_BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "legiti": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-legiti"
      ],
      "env": {
        "LEGITI_API_KEY": "your-value",
        "LEGITI_BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

LEGITI_API_KEY 机密必填 env
Legiti 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.
LEGITI_BASE_URL env
Legiti API base URL. Defaults to https://collection-prod.inspcdn.net. Legiti issues customer-specific base URLs — override per contract.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 codespar 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32715 个服务器的 0%
发布到注册中心的时间比此分类中其他 32715 个服务器的 50% 更新
基础检查结果等于或优于此分类中其他 32715 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

MCP Legiti 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：LEGITI_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.2.0-alpha.4）于41天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, First Sale Scout

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

First Sale Scout

作者：firstsale.pro

Playbooks and a 14-day checklist for founders winning their first paying customers.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@codespar/mcp-legiti

Deprecated: no live endpoint. Measured on 2026-09-27 against two public DNS resolvers (8.8.8.8 and 1.1.1.1): collection-prod.inspcdn.net, the host this server calls, does not resolve in DNS. No tool in this server reaches a service. The package is deprecated on npm and stays in this repository for reference only. If you have a working endpoint, point the server at it with LEGITI_BASE_URL. To bring the package back, open an issue in mcp-dev-latam with the provider's documented base URL.

MCP server for Legiti — Brazilian fraud prevention, ticketing-native with a simple synchronous evaluation API.

Fourth entry in the CodeSpar fraud category, after @codespar/mcp-clearsale, @codespar/mcp-konduto, and @codespar/mcp-sift. Legiti (formerly Inspetor, São Paulo) occupies the mid-size BR tier: smaller public footprint than ClearSale, more vertical depth than Konduto for ticketing / events, and a simpler API surface than Sift.

Positioning

	Strength	Typical fit
ClearSale	BR pioneer (2001), large chargeback history	Default for large BR retail
Konduto	BR, API-first, behavioral device intel	Digital-native BR ecommerce
Legiti (this)	BR, ticketing-native, sync evaluation	BR ticketing marketplaces, mid-size retail
Sift	Global, multi-abuse-type ML, workflows	International enterprise

BR merchants frequently bundle 2-3 of these for best-of-breed scoring — Legiti for its ticketing-specific signals, ClearSale or Konduto for the generalist fraud layer, Sift for cross-border flows.

Tools (18)

Tool	Purpose
`evaluate_order`	Submit an order to Legiti for real-time fraud evaluation via the v2 order endpoint.
`update_order`	Notify Legiti of a status change on an existing order (e.g.
`mark_order_fraudulent`	Report a confirmed chargeback / fraud outcome back to Legiti.
`evaluate_sale`	Legacy single-shot sale evaluation via POST /evaluation.
`track_account`	Notify Legiti of an account lifecycle event (created / updated / deleted).
`track_event`	Notify Legiti of an Event (concert, show, match, session) lifecycle change.
`track_sale`	Notify Legiti of a Sale state change (created / updated).
`track_auth`	Notify Legiti of an authentication or password event (login attempt, logout, password recovery request, pas...
`track_login`	Notify Legiti of a login attempt (successful or failed).
`track_logout`	Notify Legiti of a logout event.
`track_signup`	Notify Legiti of a new account creation.
`track_account_update`	Notify Legiti of an account profile change (email, phone, CPF, address).
`track_password_recovery`	Notify Legiti of a password recovery request (the 'forgot password' click).
`track_event_view`	Notify Legiti that a user viewed an event/show page.
`track_payment`	Notify Legiti of a payment-method-level event (authorization attempt, capture, refund, void).
`get_decision`	Fetch the latest Legiti decision for an order.
`update_decision_status`	Manually override Legiti's decision for an order — typically used to accept or decline a sale that landed i...
`mark_dispute_resolution`	Report the outcome of a chargeback dispute back to Legiti — i.e.

Install

npm install @codespar/mcp-legiti@alpha

Environment

LEGITI_API_KEY="eyJhbGciOi..."   # JWT bearer token; required

LEGITI_BASE_URL="..." # optional; defaults to https://collection-prod.inspcdn.net

Authentication

Bearer token (JWT-format):

Authorization: Bearer <LEGITI_API_KEY>

Legiti issues separate sandbox and production keys. The sandbox key tags every request as test data so it does NOT train the ML model. Always develop and run integration tests with the sandbox key — hitting production with test data pollutes the model.

Decision values

evaluate_order and evaluate_sale return one of three decisions:

approve — ship it
reject — block the sale
manual — route to manual review

Evaluation is synchronous; the response may take up to ~20 seconds.

Typical flow (ticketing)

At signup / login, call track_account (create/update) and track_auth (login/logout, password_recovery, password_reset). Every auth attempt — successful or failed — is valuable signal for account-takeover detection.
When a new event (concert, show, match) is published on the platform, call track_event (create). Update on price/capacity/date changes.
At checkout, call evaluate_order with the sale, account, payment, CPF, and the primary event_date_id. Act on the returned decision: approve → ship, reject → block, manual → human review.
As the order progresses (paid, shipped, delivered, cancelled, refunded), call update_order.
When a chargeback is confirmed by the issuer, call mark_order_fraudulent. This is Legiti's primary ML feedback channel — unreported chargebacks degrade future decision quality for similar buyers.

Typical flow (non-ticketing ecommerce)

Skip track_event. The event_date_id fields become optional in evaluate_order — Legiti will still evaluate on account + sale + payment signal, though ticketing-vertical features will be unused.

Alpha note

Shipped as 0.1.0-alpha.1. Legiti's public documentation is tighter than ClearSale's or Konduto's:

Documented in open-source `github.com/legiti/docs-backend`: POST /evaluation, plus the Collection API (account, event, sale, transfer, auth, password) shape and the Authorization: Bearer scheme.
Documented on `docs.legiti.com` integration guides: the v2 order family (POST /v2/order, PUT /v2/order, POST /v2/order/mark_fraudulent).
Dropped from the original category spec: create_rule / list_rules / update_rule / delete_rule — no public custom-rules surface exists on Legiti. If a customer contract exposes one, promote to 0.2.0.

Promote to 0.1.0 once the v2 order payload schema is confirmed in production.

Run

# stdio (default — for Claude Desktop, Cursor, etc)

npx @codespar/mcp-legiti

HTTP (for server-to-server testing)

MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-legiti

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