updated 2026-08-15 10:11 UTC

mcp-agent

lastmile-ai/mcp-agent

Build effective agents using Model Context Protocol and simple workflow patterns

Agent Frameworks Python Grade D Listed Apache-2.0
23.2/100
Rank #899 of 1283
Compare mcp-agent

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-01-25 · 202d ago
Recent change
Rank +1

Is mcp-agent safe? mcp-agent scores 23.2/100 (Grade D), ranked #899 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 72% of recent commits are signed; last pushed 2026-01-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#95 BitFun — 23.5 (D) → #96 Franklin — 23.4 (D) → #98 AWorld — 22.9 (D) → #99 chidori — 22.7 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 53 spots (#850 → #903)
2026-08-08
Rank Moved
Rank dropped 379 spots (#465 → #844)
2026-07-28
Rank Moved
Rank dropped 13 spots (#410 → #423)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Refresh maintenance signals The repo was last pushed 202 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for mcp-agent View Agent Frameworks Report missing data
37.3
Activity sub-score · out of 100
#97
In Agent Frameworks

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-15 10:11 UTC · Repo last pushed 202 days ago — may be stale

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
8.5k
Forks
877
Last Push
2026-01-25
202 days ago
Commits (4 wk)
0
Downloads (7d)
7,548
pypi
HN mentions (30d)
—
Open Issues
75
Rank Change
▲9
was #908

Analysis

HVTrust Dimensions vs Agent Frameworks

23.2 / 100 · 67.0% confidence

mcp-agent Agent Frameworks average (118 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.6 / 25
4.6 below avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.1 below avg 11.6
Maintenance60% last-push freshness · 40% commit activity
0 / 20
14.2 below avg 14.2
AdoptionLog-scaled stars · package downloads
14.6 / 20
3.2 above avg 11.4

Activity Inputs

37.3 / 100
StarsRepository reach
23.6 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
72%
of last 100 commits verified

Is mcp-agent safe?

Public trust evidence for mcp-agent 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-agent publish package provenance?
No published build provenance is currently detected for mcp-agent. 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-agent have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for mcp-agent. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is mcp-agent actively maintained?
Stale. The repository has not been pushed to in 202 days. Consider whether the project is still being maintained.
What license does mcp-agent use?
mcp-agent ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are mcp-agent's commits signed?
72% of the last 100 commits to mcp-agent 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-agent appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
6 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
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

Maintain mcp-agent?

For maintainers

HVTrust scores mcp-agent 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
Rank 9Listed 2Delisted 1
2026-08-10
Rank Moved
Rank dropped 53 spots (#850 → #903)
2026-08-08
Rank Moved
Rank dropped 379 spots (#465 → #844)
2026-07-28
Rank Moved
Rank dropped 13 spots (#410 → #423)
2026-07-15
Rank Moved
Rank dropped 17 spots (#390 → #407)
2026-07-14
Rank Moved
Rank dropped 29 spots (#361 → #390)
2026-07-13
Rank Moved
Rank dropped 39 spots (#322 → #361)
2026-06-24
Rank Moved
Rank dropped 32 spots (#280 → #312)
2026-06-23
Rank Moved
Rank dropped 21 spots (#259 → #280)
2026-06-21
Rank Moved
Rank dropped 18 spots (#233 → #251)
2026-06-08
Newly Listed
First tracked at rank #205
2026-06-07
Removed From Active Tracking
Removed from active tracking
2026-06-06
Newly Listed
First tracked at rank #202
GitHub → PyPI: mcp-agent

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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