Numbers-LE
Extract every hardcoded number in a codebase, so a person can check them
No editor in the loop? npx -y numbers-le-mcp runs the same engine as an MCP server, so an agent can call extract_numbers with nothing else installed, and cargo install numbers-le puts the same check in a terminal. Every way to install it.
What Numbers-LE does
Numbers are the values most likely to be wrong and least likely to be read. Numbers-LE pulls every numeric value out of a config, fixture or data file into a plain list, so ranges and outliers are visible at a glance instead of buried in syntax. It parses JSON, YAML, CSV, TOML, INI and .env, and falls back to scanning plain text for anything else.
What people use it for
Data validation
Pull the numbers out of a config or fixture and eyeball the ranges at a glance.
Config audits
Compare ports, thresholds and limits across INI, TOML and .env files.
CSV work
Extract everything, one column, or several columns into separate documents.
6 commands in the palette
Open the command palette and type the name. Nothing is bound to a shortcut by default — the editor's keymap is the user's, not ours.
numbers-le.extractNumbersnumbers-le.postProcess.dedupenumbers-le.postProcess.sortnumbers-le.csv.toggleStreamingnumbers-le.openSettingsnumbers-le.helpInstall Numbers-LE
VS Code
ext install nolindnaidoo.numbers-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension OffensiveEdge.numbers-leVS Code forks pull from Open VSX, where the namespace is OffensiveEdge.
Zed
npx -y numbers-le-mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and extract_numbers appears in its tool list. There is no one-click listing in Zed's extension registry yet.
AI agents
npx -y numbers-le-mcpRuns Numbers-LE's engine as an MCP server, so an agent can call extract_numbers with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where it ships
One engine, 6 places to get it. The ids differ by registry — copy the one for the editor you use.
Zed
built from Rust in the tool reponumbers-leOpenno listing yet — this links Zed’s instructions for adding it by hand
Where Numbers-LE lives
- VS Code Marketplacenumbers-le
- Open VSXfor Cursor and VSCodium
- npmnumbers-le-mcp
- GitHubsource, issues, changelog
- MCP registryio.github.nolindnaidoo/numbers-le
The other 15
Extract every string in a codebase, with its position, so a person can read them
Extract every file path in a codebase, and say whether it still points at anything
Extract every color in a codebase, and say which ones are not in your palette
Extract every URL in a codebase, with its protocol and exact position
Extract every date and timestamp, and the exact instant each one resolves to
Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name
Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside
Extract every IP address, CIDR block and MAC, normalized and classified by scope
Find every regex in a codebase, and report which can be driven into catastrophic backtracking
Check whether a page is scrapeable before the scraper is written, and say when it cannot tell
Find where one dependency is constrained differently across a repository's manifests
Identify the i18n library a project uses, then audit its catalogs by that library's rules
Find hardcoded credentials in a codebase, and never print one into the report
Compare the dotenv files in a tree, and say which keys are missing from which
Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts