MCP Dev Latam

Open-source MCP servers for Latin American commerce — Pix, NF-e, banking, fiscal, logistics, and messaging across Brazil, Mexico, Argentina, Colombia, Chile, and Peru. MIT, on npm.

MCP Servers TypeScript Listed MIT

Is MCP Dev Latam safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.6 / 10
Provenance None
Signed commits 94%
Last push 28d ago
Compare MCP Dev Latam
Suggest a correction

In detail: MCP Dev Latam scores 54.0/100 (Grade C), ranked #817 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.6/10; 94% of recent commits are signed; last pushed 2026-08-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Dev Latam compares in MCP Servers

  1. #455 MCP Baepsae 54.2 +0.2
  2. #456 MCP Fns Check 54.1 +0.1
  3. #457 MCP Dev Latam 54.0 this agent
  4. #458 RU Marketplace MCP 54.0 ±0
  5. #459 Funplay Unity MCP 54.0 ±0

Bars show each HVTrust score; the tick marks MCP Dev Latam’s 54.0.

Where the 54.0 comes from

HVTrust dimensions vs the MCP Servers average

54.0 / 100 · 100.0% confidence

MCP Dev Latam MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.4 / 25
in line with avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.0 / 20
in line with avg 12.0
AdoptionLog-scaled stars · package downloads
7.4 / 20
in line with avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
49.6
Activity sub-score · out of 100
#457

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 12:32 UTC · Repo last pushed 28 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
271
Forks
50
Last Push
2026-08-29
28 days ago
Commits (4 wk)
2
Downloads (7d)
14
npm
HN mentions (30d)
—
Open Issues
8
Rank Change
▼2
was #815

Analysis

Activity Inputs

49.6 / 100
StarsRepository reach
14.6 / 30
FreshnessLast push recency
21.1 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
7.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Sep 20, 2026
Signed Commits
94%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 9
CII-Best-Practices 0
Code-Review 1
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Common questions about MCP Dev Latam

Public trust evidence for MCP Dev Latam is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does MCP Dev Latam publish package provenance?
No published build provenance is currently detected for MCP Dev Latam. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Dev Latam have an OpenSSF Scorecard?
MCP Dev Latam has an OpenSSF Scorecard score of 4.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is MCP Dev Latam actively maintained?
Maintained. Last push was 28 days ago.
What license does MCP Dev Latam use?
MCP Dev Latam ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Dev Latam's commits signed?
94% of the last 100 commits to MCP Dev Latam are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
MCP Dev Latam appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to MCP Dev Latam's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain MCP Dev Latam?

For maintainers

HVTrust scores MCP Dev Latam from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 18HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 147 spots (#955 → #808)
2026-09-23
HVTrust Changed
HVTrust up 28.5pts (25.7 → 54.2)
2026-09-22
Newly Listed
First tracked at rank #955
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 16 spots (#784 → #800)
2026-09-11
Rank Moved
Rank dropped 46 spots (#724 → #770)
2026-09-08
Rank Moved
Rank dropped 41 spots (#669 → #710)
2026-09-07
Rank Moved
Rank dropped 53 spots (#616 → #669)
2026-09-06
Rank Moved
Rank rose 49 spots (#665 → #616)
2026-09-05
Rank Moved
Rank dropped 79 spots (#586 → #665)
2026-09-04
Rank Moved
Rank dropped 22 spots (#564 → #586)
2026-09-03
Rank Moved
Rank dropped 29 spots (#535 → #564)
2026-09-02
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank rose 450 spots (#985 → #535)
2026-09-02
HVTrust Changed
HVTrust up 18.4pts (37.6 → 56.0)
2026-09-01
Rank Moved
Rank dropped 43 spots (#942 → #985)
2026-08-31
Rank Moved
Rank dropped 34 spots (#908 → #942)
2026-08-30
Rank Moved
Rank dropped 41 spots (#867 → #908)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.6/10
2026-08-29
Rank Moved
Rank rose 338 spots (#1205 → #867)
2026-08-29
HVTrust Changed
HVTrust up 18.7pts (19.0 → 37.7)
2026-08-26
Rank Moved
Rank dropped 44 spots (#1148 → #1192)
2026-08-16
Rank Moved
Rank dropped 23 spots (#1125 → #1148)
2026-08-15
Rank Moved
Rank dropped 14 spots (#1111 → #1125)
2026-08-10
Rank Moved
Rank dropped 63 spots (#1041 → #1104)
2026-08-08
Newly Listed
First tracked at rank #1070

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-dev-latam.svg)](https://hvtracker.net/agents/mcp-dev-latam)
HTML:
<a href="https://hvtracker.net/agents/mcp-dev-latam"><img src="https://hvtracker.net/badge/mcp-dev-latam.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON