reference-mcp

io.github.AbduljabbarBXRPublished by GitHub account AbduljabbarBXRv0.1.6Updated Oct 24, 2026

Reference integrity for AI agents. Scans and verifies links, imports, assets, deps.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lets an assistant scan a project for broken links, imports, assets, and dependency references and report integrity problems.

What you can do
This local MCP server provides reference-integrity checking for AI agents. According to its description, it scans and verifies links, imports, assets, and dependencies, so an assistant can surface references that no longer resolve. The manifest lists no individual tools, so the exact commands and output format are not documented here.
When to use it
Worth adding when an assistant works inside a codebase or content repository and needs to check that links, imports, asset paths, and dependency references still resolve. Useful before releases, refactors, or documentation updates where stale references are a risk.
Requirements
Runs as a local process over stdio, installed from the npm package reference-mcp, so Node.js and npm are needed on the machine. It is desktop-only and has no web executable. The manifest declares no authentication, environment variables, or headers.
Before you install
The manifest declares no credentials, environment variables, or headers, and no write, send, or delete behavior is described. It reads project files to check references, so point it only at directories you are comfortable having scanned. No tools are listed, so verify what it actually reads and reports before relying on it.

Installation

In SourceWeft

  1. Open reference-mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.6LatestSep 18, 2026
  2. v0.1.3Sep 17, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.