Prometeo MCP Server

A MCP Server for Prometeo API

Local serverstdioPython

What is the Prometeo MCP Server?

A MCP Server for Prometeo API

What it actually does

A server implementation for MCP (Model Context Protocol) to connect Prometeo API. Include functions to access banking information, validate accounts and query CURP.

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
curp_queryAllows you to validate and retrieve information associated with an existing CURP (Clave Única de Registro de Población) by providing the CURP code directly. This function is essential for verifying Mexican identity docum
curp_reverse_queryEnables retrieval of a CURP by providing personal demographic data instead of the CURP itself. This function requires name, surnames, gender, birthdate, and state of registration to find the corresponding CURP.
validate_accountValidates bank account information across multiple Latin American countries (Argentina, Brazil, Colombia, Chile, Ecuador, Mexico, Peru, Uruguay) and the United States. This function verifies if an account exists and retu
get_validation_resultRetrieves the status or result of a previously initiated account validation request. This is particularly useful for asynchronous validations that may take time to process through banking systems.
get_tasksRetrieves information about system tasks and their statuses. This function is useful for monitoring background processes and understanding the overall system state.
banking_loginEstablishes a connection with a banking provider by authenticating user credentials. It handles multi-factor authentication scenarios by returning a session key that can be used for subsequent operations. If two-factor a
banking_get_accountsRetrieves a list of all accounts associated with an authenticated banking session. This provides account numbers, types, balances, and other relevant details once a user is successfully logged in.
banking_get_movementsObtains transaction history (movements) for a specific account within a defined date range. This function requires an active session key, account number, currency code, and the desired date range for the transactions.
banking_logoutSecurely terminates an active banking session, ensuring proper cleanup of authentication tokens and session data.
crossborder_create_intentCreate a crossborder payin intent using the destination_id, concept, currency, amount, customer and external_id. Payins support: virtual account (MX) or QR code (BR, PE).
crossborder_create_payoutCreate a crossborder payout transfer for the local rail. For MX uses SPEI, for BR uses PIX and for PE uses CCE.
crossborder_get_intentGet a crossborder payin intent by intent_id. Able to get the status of the intent.
crossborder_get_payoutGet a crossborder payout transfer by payout_id. Able to get the status of the payout.
crossborder_list_intents

Configuration

VariableDescriptionRequired
PROMETEO_API_KEYCredential the server authenticates with.Yes
PROMETEO_ENVIRONMENTConfiguration value read at startup.Optional

Example prompts to try

  • “Use Prometeo to curp query.”
  • “Use Prometeo to curp reverse query.”
  • “Use Prometeo to validate account.”

Frequently asked questions

Python 3.11+ is required. The server uses Pydantic v2.x, FastMCP, and the Prometeo API SDK.