Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
DEPRECATED: no live endpoint (collection-prod.inspcdn.net does not resolve)
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
LEGITI_API_KEY, LEGITI_BASE_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"legiti": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-legiti"
],
"env": {
"LEGITI_API_KEY": "your-value",
"LEGITI_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add legiti --env LEGITI_API_KEY=your-value --env LEGITI_BASE_URL=your-value -- npx -y @codespar/mcp-legitiFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"legiti": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-legiti"
],
"env": {
"LEGITI_API_KEY": "your-value",
"LEGITI_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"legiti": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-legiti"
],
"env": {
"LEGITI_API_KEY": "your-value",
"LEGITI_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
LEGITI_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account codespar, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: LEGITI_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0-alpha.4) reached the registry 41 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, SwarmMemo
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Talk with agent swarms: rooms, private messages and paid tasks for AI agents
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 withLEGITI_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.
| 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.
| 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. |
npm install @codespar/mcp-legiti@alpha
LEGITI_API_KEY="eyJhbGciOi..." # JWT bearer token; required
LEGITI_BASE_URL="..." # optional; defaults to https://collection-prod.inspcdn.net
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.
evaluate_order and evaluate_sale return one of three decisions:
approve — ship itreject — block the salemanual — route to manual reviewEvaluation is synchronous; the response may take up to ~20 seconds.
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.track_event (create). Update on price/capacity/date changes.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.update_order.mark_order_fraudulent. This is Legiti's primary ML feedback channel — unreported chargebacks degrade future decision quality for similar buyers.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.
Shipped as 0.1.0-alpha.1. Legiti's public documentation is tighter than ClearSale's or Konduto's:
POST /evaluation, plus the Collection API (account, event, sale, transfer, auth, password) shape and the Authorization: Bearer scheme.POST /v2/order, PUT /v2/order, POST /v2/order/mark_fraudulent).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.
# stdio (default — for Claude Desktop, Cursor, etc)
npx @codespar/mcp-legiti
MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-legiti
fraud — fourth server in this CodeSpar category alongside ClearSale, Konduto, and Sift. 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.
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.
MIT