How do I install Dev Latam?

Dev Latam is a local plugin. Install it using npm package: @codespar/mcp-epayco 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: EPAYCO_PUBLIC_KEY, EPAYCO_PRIVATE_KEY, EPAYCO_TEST. 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.2LocalNew

Free

MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks

About

MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks

Security Report

4.2

Use Caution4.2High Risk

This is a monorepo aggregating 110 MCP servers for Latin American commerce APIs. The codebase is well-organized with appropriate permissions for its purpose (network_http, env_vars). The analyzed Sift server example exhibits solid security practices: proper API key handling via environment variables, structured authentication patterns, and no hardcoded secrets. However, the broad scope of the monorepo (spanning payments, banking, fiscal, identity, crypto across 6 countries) introduces inherent complexity and trust surface. Individual servers require API keys to third-party providers, and users must trust each package's implementation. The README and package structures are transparent, but no centralized security audit or dependency scanning framework is evident in the provided code. 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 · 9 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.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

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

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:

ePayco public keyOptional

Environment variable: EPAYCO_PUBLIC_KEY

ePayco private keyRequired

Environment variable: EPAYCO_PRIVATE_KEY

"true" flags payloads as test mode. Defaults to "true" — set "false" for production.Optional

Environment variable: EPAYCO_TEST

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-codespar-mcp-epayco": {
      "env": {
        "EPAYCO_TEST": "your-epayco-test-here",
        "EPAYCO_PUBLIC_KEY": "your-epayco-public-key-here",
        "EPAYCO_PRIVATE_KEY": "your-epayco-private-key-here"
      },
      "args": [
        "-y",
        "mcp-dev-latam"
      ],
      "command": "npx"
    }
  }
}