Prometeo MCP Server

Created By
prometeoapia year ago
A MCP Server for Prometeo API
Overview

What is Prometeo MCP Server?

Prometeo MCP Server is a server implementation for the Model Context Protocol (MCP) designed to connect with the Prometeo API, enabling access to banking information, account validation, and CURP queries.

How to use Prometeo MCP Server?

To use the Prometeo MCP Server, clone the repository from GitHub, set up a virtual environment, and install the necessary dependencies. You can then run the server using the provided commands for various LLMs (Large Language Models) that support MCP integration.

Key features of Prometeo MCP Server?

  • Supports Python 3.11+
  • Integrates with FastMCP and Prometeo API SDK
  • Provides tools for CURP queries and account validation across multiple Latin American countries
  • Allows cross-border payment functionalities

Use cases of Prometeo MCP Server?

  1. Validating bank accounts in Latin America.
  2. Retrieving CURP information for identity verification.
  3. Facilitating cross-border payments and transactions.

FAQ from Prometeo MCP Server?

  • What programming language is used?

    The server is implemented in Python 3.11 and requires specific libraries like Pydantic and FastMCP.

  • Is there a license for this project?

    Yes, the project is licensed under the MIT License.

  • How can I contribute to the project?

    Contributions are welcome! You can open issues or submit pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
prometeoapi
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago