Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Numbers-LE

NPM · NUMBERS-LE-MCP

Extract numeric values from config files, data files and plain text.

Available components

0 this week 94 Trust /100

Last scanned (19 hours ago)

Scores higher than 96% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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 & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to nolindnaidoo/numbers-le). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 24 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 254 tokens (~254/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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

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 →

Changelog

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.

  • 20 Nov 26 +1
    • Stability: 0.97 → pass security
  • 19 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 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.

  • 8 Nov 26 −3
    • Stability: pass → 0.83 functional
  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 −6
    • Malware scan: pass → unverified ▼ security
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: nolindnaidoo/numbers-le security
    • MCP protocol: pass → fail ▼ functional
    • Package version: 2.5.0 → 2.8.0 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/numbers-le-mcp@2.8.0

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 nolindnaidoo/numbers-le
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/nolindnaidoo/numbers-le/.github/workflows/release.yml@refs/tags/v2.8.0
Rekor log index 3521750434
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:80832d7df88e07710cfe71fe9d0e0ad882a4c95e614e506e2a3da5e63f084a2a0acf6c03e05272da91b8b95e2e6df447f8f7d689a8fef45e3389adbc6

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~254 tokens

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 →

Tool Tokens
extract_numbers ~254

Extract every numeric value from a document. Parses JSON, YAML, CSV, TOML, INI and dotenv, and reads numeric literals in Python, Rust, Go, Java, Kotlin, C#, C, C++, JavaScript, TypeScript, SQL and shell — including hex, binary, octal, digit separators and type suffixes. Anything else is scanned as plain text, so a format is optional. Returns each number with the notation it was written in, in document order, and its 1-based line and column where the source says exactly where it is: JSON, the source languages and plain text. Parsed formats (YAML, TOML, CSV, INI, dotenv) carry no position.

NameTypeReqDescription
contentstringyesThe document text to scan.
dedupeboolean–Collapse repeated values to their first occurrence.
filenamestring–Filename used to infer the format when `format` is absent, e.g. "config.toml".
formatstring–Document format. Optional — an unrecognised or absent format scans the text directly.
maxResultsinteger–Cap on returned numbers (default 500). meta.truncated reports whether any were dropped.

No output schema declared.

No examples provided.

Install

How do I install the Numbers-LE MCP server?

Numbers-LE runs locally as an npm package, launched with npx -y numbers-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 · numbers-le-mcp

# add to Claude Code
claude mcp add nolindnaidoo-numbers-le -- npx -y numbers-le-mcp
Common questions

What is the Numbers-LE MCP server?

Numbers-LE is an MCP server listed in the public MCP registry as io.github.nolindnaidoo/numbers-le. Extract numeric values from config files, data files and plain text. This page covers its npm package (numbers-le-mcp).

Is the Numbers-LE MCP server safe to use?

Numbers-LE scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Numbers-LE MCP server expose?

Numbers-LE exposes 1 tool: extract_numbers. Their descriptions and schemas cost roughly 254 tokens of context every time the server is loaded.

Is the Numbers-LE MCP server still maintained?

Numbers-LE is still listed as active in the MCP registry. We last reached this channel on 21 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 Numbers-LE MCP server under?

Numbers-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.

What did VerifyMCP test on the Numbers-LE MCP server?

VerifyMCP ran 16 checks on Numbers-LE, 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.