Mcp Matera

io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.4Updated Oct 24, 2026

DEPRECATED: no live endpoint (api.matera.com does not resolve)

VerifiedSTDIODesktop onlyFinance Business & Commerce

Server details

Identifier: io.github.codespar/mcp-matera
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account codespar for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.codespar%2Fmcp-matera.svg)](https://sourceweft.com/mcp/io.github.codespar%2Fmcp-matera?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Deprecated local MCP server for Matera, Brazilian core-banking infrastructure, exposing Pix charges, payments, DICT keys and account tools that currently reach

What you can do: Create, retrieve, list and update Pix charges, including static, dynamic and due-dated charges (the README lists 22 tools but says the stable contract is 10 names). Initiate, retrieve, list and refund outbound Pix payments, and list inbound Pix received. Resolve, list, register and delete DICT Pix keys. Register, retrieve and cancel Pix Automático recurrences. Read account balance and statement, and book internal transfers between Matera-held accounts. The README states no tool reaches a service and most calls would return 404s.
When to use it: Only for reference or experimentation if you already have a working Matera endpoint and want an assistant to draft Pix charge, payment, DICT or account operations. Not suitable for production or live money movement, since the package is deprecated and the host it calls does not resolve.
Requirements: Runs locally via npx from the npm package @codespar/mcp-matera, so Node.js is needed. Requires MATERA_CLIENT_ID and MATERA_CLIENT_SECRET, and optionally MATERA_BASE_URL (defaults to the production API host). Network access to a Matera endpoint is needed, but the documented default host does not resolve.

Before you install

Deprecated and unverified: the README says the default API host does not resolve, wire paths are assumed, and the OAuth2 token flow is likely wrong for server integration. Tools would create charges, send and refund money, register or delete Pix keys, cancel recurrences and transfer between accounts. Requires the secret MATERA_CLIENT_SECRET; keep it out of shared configs.

Installation

In SourceWeft

Open Mcp Matera 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

@codespar/mcp-matera

Deprecated: no live endpoint. Measured on 2026-09-27 against two public DNS resolvers (8.8.8.8 and 1.1.1.1): api.matera.com, the host this server calls, does not resolve in DNS. No tool in this server reaches a service. The package is deprecated on npm and stays in this repository for reference only. If you have a working endpoint, point the server at it with MATERA_BASE_URL. To bring the package back, open an issue in mcp-dev-latam with the provider's documented base URL.

MCP server for Matera — Brazilian core-banking infrastructure (BaaS) for fintechs building on top of Pix, DICT, and Pix Automático

[npm] [License: MIT]

Why Matera

Matera is core-banking infrastructure, not a PSP. Per vendor case studies it processes roughly 10% of Brazil's Pix transactions. Its customer is a fintech building on top of Pix — issuing accounts, moving money through DICT, registering Pix Automático agreements — not a merchant accepting Pix (that's what Zoop / Asaas / Mercado Pago are for).

This opens a segment in the CodeSpar catalog distinct from PSP servers: fintech-building-on-top-of-Pix. Matera sits under banking alongside Stark Bank and Open Finance, not under payments.

Use Matera when an agent needs to:

Spin up Pix charges against accounts the fintech itself issued
Do DICT lookups to resolve a Pix key before moving money
Register recurring Pix Automático agreements (BCB 2025 product — few providers are live with this)
Move money bank-to-bank through the fintech's own Matera rails

Quick Start

Claude Desktop

Add to ~/.config/claude/claude_desktop_config.json:

json

{  "mcpServers": {    "matera": {      "command": "npx",      "args": ["-y", "@codespar/mcp-matera"],      "env": {        "MATERA_CLIENT_ID": "your-client-id",        "MATERA_CLIENT_SECRET": "your-client-secret"      }    }  }}

{  "mcpServers": {    "matera": {      "command": "npx",      "args": ["-y", "@codespar/mcp-matera"],      "env": {        "MATERA_CLIENT_ID": "your-client-id",        "MATERA_CLIENT_SECRET": "your-client-secret"      }    }  }}

Claude Code

Cursor / VS Code

Add to .cursor/mcp.json or .vscode/mcp.json:

json

{  "servers": {    "matera": {      "command": "npx",      "args": ["-y", "@codespar/mcp-matera"],      "env": {        "MATERA_CLIENT_ID": "your-client-id",        "MATERA_CLIENT_SECRET": "your-client-secret"      }    }  }}

{  "servers": {    "matera": {      "command": "npx",      "args": ["-y", "@codespar/mcp-matera"],      "env": {        "MATERA_CLIENT_ID": "your-client-id",        "MATERA_CLIENT_SECRET": "your-client-secret"      }    }  }}

Tools (22)

