{
  "markdown": "<p align=\"center\">\n  <img src=\"src/assets/images/icon.png\" alt=\"Numbers-LE Logo\" width=\"96\" height=\"96\"/>\n</p>\n<h1 align=\"center\">Numbers-LE: Zero Hassle Number Extraction</h1>\n<p align=\"center\">\n  <b>Pull every number out of the current file in one keystroke</b><br/>\n  <i>JSON/JSONC, YAML, CSV/TSV, TOML, INI, Environment files, and twelve source languages</i>\n</p>\n\n<p align=\"center\">\n  <a href=\"https://marketplace.visualstudio.com/items?itemName=nolindnaidoo.numbers-le\">\n    <img src=\"https://img.shields.io/badge/Install%20from-VS%20Code-blue?style=for-the-badge&logo=visualstudiocode\" alt=\"Install from VS Code Marketplace\" />\n  </a>\n  <a href=\"https://open-vsx.org/extension/OffensiveEdge/numbers-le\">\n    <img src=\"https://img.shields.io/open-vsx/dt/OffensiveEdge/numbers-le?style=for-the-badge&label=Open%20VSX&color=blue\" alt=\"Open VSX downloads\" />\n  </a>\n  <a href=\"https://www.npmjs.com/package/numbers-le-mcp\">\n    <img src=\"https://img.shields.io/npm/v/numbers-le-mcp?style=for-the-badge&label=MCP%20server&color=blue&logo=npm\" alt=\"numbers-le-mcp on npm\" />\n  </a>\n  <a href=\"https://crates.io/crates/numbers-le\">\n    <img src=\"https://img.shields.io/crates/v/numbers-le?style=for-the-badge&label=Rust%20CLI&color=blue&logo=rust\" alt=\"numbers-le on crates.io\" />\n  </a>\n  <a href=\"https://letools.dev/tools/numbers-le\">\n    <img src=\"https://img.shields.io/badge/LE%20Tools-letools.dev-blue?style=for-the-badge\" alt=\"LE Tools\" />\n  </a>\n</p>\n\n---\n\n<p align=\"center\">\n  <img src=\"src/assets/images/demo.gif\" alt=\"Numbers-LE Demo\" style=\"max-width: 100%; height: auto;\" />\n</p>\n\n> **Useful?** A star or rating is how other developers find it —\n> [★ GitHub](https://github.com/nolindnaidoo/numbers-le) ·\n> [★ Open VSX](https://open-vsx.org/extension/OffensiveEdge/numbers-le/reviews) ·\n> [★ Marketplace](https://marketplace.visualstudio.com/items?itemName=nolindnaidoo.numbers-le&ssr=false#review-details)\n\n## What it does\n\nOpen a file, press `Ctrl+Alt+N` (`Cmd+Alt+N` on Mac), and every numeric value in the document lands in a new editor — deduplicate and sort it from there. Works in VS Code and in VS Code–based editors like Cursor and VSCodium (installable from Open VSX).\n\n- **Data validation** — pull the numbers out of a config or fixture and eyeball ranges at a glance\n- **Config audits** — compare ports, thresholds, and limits across INI/TOML/.env files\n- **CSV work** — extract everything, one column, or several columns into separate documents\n\n## Install\n\n| Where | What you get | Install |\n|---|---|---|\n| **VS Code** | The same extraction, in your editor, on a keystroke | [Marketplace](https://marketplace.visualstudio.com/items?itemName=nolindnaidoo.numbers-le) |\n| **Cursor, VSCodium, Windsurf** | The same extension | [Open VSX](https://open-vsx.org/extension/OffensiveEdge/numbers-le) |\n| **A terminal or a CI step** | The same run over a whole tree, with exit codes | `cargo install numbers-le` · [crates.io](https://crates.io/crates/numbers-le) |\n| **Any MCP agent, via Node** | `extract_numbers` over stdio | `npx numbers-le-mcp` · [npm](https://www.npmjs.com/package/numbers-le-mcp) |\n| **Zed** | The MCP server as a context server | [add it by hand](https://zed.dev/docs/ai/mcp) *(no listing yet)* |\n\n## Use it from an AI agent\n\nThe same engine runs as an [MCP](https://modelcontextprotocol.io) server, so an agent can call it directly instead of you running a command.\n\n| Editor | How |\n|---|---|\n| **VS Code** 1.101+ | Nothing to install — the extension registers `extract_numbers` with agent mode |\n| **Zed** | No listing yet — [add the MCP server by hand](https://zed.dev/docs/ai/mcp) |\n| **Claude Code** | `claude mcp add numbers-le -- npx -y numbers-le-mcp` |\n| **Cursor, Windsurf, anything else** | point it at `npx numbers-le-mcp` |\n\n```\nextract_numbers(content, format?, filename?, dedupe?, maxResults?)\n```\n\nReturns the values in document order, capped at 500 by default with `meta.truncated`. A format is optional — anything unrecognised is scanned as plain text rather than refused.\n\nThe server takes content and returns data — it reads no files and makes no network requests of its own. Published as [`numbers-le-mcp`](https://www.npmjs.com/package/numbers-le-mcp) on npm and as `io.github.nolindnaidoo/numbers-le` in the [MCP registry](https://registry.modelcontextprotocol.io).\n\n<details>\n<summary><b>Configuring it by hand</b> — any host with an MCP config file</summary>\n\nMost hosts read a JSON config. Add one entry:\n\n```json\n{\n  \"mcpServers\": {\n    \"numbers-le\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"numbers-le-mcp\"]\n    }\n  }\n}\n```\n\n`-y` skips the install prompt on first run. Pin a version if you would rather not track releases — `numbers-le-mcp@2.3.1`.\n\nPrefer not to go through `npx` on every launch? Install it once and point at the binary instead:\n\n```bash\nnpm install -g numbers-le-mcp\n```\n\n```json\n{\n  \"mcpServers\": {\n    \"numbers-le\": { \"command\": \"numbers-le-mcp\" }\n  }\n}\n```\n\nIt speaks MCP over stdio and needs no environment variables, no API key and no configuration of its own. To check it before wiring it into anything:\n\n```bash\necho '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/list\"}' | npx -y numbers-le-mcp\n```\n\nThat prints the tool list and exits — if you see `extract_numbers`, the server works.\n\n</details>\n\n## Supported formats\n\n| Format | What counts as a number |\n|---|---|\n| JSON | Number values anywhere in the structure. Quoted numbers (`\"42\"`) are strings, not numbers, and are never extracted |\n| YAML | Number values, including hex/octal int forms and exponents; multi-document (`---`) streams extract from every document |\n| TOML | Integer and float values (dates are not numbers) |\n| CSV | Cells whose entire content is numeric — `19.99` counts, `12abc` and `1,000` do not. No header inference: every row is data |\n| INI | Values whose entire content is numeric (INI values are inherently strings) |\n| Environment | Values whose entire content is numeric (`PORT=3000` yields 3000; `VERSION=1.2.3` yields nothing) |\n\nThe shared policy (one heuristics module, applied to every format): only finite numbers are extracted — `NaN` and `inf`/`.inf` never appear in results — and a coerced string must be numeric in full: plain decimals with optional sign, decimal point, and exponent.\n\nPython, Rust, Go, Java, Kotlin, C#, C, C++, JavaScript, TypeScript, SQL and shell are read by a numeric-literal extractor that understands hex `0xFF`, binary `0b1010`, octal `0o755` and legacy `0755`, digit separators `1_000_000` and `1'000`, and suffixes `123n`, `1.5f`, `10u32`, `100L` — and that knows `u32` is a type name, not the number 32. A dialect changes an answer: `0755` is 493 in C, C++, Go and Java, and 755 in Rust, Python 3, Kotlin and C#.\n\nEvery finding carries the notation it was written in — `decimal`, `hex`, `binary`, `octal`, `scientific`, `bigint`. For anything left over you can pick a format explicitly or fall back to a plain-text scan (no grammar: `v1.2.3` reads as `1.2` and `0.3`).\n\n## The CLI\n\nThe same extraction runs from a terminal or a shell pipeline: a Rust CLI\nin [`crate/`](crate/README.md), sharing one corpus with the extension —\n[`crate/fixtures/`](crate/fixtures/) — so the two can never read a\ndocument differently.\n\n```bash\nnumbers-le .                     # every number in the tree, as JSON\nnumbers-le --values config/      # just the numbers, one per line\nnumbers-le mcp                   # the same extraction over MCP on stdio\n\n# the point of the whole thing:\nnumbers-le --values --dedupe src/ | sort -n > after.txt\ndiff before.txt after.txt        # what constants moved this release\n```\n\n**Somebody has to verify that the rate in the code is the rate in the\nspecification.** A tax percentage, a retention window, a rounding\nboundary. In a regulated setting that check is a deliverable, and the\nperson doing it usually has no checkout and never has the editor open.\n\n**Numbers are printed exactly as JavaScript prints them** — `1e+21`, not\nRust's `1000000000000000000000`. This tool's whole output is numbers as\ntext, so the rendering is the contract, and the corpus pins it.\n\n**Exit codes follow grep** — 0 numbers found, 1 none found, 2 the question\nwas malformed.\n\n## Commands\n\n| Command | Description |\n|---|---|\n| `Numbers-LE: Extract Numbers` (`Ctrl+Alt+N` / `Cmd+Alt+N`) | Extract all numbers from the active document |\n| `Numbers-LE: Deduplicate Numbers` | Remove duplicate numbers from the results |\n| `Numbers-LE: Sort Numbers` | Sort results numerically or by magnitude |\n| `Numbers-LE: Toggle CSV Streaming` | Flip `csv.streamingEnabled` for large CSV files |\n| `Numbers-LE: Open Settings` | Open Numbers-LE settings |\n| `Numbers-LE: Help & Troubleshooting` | Built-in documentation |\n\n## Settings\n\n| Setting | Default | Description |\n|---|---|---|\n| `numbers-le.openResultsSideBySide` | `true` | Open results beside the current editor |\n| `numbers-le.postProcess.openInNewFile` | `true` | Dedupe/Sort write to a new file instead of replacing the editor content |\n| `numbers-le.copyToClipboardEnabled` | `false` | Also copy results to the clipboard (non-CSV) |\n| `numbers-le.dedupeEnabled` | `false` | Deduplicate automatically during extraction |\n| `numbers-le.sortEnabled` | `false` | Sort automatically during extraction |\n| `numbers-le.sortMode` | `off` | `numeric-asc/desc`, `magnitude-asc/desc` |\n| `numbers-le.csv.streamingEnabled` | `false` | Incremental CSV parsing for large files |\n| `numbers-le.showParseErrors` | `false` | Surface parse errors as notifications |\n| `numbers-le.notificationsLevel` | `silent` | `all` = every notification, `important` = warnings + errors, `silent` = errors only |\n| `numbers-le.safety.enabled` | `true` | Guardrails for very large files/outputs |\n| `numbers-le.safety.fileSizeWarnBytes` | `1000000` | Warn above this file size |\n| `numbers-le.safety.largeOutputLinesThreshold` | `50000` | Offer Open/Copy/Cancel above this result count |\n| `numbers-le.safety.manyDocumentsThreshold` | `8` | Confirm before opening this many column documents |\n| `numbers-le.statusBar.enabled` | `true` | Show the status bar item |\n| `numbers-le.telemetryEnabled` | `false` | Local-only event log (see Privacy) |\n\n## Languages\n\nTwelve languages besides English:\n\nGerman · Spanish · French · Indonesian · Italian · Japanese · Korean ·\nPortuguese (Brazil) · Russian · Ukrainian · Vietnamese · Chinese (Simplified)\n\nBoth halves are covered — the manifest (command titles, setting names and\ndescriptions) and everything shown while the extension runs (notifications,\nthe status bar, quick-picks and prompts). The extension follows VS Code's\ndisplay language, so it matches whatever the editor is already set to; no\nsetting of its own.\n\n## Privacy & security\n\n- **No network access.** The extension never sends data anywhere. The `telemetryEnabled` setting only writes events to a local Output Channel you can inspect (`Numbers-LE`).\n- **The MCP server holds the same line.** It takes content as an argument and returns data: no filesystem access, no network calls, no telemetry. Your agent already has file-read tools, so duplicating them inside the server would add a path-traversal surface for no capability. `check:mcp-bundle` fails the build if the server ever imports something that could reach either.\n- Error notifications redact home directories and credential-shaped fragments.\n\n## Documentation\n\n| What | Where |\n|---|---|\n| What the tool is allowed to say — scope, output contract, refusals, non-goals | [`crate/SPEC.md`](crate/SPEC.md) |\n| How the extension is built and held together — architecture, invariants, toolchain, release | [AGENTS.md](AGENTS.md) |\n| How the CLI is built and held together | [`crate/AGENTS.md`](crate/AGENTS.md) |\n| What changed | [CHANGELOG.md](CHANGELOG.md) · [`crate/CHANGELOG.md`](crate/CHANGELOG.md) |\n| The tool's page, and the other fifteen | [letools.dev/tools/numbers-le](https://letools.dev/tools/numbers-le) |\n\n## Performance\n\n<!-- performance:start -->\n| Input | Size | Found | Time | Rate | Scan speed |\n| --- | --- | --- | --- | --- | --- |\n| JSON metrics | 2.18 MB | 120,000 | 22.32 ms | 5,376,475/sec | 97.9 MB/s |\n| CSV data | 0.93 MB | 150,000 | 51.26 ms | 2,926,066/sec | 18.2 MB/s |\n| INI config | 0.42 MB | 30,000 | 20.05 ms | 1,496,430/sec | 20.7 MB/s |\n\nMedian of 7 runs after warmup, on Apple M5 Pro, 24 GB RAM, Node 24.3.0. Inputs are generated\nby `scripts/benchmark.ts` rather than checked in, so the sizes above are\nexactly what was measured. Reproduce with `bun run benchmark`.\n\nThese are machine-specific and are not asserted in CI — a benchmark that gates\na build only tells you how busy the runner was.\n<!-- performance:end -->\n\n## Testing\n\n<!-- coverage:start -->\n| Metric | Coverage |\n| --- | --- |\n| Statements | 90.65% |\n| Branches | 84.08% |\n| Functions | 96.34% |\n| Lines | 92.42% |\n\n358 test cases across 23 files, plus an integration suite that runs\nin a real VS Code extension host and an end-to-end test that installs the\nbuilt `.vsix` into a clean profile.\n\nGenerated from a real run — `coverage/coverage-summary.json` and\n`coverage/test-results.json` — by `scripts/coverage-readme.js`; CI fails if\nthis section drifts. Reproduce with `bun run test:coverage`, and the case\ncount is the one vitest prints.\n<!-- coverage:end -->\n\n## More from the LE family\n\nSixteen single-purpose tools for the work in front of every model. Each ships\na Rust CLI and an MCP server. One page: **[letools.dev](https://letools.dev)**\n\n**Get it out**\n\n- **[String-LE](https://letools.dev/tools/string-le)** — Extract every string in a codebase, with its position, so a person can read them\n- **[Numbers-LE](https://letools.dev/tools/numbers-le)** — Extract every hardcoded number in a codebase, so a person can check them\n- **[Units-LE](https://letools.dev/tools/units-le)** — Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name\n- **[Dates-LE](https://letools.dev/tools/dates-le)** — Extract every date and timestamp, and the exact instant each one resolves to\n- **[IDs-LE](https://letools.dev/tools/ids-le)** — Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside\n- **[IPs-LE](https://letools.dev/tools/ips-le)** — Extract every IP address, CIDR block and MAC, normalized and classified by scope\n- **[URLs-LE](https://letools.dev/tools/urls-le)** — Extract every URL in a codebase, with its protocol and exact position\n- **[Paths-LE](https://letools.dev/tools/paths-le)** — Extract every file path in a codebase, and say whether it still points at anything\n- **[Colors-LE](https://letools.dev/tools/colors-le)** — Extract every color in a codebase, and say which ones are not in your palette\n\n**Check it**\n\n- **[Regex-LE](https://letools.dev/tools/regex-le)** — Find every regex in a codebase, and report which can be driven into catastrophic backtracking\n- **[Versions-LE](https://letools.dev/tools/versions-le)** — Find where one dependency is constrained differently across a repository's manifests\n- **[i18n-LE](https://letools.dev/tools/i18n-le)** — Identify the i18n library a project uses, then audit its catalogs by that library's rules\n- **[Scrape-LE](https://letools.dev/tools/scrape-le)** — Check whether a page is scrapeable before the scraper is written, and say when it cannot tell\n\n**Guard it**\n\n- **[Secrets-LE](https://letools.dev/tools/secrets-le)** — Find hardcoded credentials in a codebase, and never print one into the report\n- **[EnvSync-LE](https://letools.dev/tools/envsync-le)** — Compare the dotenv files in a tree, and say which keys are missing from which\n- **[Unicode-LE](https://letools.dev/tools/unicode-le)** — Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts\n\nEach stands on its own: no shared crate, no published core. Where two of them\nagree, it is because the same answer was right twice.\n\n**Contact** — [nolindnaidoo.com](https://nolindnaidoo.com) · [GitHub](https://github.com/nolindnaidoo) · [LinkedIn](https://www.linkedin.com/in/nolindnaidoo/)\n\n## Also by nolindnaidoo\n\n**Rust** — pixelcoords and pixelactions are one loop: pixelcoords answers\n*where*, pixelactions *acts* there. Their own tools, their own voice — not\npart of the LE family.\n\n- **[pixelcoords](https://github.com/nolindnaidoo/pixelcoords)** — Freeze your screen, mark regions, get pixel-exact coordinates and crops\n  [pixelcoords.dev](https://pixelcoords.dev) · [crates.io](https://crates.io/crates/pixelcoords) · [docs.rs](https://docs.rs/pixelcoords)\n- **[pixelactions](https://github.com/nolindnaidoo/pixelactions)** — Consume human-verified coordinates, perform the interaction, confirm it landed\n  [pixelactions.dev](https://pixelactions.dev) · [crates.io](https://crates.io/crates/pixelactions) · [docs.rs](https://docs.rs/pixelactions)\n\n## License\n\nMIT © [nolindnaidoo](https://github.com/nolindnaidoo)\n",
  "bytes": 16855,
  "sha": "14b05e9cc4ad775da06ddd97d51d986bd4a77474248338f2a8e9458d8ee3c7d1",
  "repo_slug": "nolindnaidoo/numbers-le",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_nolindnaidoo_numbers_le_12625155/readme"
}