updated 2026-09-04 14:03 UTC

Augments MCP Server

augmnt/augments-mcp-server

Comprehensive MCP server providing real-time framework documentation access for Claude Code with intelligent caching, mu

MCP Servers TypeScript Grade D Listed MIT
24.2/100
Rank #1257 of 1320
Compare Augments MCP Server

How does it stack up against its MCP Servers 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-03-13 · 175d ago
Recent change
Rank +6

Is Augments MCP Server safe? Augments MCP Server scores 24.2/100 (Grade D), ranked #1257 of 1320 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; recent commits are unsigned; last pushed 2026-03-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#737 Kronan MCP — 24.5 (D) → #738 MCP Mat — 24.3 (D) → #740 Autotask — 24.2 (D) → #741 MCP NixOS — 24.2 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-03
Rank Moved
Rank dropped 37 spots (#1216 → #1253)
2026-09-02
Rank Moved
Rank dropped 33 spots (#1183 → #1216)
2026-09-01
Rank Moved
Rank dropped 45 spots (#1138 → #1183)
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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 175 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Augments MCP Server View MCP Servers Report missing data
19.5
Activity sub-score · out of 100
#739
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 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-09-04 14:03 UTC · Repo last pushed 175 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
128
Forks
20
Last Push
2026-03-13
175 days ago
Commits (4 wk)
0
Downloads (7d)
100
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▼4
was #1253

Analysis

HVTrust Dimensions vs MCP Servers

24.2 / 100 · 67.0% confidence

Augments MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0 / 25
9.5 below avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
0.3 / 20
11.9 below avg 12.2
AdoptionLog-scaled stars · package downloads
7.7 / 20
1.5 above avg 6.2

Activity Inputs

19.5 / 100
StarsRepository reach
12.7 / 30
FreshnessLast push recency
0.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
6.1 / 20

Supply Chain Trust

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

Is Augments MCP Server safe?

Public trust evidence for Augments MCP Server 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 Augments MCP Server publish package provenance?
No published build provenance is currently detected for Augments MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Augments MCP Server have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Augments MCP Server. 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 Augments MCP Server actively maintained?
Slowing down. Last push was 175 days ago — keep an eye on whether activity resumes.
What license does Augments MCP Server use?
Augments MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Augments MCP Server's commits signed?
0% of the last 100 commits to Augments MCP Server 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
Augments MCP Server 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
Match
Published package metadata matches the tracked repo
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 Augments MCP Server'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-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain Augments MCP Server?

For maintainers

HVTrust scores Augments MCP Server 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 13Listed 1Surface 1
2026-09-03
Rank Moved
Rank dropped 37 spots (#1216 → #1253)
2026-09-02
Rank Moved
Rank dropped 33 spots (#1183 → #1216)
2026-09-01
Rank Moved
Rank dropped 45 spots (#1138 → #1183)
2026-08-31
Rank Moved
Rank dropped 29 spots (#1109 → #1138)
2026-08-30
Rank Moved
Rank dropped 45 spots (#1064 → #1109)
2026-08-29
Rank Moved
Rank dropped 49 spots (#1015 → #1064)
2026-08-28
Rank Moved
Rank dropped 38 spots (#977 → #1015)
2026-08-27
Rank Moved
Rank dropped 25 spots (#952 → #977)
2026-08-26
Rank Moved
Rank dropped 104 spots (#848 → #952)
2026-08-24
Rank Moved
Rank dropped 12 spots (#836 → #848)
2026-08-16
Rank Moved
Rank dropped 20 spots (#821 → #841)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-12
Rank Moved
Rank rose 15 spots (#826 → #811)
2026-08-10
Rank Moved
Rank dropped 47 spots (#777 → #824)
2026-08-08
Newly Listed
First tracked at rank #766
GitHub → PyPI: augments-mcp-server

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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