Is Agrobr MCP safe to use?

Agrobr MCP has an HVTrust score of 46.5/100 (Grade D), ranked #1030 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Agrobr MCP?

Agrobr MCP scores 46.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 27 GitHub stars and is categorized under MCP Servers.

Agrobr MCP

bruno-portfolio/agrobr-mcp

MCP server for Brazilian agricultural data — connect LLMs to 10 public data sources via agrobr

MCP Servers Python Listed MIT

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

OSSF Scorecard 3.4 / 10

Provenance Attested

Signed commits 58%

Last push 198d ago

Compare Agrobr MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Agrobr MCP scores 46.5/100 (Grade D), ranked #1030 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.4/10; 58% of recent commits are signed; last pushed 2026-03-12. Every point is earned from checkable signals — never paid placement. How scoring works →

How Agrobr MCP compares in MCP Servers

#602 Funplay Godot MCP 46.8 +0.3
#603 Scrapegraph MCP 46.8 +0.3
#604 Agrobr MCP 46.5 this agent
#605 Devcontainer MCP 46.4 −0.1
#606 Synter Media AI MCP Server 46.1 −0.4

Bars show each HVTrust score; the tick marks Agrobr MCP’s 46.5.

Where the 46.5 comes from

HVTrust dimensions vs the MCP Servers average

46.5 / 100 · 100.0% confidence

Agrobr MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

14.7 / 25

4.4 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.4 / 17

0.8 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.1 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.4 / 20

1.8 below avg 7.2

Quick Trust Read

What Would Improve It

Improve maintenance to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.4/10. Tighten the weakest checks to improve public safety evidence.

Refresh maintenance signals The repo was last pushed 198 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Agrobr MCP View MCP Servers Report missing data

13.1

Activity sub-score · out of 100

#604

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-03-12

198 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

was #1030

Analysis

Activity Inputs

13.1 / 100

StarsRepository reach

8.7 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

4.4 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

3.4 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

58%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about Agrobr MCP

Public trust evidence for Agrobr MCP 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 Agrobr MCP publish package provenance?

Yes. Agrobr MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Agrobr MCP have an OpenSSF Scorecard?

Agrobr MCP has an OpenSSF Scorecard score of 3.4/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 Agrobr MCP actively maintained?

Stale. The repository has not been pushed to in 198 days. Consider whether the project is still being maintained.

What license does Agrobr MCP use?

Agrobr MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Agrobr MCP's commits signed?

58% of the last 100 commits to Agrobr MCP 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

medium confidence

Implemented

Agrobr MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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

high confidence

Warning

1 package source mismatch detected

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 Agrobr MCP'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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-09-23

Provenance Added

Package provenance attestation detected

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain Agrobr MCP?

For maintainers

HVTrust scores Agrobr MCP 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Rank Moved

Rank rose 251 spots (#1272 → #1021)

2026-09-23

HVTrust Changed

HVTrust up 32.1pts (14.3 → 46.4)

2026-09-22

Newly Listed

First tracked at rank #1272

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank rose 10 spots (#1029 → #1019)

2026-09-12

Rank Moved

Rank dropped 13 spots (#1013 → #1026)

2026-09-09

Rank Moved

Rank dropped 12 spots (#994 → #1006)

2026-09-08

Rank Moved

Rank dropped 12 spots (#982 → #994)

2026-09-07

Rank Moved

Rank dropped 34 spots (#948 → #982)

2026-09-06

Rank Moved

Rank dropped 15 spots (#933 → #948)

2026-09-05

Rank Moved

Rank dropped 52 spots (#881 → #933)

2026-09-04

Rank Moved

Rank dropped 31 spots (#850 → #881)

2026-09-03

Rank Moved

Rank dropped 51 spots (#799 → #850)

2026-09-02

Rank Moved

Rank dropped 46 spots (#753 → #799)

2026-09-01

Rank Moved

Rank dropped 29 spots (#724 → #753)

2026-08-31

Rank Moved

Rank dropped 36 spots (#688 → #724)

2026-08-30

Scorecard Added

OSSF Scorecard: 3.4/10

2026-08-30

Rank Moved

Rank rose 140 spots (#828 → #688)

2026-08-30

HVTrust Changed

HVTrust up 7.2pts (39.8 → 47.0)

2026-08-29

Rank Moved

Rank dropped 41 spots (#787 → #828)

2026-08-28

Rank Moved

Rank dropped 31 spots (#756 → #787)

2026-08-27

Rank Moved

Rank dropped 23 spots (#733 → #756)

2026-08-26

Rank Moved

Rank dropped 95 spots (#638 → #733)

2026-08-16

Rank Moved

Rank dropped 10 spots (#603 → #613)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-10

Rank Moved

Rank dropped 24 spots (#578 → #602)

2026-08-08

Newly Listed

First tracked at rank #571

GitHub → PyPI: agrobr-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/agrobr-mcp.svg)](https://hvtracker.net/agents/agrobr-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/agrobr-mcp"><img src="https://hvtracker.net/badge/agrobr-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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