updated 2026-09-26 06:32 UTC

Ref Tools MCP

ref-tools/ref-tools-mcp

Helping coding agents never make mistakes working with public or private libraries without wasting the context window.

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.0 / 10
Provenance None
Signed commits 23%
Last push 12d ago
Compare Ref Tools MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Ref Tools MCP scores 50.2/100 (Grade C), ranked #931 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 3.0/10; 23% of recent commits are signed; last pushed 2026-09-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Ref Tools MCP compares in MCP Servers

  1. #530 Cr7258 Elasticsearch MCP Server 50.3 +0.1
  2. #531 MCP Server 12306 50.3 +0.1
  3. #532 Ref Tools MCP 50.2 this agent
  4. #533 Openevidence MCP 50.2 ±0
  5. #534 MCP Eu Ai Act 50.1 −0.1

Bars show each HVTrust score; the tick marks Ref Tools MCP’s 50.2.

Where the 50.2 comes from

HVTrust dimensions vs the MCP Servers average

50.2 / 100 · 100.0% confidence

Ref Tools MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.9 / 25
5.4 below 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
11.1 / 17
1.1 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
11.2 / 20
0.9 below avg 12.1
AdoptionLog-scaled stars · package downloads
11.2 / 20
4.0 above 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-25
Rank Moved
Rank dropped 10 spots (#922 → #932)
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 3.0/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Ref Tools MCP View MCP Servers Report missing data
50.5
Activity sub-score · out of 100
#532
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 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 06:32 UTC · Repo last pushed 12 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
1.2k
Forks
70
Last Push
2026-09-14
12 days ago
Commits (4 wk)
0
Downloads (7d)
773
npm
HN mentions (30d)
—
Open Issues
4
Rank Change
▲1
was #932

Analysis

Activity Inputs

50.5 / 100
StarsRepository reach
18.4 / 30
FreshnessLast push recency
23.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.6 / 20

Supply Chain Trust

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

Common questions about Ref Tools MCP

Public trust evidence for Ref Tools 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 Ref Tools MCP publish package provenance?
No published build provenance is currently detected for Ref Tools MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Ref Tools MCP have an OpenSSF Scorecard?
Ref Tools MCP has an OpenSSF Scorecard score of 3.0/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 Ref Tools MCP actively maintained?
Maintained. Last push was 12 days ago.
What license does Ref Tools MCP use?
Ref Tools MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ref Tools MCP's commits signed?
23% of the last 100 commits to Ref Tools 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
high confidence
Implemented
Ref Tools MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency 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 Ref Tools 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

Maintain Ref Tools MCP?

For maintainers

HVTrust scores Ref Tools 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
Rank 22HVTrust 4Listed 2Grade 2Scorecard 1Score 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 10 spots (#922 → #932)
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 122 spots (#1040 → #918)
2026-09-23
HVTrust Changed
HVTrust up 26.4pts (24.0 → 50.4)
2026-09-22
Newly Listed
First tracked at rank #1040
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 12 spots (#919 → #907)
2026-09-14
Grade Changed
Trust grade D → C
2026-09-14
Rank Moved
Rank rose 135 spots (#1043 → #908)
2026-09-14
HVTrust Changed
HVTrust up 5.3pts (45.3 → 50.6)
2026-09-14
Activity Score Changed
Activity score up 11pts (41 → 52)
2026-09-12
Rank Moved
Rank dropped 11 spots (#1023 → #1034)
2026-09-09
Rank Moved
Rank dropped 15 spots (#1001 → #1016)
2026-09-08
Rank Moved
Rank dropped 12 spots (#989 → #1001)
2026-09-07
Rank Moved
Rank dropped 37 spots (#952 → #989)
2026-09-06
Rank Moved
Rank dropped 15 spots (#937 → #952)
2026-09-05
Rank Moved
Rank dropped 48 spots (#889 → #937)
2026-09-04
Rank Moved
Rank dropped 35 spots (#854 → #889)
2026-09-03
Rank Moved
Rank rose 325 spots (#1179 → #854)
2026-09-03
HVTrust Changed
HVTrust up 17.7pts (28.8 → 46.5)
2026-09-02
Rank Moved
Rank dropped 37 spots (#1142 → #1179)
2026-09-01
Rank Moved
Rank dropped 45 spots (#1097 → #1142)
2026-08-31
Rank Moved
Rank dropped 28 spots (#1069 → #1097)
2026-08-30
Rank Moved
Rank dropped 54 spots (#1015 → #1069)
2026-08-29
Rank Moved
Rank dropped 52 spots (#963 → #1015)
2026-08-28
Rank Moved
Rank dropped 35 spots (#928 → #963)
2026-08-27
Rank Moved
Rank dropped 25 spots (#903 → #928)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.0/10
2026-08-26
Rank Moved
Rank rose 351 spots (#1254 → #903)
2026-08-26
HVTrust Changed
HVTrust up 13.7pts (15.4 → 29.1)
2026-08-16
Rank Moved
Rank dropped 24 spots (#1228 → #1252)
2026-08-10
Rank Moved
Rank dropped 77 spots (#1147 → #1224)
2026-08-08
Newly Listed
First tracked at rank #1146
GitHub → npm: ref-tools-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/ref-tools-mcp.svg)](https://hvtracker.net/agents/ref-tools-mcp)
HTML:
<a href="https://hvtracker.net/agents/ref-tools-mcp"><img src="https://hvtracker.net/badge/ref-tools-mcp.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