Correios MCP server

by codespar·io.github.codespar/mcp-correios·v0.2.0-alpha.3·271 stars

No reviews yet

MCP server for Correios — package tracking, shipping rates, CEP lookup

B82/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B82/100

full report

Adoption

Growing

271 stars

Reviews

Write one

Nobody has reviewed Correios yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Correios tools (21, 7 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

buy_label_rangewrite action
Request a range of SIGEP tracking labels (etiquetas) for a service
calculate_shipping
Calculate shipping rates between two CEPs
cancel_collectionwrite action
Cancel a scheduled collection request
cancel_prepostwrite action
Cancel a pre-posting order
create_collectionwrite action
Schedule a package collection (pickup) from an address
create_prepostwrite action
Create a pre-posting order for shipping
create_reversewrite action
Create a reverse logistics (return) order
find_cep
Look up address by CEP via Correios
find_cep_bulk
Batch address lookup for up to 20 CEPs in a single call
get_collection
Get collection request details by ID
get_delivery_modality
Get delivery modality (forma de entrega) for a CEP and service — whether delivery is domicile, agency pickup, etc.
get_delivery_time
Get estimated delivery time between two CEPs
get_prepost
Get a pre-posting order by ID
get_reverse
Get reverse logistics order details by ID
list_cep_ranges
List CEP ranges (faixas de CEP) served by a given shipping service
list_postal_codes
Search addresses by street name or location (returns matching CEPs)
list_preposts
List pre-posting orders with optional filters (date range, status)
list_services
List available Correios shipping services
post_objectswrite action
Close and post a list of pre-posted objects (fechar postagem SIGEP) — creates a PLP
track_bulk
Track multiple Correios packages in a single call (up to 50 codes)
track_package
Track a package by Correios tracking code

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings

Code scan5 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitystatic API keys via environment variables6/15
Maintenancelast push 29 days ago15/15
Maintainer identityregistry namespace matches repository owner7/10

Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Correios compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 82/100; higher than 63% of 48,255 servers
Tools: 21; the typical server has 7
Tools that change things: 33%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 271; more than 95% of 28,688 servers

What its tools let an agent do: 14 read · 3 create · 1 change · 2 delete · 1 send or post

Install Correios in Claude Code, Cursor or VS Code

Runs npx -y @codespar/mcp-correios on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-correios -- npx -y @codespar/mcp-correios

Add to Cursor

What the publisher says

From the Correios repository's README, as published. We do not edit it. Read it on GitHub

MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute

The Problem

AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).

Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.

MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.

The Solution

Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.

🛒 Customer places order
  → 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
  → 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
  → 📦 Agent generates shipping label (Melhor Envio / Skydropx)
  → 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
  → 📊 Agent records in ERP (Omie / Bling / Tiny)
  → 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)

Six systems. Zero human intervention. One agent.

Agentic Payment Protocols

Four servers for the emerging agentic payment stack:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Correios: common questions

Is Correios MCP server safe?: Mostly: it is graded B (82/100). Read the Correios safety report
How do I install Correios?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Correios need an API key?: Yes. The registry entry asks for CORREIOS_TOKEN.
Is Correios maintained?: The last commit was 67 days ago (2026-08-29). The latest release is v0.2.0-alpha.3.
How does Correios compare with other MCP servers?: safety score 82/100 (higher than 63% of 48,255 servers); tools 21 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.