Developer · Local MCP server
URLs-LE
Extract URLs from documentation, configuration and code, with their protocol and position.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nolindnaidoo/urls-le- Version
- 2.3.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- nolindnaidoo (GitHub) · 11 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/nolindnaidoo) · how
- Website
- letools.dev/tools/urls-le
- Repository
- github.com/nolindnaidoo/urls-le
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | urls-le-mcp | 2.3.3 | stdio |
How to connect URLs-LE
URLs-LE runs locally from a Node.js package published to the npm registry: urls-le-mcp version 2.3.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y urls-le-mcp@2.3.3.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"urls-le": {
"command": "npx",
"args": [
"-y",
"urls-le-mcp@2.3.3"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from nolindnaidoo (GitHub)
| Server | Runs |
|---|---|
| Colors-LEExtract colors from stylesheets and code, with their notation and position. | Local · stdio |
| Dates-LEExtract dates and timestamps from logs, data files and code, with their format and position. | Local · stdio |
| EnvSync-LECompare dotenv files and report which keys are missing or extra, by name only. | Local · stdio |
| Numbers-LEExtract numeric values from config files, data files and plain text. | Local · stdio |
| Paths-LEExtract file and directory paths from config files and code, with their kind and position. | Local · stdio |
| Regex-LEExtract regular expressions from code, each with a ReDoS safety verdict. | Local · stdio |
| Scrape-LEAnalyse robots.txt content and report whether a path may be crawled. | Local · stdio |
| Secrets-LEDetect hardcoded secrets in source and config. Reports masked previews, never the values. | Local · stdio |
| Strings-LEExtract string values from config files, data files and plain text. | Local · stdio |
| Unicode-LEFind the Unicode that hides meaning: bidi controls, invisibles, homoglyphs and mixed scripts. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| UptyBotsUptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| URL to Clean Markdown for LLMs & RAGFetch URLs and return clean Markdown for RAG - nav, ads and boilerplate stripped. | Remote · HTTPLive check: sign-in required |
| UrlhausURLhaus MCP - wraps abuse.ch URLhaus malware URL database (free, no auth) | Remote · HTTPLive check: ✓ handshake |
| URLpipeRead any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse. | Remote · HTTPLive check: ✓ handshake |
| US Code of Federal RegulationsLook up, search, and track changes to the US Code of Federal Regulations (eCFR). | Local · stdio |
| UsageMax public observabilityRead-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data. | Remote · HTTPLive check: ✓ handshake |
| Useful Utilities63 tools an LLM can't do alone, in focused subsets: file edits, live data, real checksums. | Remote · HTTP, SSELive check: sign-in required |
| UseMyContext.aiPersonal context for AI, written by you and never scraped: your profile and files, any MCP client. | Remote · HTTPLive check: ✓ handshake |