How do I install Dev Latam?

Dev Latam is a local plugin. Install it using npm package: @codespar/mcp-vindi and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Dev Latam safe to use?

Dev Latam was flagged by MCP Marketplace's security scan, scoring 4.2/10 (high risk). It has 2 high or critical findings to review. Review the security report on this page carefully before installing it.

What credentials does Dev Latam need?

Dev Latam requires the following credentials or environment variables: VINDI_API_KEY. You can find setup instructions on the server detail page.

What AI apps work with Dev Latam?

Dev Latam uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Dev Latam MCP Server

by User

Developer ToolsUse Caution4.2Local

Free

MCP server for Vindi — recurring billing, subscriptions, invoices

About

MCP server for Vindi — recurring billing, subscriptions, invoices

Security Report

4.2

Use Caution4.2High Risk

MCP Dev LATAM is a large, well-structured monorepo of 109 MCP servers for Latin American commerce APIs and agentic payment protocols. The codebase itself (README, root package.json, and sampled Sift fraud server) shows no malicious patterns, hardcoded secrets, or dangerous code execution. However, the catalog inherently distributes credentials via environment variables, and several servers are shipped as alpha with unverified endpoint paths. The analyzed Sift server demonstrates solid code quality with proper auth patterns, input validation, and error handling—permissions align with purpose (network_http, env_vars). Primary concerns are: (1) alpha packages with TODO(verify) endpoint paths that could fail silently, (2) reliance on users to secure API keys in env vars across 109 independent packages, and (3) broad permission scope across a distributed catalog (each server can access network and environment independently). These are inherent to the MCP ecosystem and LATAM's fragmented API landscape, not implementation flaws. Supply chain analysis found 2 known vulnerabilities in dependencies (1 critical, 0 high severity). Package verification found 1 issue (1 critical, 0 high severity).

4 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

Unverified package source

We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.

What You'll Need

Set these up before or after installing:

API key for vindiRequired

Environment variable: VINDI_API_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-codespar-mcp-vindi": {
      "env": {
        "VINDI_API_KEY": "your-vindi-api-key-here"
      },
      "args": [
        "-y",
        "mcp-dev-latam"
      ],
      "command": "npx"
    }
  }
}