Tool	Purpose
`create_pix_charge_static`	Create a static Pix charge (reusable QR code tied to a merchant Pix key).
`create_pix_charge_dynamic`	Create a dynamic Pix charge (single-use QR with expiration).
`get_pix_charge`	Retrieve a Pix charge (static or dynamic) by txid.
`list_pix_charges`	List immediate Pix charges (BCB /cob) with date and status filters.
`update_pix_charge`	Update an immediate Pix charge (BCB PATCH /cob/{txid}).
`create_pix_charge_due`	Create a due-dated Pix charge (BCB /cobv — Pix com Vencimento).
`get_pix_charge_due`	Retrieve a due-dated Pix charge (BCB GET /cobv/{txid}).
`create_pix_payment`	Initiate an outbound Pix transfer (ordem de pagamento).
`get_pix_payment`	Retrieve an outbound Pix payment by endToEndId.
`refund_pix_payment`	Refund (devolução) a Pix payment.
`list_pix_payments`	List outbound Pix payments with optional filters.
`list_pix_received`	List inbound Pix (Pix recebidos) credited to merchant accounts in a date range.
`resolve_pix_key`	Resolve a Pix DICT key to the account holder's identity and ISPB/branch/account.
`list_dict_keys`	List DICT keys registered to the merchant's accounts on Matera.
`register_dict_key`	Register (claim) a DICT key for a merchant account on Matera.
`delete_dict_key`	Delete a DICT key the merchant owns.
`create_pix_automatico`	Register a Pix Automático recurrence (BCB 2025 recurring Pix product, /rec).
`get_pix_automatico`	Retrieve a Pix Automático recurrence by idRec.
`cancel_pix_automatico`	Cancel an active Pix Automático recurrence.
`get_account_balance`	Get the current balance of a Matera-managed account.
`get_account_statement`	Get the statement (extrato) of a Matera-managed account in a date range.
`internal_transfer`	Book a transfer between two accounts both held on Matera (TED-interno / transferência interna).

Authentication

Matera's public doc index states that server integration uses secret-key + data-signature headers, while OAuth2 is scoped to mobile / web-UI integrations (doc-api.matera.com). The v0.1-alpha scaffold currently implements the OAuth2 client-credentials path against POST /auth/token. That pairing is almost certainly wrong for server-to-server use and will be replaced with the signed-request scheme once we can validate against a live sandbox — see the "Status" section below.

Environment Variables

Variable	Required	Description
`MATERA_CLIENT_ID`	Yes	OAuth2 client_id issued by Matera
`MATERA_CLIENT_SECRET`	Yes	OAuth2 client_secret (secret)
`MATERA_BASE_URL`	No	API base URL. Defaults to `https://api.matera.com`. Sandbox URL varies per product line — ask your Matera contact.

Status

v0.1.0-alpha.1 — tool surface is stable, wire paths are NOT yet verified.

On 2026-04-24 we attempted to validate every endpoint path against doc-api.matera.com. The doc site is reachable in a browser but could not be fetched from our automation environment (DNS / network-gated; no login wall observed). Public search snippets and third-party references confirm the product surface (Pix charges, Pix payments, DICT, Pix Automático) and the authentication model (server = secret-key + data-signature; OAuth2 = end-user only) but do not surface the exact URL paths.

Until we can run the server against a live Matera sandbox, the following remain assumed, not verified:

Area	Value in code	Why it's suspect
Token endpoint	`POST /auth/token` (Basic auth, `grant_type=client_credentials`)	Likely wrong for server integration — see Authentication
Pix charges	`/pix/charges/static`, `/pix/charges/dynamic`, `/pix/charges/{txid}`	Matera likely follows BCB's `/cob` (immediate) / `/cobv` (dated) naming
Pix payments	`/pix/payments`, `/pix/payments/{e2eid}`, `/pix/payments/{e2eid}/refund`	BCB spec names refunds `/pix/{e2eid}/devolucao/{id}`
DICT lookup	`GET /pix/dict/{key}`, `GET /pix/dict/keys`	BCB DICT is RSFN-gated; Matera exposes its own wrapper. Exact path unknown.
Pix Automático	`POST /pix/automatico`	Almost certainly a placeholder. BCB 2025 spec uses `POST /rec` (recurrence) + `/cobr/{txid}` (recurring charge).

The 10 tool names and input schemas above are the public contract and will remain stable. Only the internal HTTP calls in src/index.ts will change when we verify against the sandbox. Using this server against a live Matera tenant today will produce 404s on most calls.

Track the verification work in the repo issues; PR welcome from anyone with a Matera sandbox.

Roadmap

v0.2 (planned)

Signed-request auth path (secret-key + data-signature) for endpoints that require it
Account opening (abertura de conta) — Matera IB product
TED / bank transfers (non-Pix rails)
Webhook event helpers

v0.3 (planned)

Internet Banking Server tools (statements, balances, card management)
Boleto issuance
Pix MED (Mecanismo Especial de Devolução) flow

Want to contribute? Open a PR or request a tool.

Enterprise

Need governance, budget limits, and audit trails for agent-initiated bank transfers? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/banking/matera/README.md at commit d0a519a

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.0-alpha.4LatestSep 27, 2026
v0.2.0-alpha.3Sep 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