Is Ref Tools safe and trustworthy?

tashan scores Ref Tools on public evidence — tashan score 35.0/100, it is currently abandoned, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, its declared dependencies reach: network. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Ref Tools?

In Claude Code: run `claude mcp add ref-tools -- npx -y ref-tools-mcp`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Ref Tools?

See the linked source repository..

‹ The Index

Ref Tools

npm

ModelContextProtocol server for Ref

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Docs & Knowledge — see all ranked ›

Install (Claude Code):

claude mcp add ref-tools -- npx -y ref-tools-mcp

Looking for a replacement? npx tashan-cli doctor is free and tells you everything above about your whole config. tashan Pro names the replacement — which one, and how it measures. $6/mo.

tashan score: 35.0
Adoption: 877/wk
Upkeep: 47.0
Freshness: 32.0
Evidence coverage: 100% of the inputs this score can use
Health: abandoned

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 3.0.3 — this package, not its dependency tree

Makes network requestsfrom declared dependencies

Can carry remote content into your agentit can pull third-party text into the model's context — treat what it returns as untrusted input

No build provenanceno attestation — the published artifact cannot be traced to its source

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Ref Tools scores 35 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-ref-tools-mcp.svg)](https://tashan.sh/capability/pkg-ref-tools-mcp.html)

npm ↗ · pkg:ref-tools-mcp

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?