
Mcp Stp Spei
io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Oct 24, 2026
STP/SPEI — Mexican instant bank transfers
Overview
Local MCP server for STP/SPEI, Mexico's instant bank transfer system, letting an assistant create, inspect, cancel and reconcile transfers and manage accounts,
- What you can do
- Create, retrieve, list and cancel SPEI transfers, and create or list refunds (devoluciones). Check account balances for one or all company accounts. Validate CLABE account numbers locally or online, list participating banks and look up a bank by code. Fetch CEP payment receipts and generate reconciliation reports by date. Register, list and delete webhook URLs for STP event notifications.
- When to use it
- Useful when an assistant needs to work with Mexican SPEI payments: preparing or tracking transfers, checking balances, validating CLABE numbers, reconciling transactions or wiring webhook notifications. It is an early alpha, so it suits evaluation and testing rather than production payment flows.
- Requirements
- Runs as a local process via npm (install the alpha dist-tag, pin exact versions). Requires the STP_API_KEY secret and the STP_COMPANY identifier as environment variables; credentials come from STP. Optional MCP_HTTP and MCP_PORT enable an HTTP transport. Network access to the STP API is needed.
Installation
In SourceWeft
- Open Mcp Stp Spei in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP STP/SPEI
Alpha release — published under the
alphanpm dist-tag. Endpoint paths follow public docs and BACEN/provider conventions but have not been fully live-validated. Pin exact versions during0.x.x-alpha. Install withnpm install <pkg>@alpha.
MCP server for STP/SPEI — Mexican instant bank transfer system (equivalent to Brazil's PIX).
Quick Start
Environment Variables
Tools (18)
Auth
Uses API key + digital signature authentication. The API key is sent as a Bearer token, and the company identifier is included in requests. Obtain credentials from STP.
API Reference
Enterprise
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
Authentication
Set these environment variables before launching the server:
STP_API_KEY(required, secret) — API key for STPSTP_COMPANY(required) — Company identifier for STP
Issue credentials at the provider's developer portal: https://stpmex.com/docs.
License
MIT
Source: packages/mexico/stp-spei/README.md at commit d0a519a
Tools
0Version history
1- v0.2.0-alpha.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts