How do I install Dev Latam?

Dev Latam is a local plugin. Install it using npm package: @codespar/mcp-rinne 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 3.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: RINNE_API_KEY, RINNE_SANDBOX, RINNE_EMAIL, RINNE_PASSWORD, RINNE_COMPANY_ID. 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 Caution3.2LocalNew

Free

Brazilian card acquiring API — merchants, cards-on-file, 3DS, PIX, banking, pricing.

About

Brazilian card acquiring API — merchants, cards-on-file, 3DS, PIX, banking, pricing.

Security Report

3.2

Use Caution3.2High Risk

This is a monorepo containing 127 MCP servers for LATAM commerce APIs. The analyzed entry point (Rinne payment server) shows reasonable authentication handling via environment variables, but the codebase exhibits moderate security concerns: overly broad error messages that expose API details, missing input validation on user-supplied parameters, and extensive unvalidated network calls to third-party payment processors. Permissions are appropriate for a payment infrastructure tool, but error handling and validation patterns need hardening. 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 · 11 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 sent as x-api-key header on every request. Organization-level keys see all merchants; merchant-level keys are scoped to one merchant.Required

Environment variable: RINNE_API_KEY

Defaults to sandbox (https://api-sandbox.rinne.com.br/core). Set to "false" for production (https://api.rinne.com.br/core).Optional

Environment variable: RINNE_SANDBOX

Login identifier for the access-management tools (API Keys, Roles, Permissions, org Users, Zipcode lookup), which reject x-api-key by design and require a JWT session.Optional

Environment variable: RINNE_EMAIL

Environment variable: RINNE_PASSWORD

Company to select after JWT login, for accounts with access to multiple companies.Optional

Environment variable: RINNE_COMPANY_ID

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-codespar-mcp-rinne": {
      "env": {
        "RINNE_EMAIL": "your-rinne-email-here",
        "RINNE_API_KEY": "your-rinne-api-key-here",
        "RINNE_SANDBOX": "your-rinne-sandbox-here",
        "RINNE_PASSWORD": "your-rinne-password-here",
        "RINNE_COMPANY_ID": "your-rinne-company-id-here"
      },
      "args": [
        "-y",
        "mcp-dev-latam"
      ],
      "command": "npx"
    }
  }
}