io.github.JustinBeckwith/linkinator-mcp
NPM · LINKINATOR-MCP
MCP server for link checking using linkinator
Available components
Last scanned (20 hours ago)
Scores higher than 93% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security93
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects glob 13.0.6, reached via linkinator > glob. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 33 of 116 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to JustinBeckwith/linkinator-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 67 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 310 tokens (~310/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −2
- CVE-2026-118764 affects this package: medium ▼ security
- CVE-2026-118773 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: pass → 0.97 functional
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 0
- Package version: 1.0.1 → 1.0.3 functional
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/linkinator-mcp@1.0.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | JustinBeckwith/linkinator-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/JustinBeckwith/linkinator-mcp/.github/workflows/release.yaml@refs/heads/main |
| Rekor log index | 2641868272 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a284df8b38e2879f3453c21524c4d4e493ff52db22b40515501bbf1eb364411eb322c80a494cbe4f07a949a43fde8214b24ca7a307d2d9c55585f33b4 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3g3m-2fjr-6pw4 | CVE-2026-118773 | medium | yes | |
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 116 packages
| Packages resolved | 116 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
scan_page ~310
Scan links in a webpage or local file path using linkinator. Checks for broken links, validates anchors, and can crawl recursively. Supports progress notifications for long-running scans.
| Name | Type | Req | Description |
|---|---|---|---|
| allowInsecureCerts | boolean | – | Accept invalid SSL certificates |
| checkCss | boolean | – | Extract and validate URLs in CSS properties |
| checkFragments | boolean | – | Validate URL anchor identifiers |
| cleanUrls | boolean | – | Enable extensionless link resolution (e.g., /about → /about.html) |
| concurrency | number | – | Number of simultaneous connections (default: 100) |
| directoryListing | boolean | – | Auto-serve directory index files |
| linksToSkip | array | – | URL patterns to exclude (regex strings) |
| markdown | boolean | – | Parse and scan markdown files |
| path | string | yes | URL or local file path to scan |
| port | number | – | Server port for local scanning (random port by default) |
| recurse | boolean | – | Follow links recursively on the same domain |
| retry | boolean | – | Retry HTTP 429 responses with retry-after header |
| retryErrors | boolean | – | Retry 5xx errors |
| retryErrorsCount | number | – | Retry attempt limit |
| retryErrorsJitter | number | – | Random delay between retries in milliseconds |
| serverRoot | string | – | Custom disk location where the server starts |
| timeout | number | – | Request timeout in milliseconds (0 = no timeout) |
| userAgent | string | – | Custom user agent header |
No output schema declared.
No examples provided.
How do I install the io.github.JustinBeckwith/linkinator-mcp server?
io.github.JustinBeckwith/linkinator-mcp runs locally as an npm package, launched with npx -y linkinator-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · linkinator-mcp
claude mcp add justinbeckwith-linkinator-mcp -- npx -y linkinator-mcp
What is the io.github.JustinBeckwith/linkinator-mcp server?
io.github.JustinBeckwith/linkinator-mcp is listed in the public MCP registry as io.github.JustinBeckwith/linkinator-mcp. MCP server for link checking using linkinator. This page covers its npm package (linkinator-mcp).
Is the io.github.JustinBeckwith/linkinator-mcp server safe to use?
io.github.JustinBeckwith/linkinator-mcp scores 90 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.JustinBeckwith/linkinator-mcp server expose?
io.github.JustinBeckwith/linkinator-mcp exposes 1 tool: scan_page. Their descriptions and schemas cost roughly 310 tokens of context every time the server is loaded.
Is the io.github.JustinBeckwith/linkinator-mcp server still maintained?
io.github.JustinBeckwith/linkinator-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.JustinBeckwith/linkinator-mcp server under?
io.github.JustinBeckwith/linkinator-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.JustinBeckwith/linkinator-mcp server?
VerifyMCP ran 16 checks on io.github.JustinBeckwith/linkinator-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.