URLs-LE
NPM · URLS-LE-MCP · SCANNED SEP 29
Extract URLs from documentation, configuration and code, with their protocol and position.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 45 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 196 tokens (~196/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
How do I install the URLs-LE MCP server?
URLs-LE runs locally as an npm package, launched with npx -y urls-le-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 · urls-le-mcp
claude mcp add nolindnaidoo-urls-le -- npx -y urls-le-mcp
{
"mcpServers": {
"nolindnaidoo-urls-le": {
"command": "npx",
"args": [
"-y",
"urls-le-mcp"
]
}
}
} {
"servers": {
"nolindnaidoo-urls-le": {
"command": "npx",
"args": [
"-y",
"urls-le-mcp"
]
}
}
} codex mcp add nolindnaidoo-urls-le -- npx -y urls-le-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nolindnaidoo-urls-le": {
"type": "local",
"command": [
"npx",
"-y",
"urls-le-mcp"
],
"enabled": true
}
}
} openclaw mcp add nolindnaidoo-urls-le --command npx --arg -y --arg urls-le-mcp
mcp_servers:
nolindnaidoo-urls-le:
command: "npx"
args: ["-y", "urls-le-mcp"] {
"McpServers": {
"nolindnaidoo-urls-le": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"urls-le-mcp"
]
}
}
} assistant mcp add nolindnaidoo-urls-le -t stdio -c npx -a -y urls-le-mcp
{
"mcpServers": {
"nolindnaidoo-urls-le": {
"command": "npx",
"args": [
"-y",
"urls-le-mcp"
]
}
}
} 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.
- 29 Sept 26 −2
- Stability: pass → 0.80 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 −2
- Stability: pass → 0.80 functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 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.
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 29 Sept 2026 · Analysed npm/urls-le-mcp@2.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
extract_urls ~196
Extract every URL from a document, with its protocol and 1-based line and column. Reads any text document. Markdown, HTML, CSS, JavaScript, TypeScript, JSON, YAML, Properties, TOML, INI and XML know what to exclude — code fences, comments, non-string tokens; everything else is scanned whole, and `fileType` says which happened.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The document text to scan. |
| dedupe | boolean | – | Collapse repeated URLs to their first occurrence. |
| filename | string | – | Filename used to infer the format when `format` is absent, e.g. "README.md". |
| format | string | – | Document format. Provide this or `filename`. Common extensions and aliases are accepted; anything else is scanned as plain text rather than refused. |
| maxResults | integer | – | Cap on returned URLs (default 500). meta.truncated reports whether any were dropped. |
No output schema declared.
No examples provided.
What is the URLs-LE MCP server?
URLs-LE is an MCP server listed in the public MCP registry as io.github.nolindnaidoo/urls-le. Extract URLs from documentation, configuration and code, with their protocol and position. This page covers its npm package (urls-le-mcp).
Is the URLs-LE MCP server safe to use?
URLs-LE scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 2026. It declares no install or post-install scripts. 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 URLs-LE MCP server expose?
URLs-LE exposes 1 tool: extract_urls. Their descriptions and schemas cost roughly 196 tokens of context every time the server is loaded.
Is the URLs-LE MCP server still maintained?
URLs-LE is still listed as active in the MCP registry. We last reached this channel on 29 September 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 URLs-LE MCP server under?
URLs-LE declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.