numbers-le-mcp@2.8.0
VERIFIED· install onlyPublisher claims: "Enables agents to extract hardcoded numeric values from supplied text or code across many data and source-code formats, returning values in document order with notation and available line/column positions. Supports deduplication and truncated result sets." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Not enough was observed to say yet. Nothing executable in the bundle ran; the trace covers the install step only. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try numbers-le-mcp` runs it now and prints the full answer.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-07 and scored it 80/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
'.env.test.local',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary><b>Configuring it by hand</b> — any host with an MCP config file</summary> Most hosts read a JSON config. Add one entry: ```json { "mcpServers": { "numFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.//! **Untyped**, like INI and `.env`: a numeric-looking cell is a number.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.'.env.production',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.'.env',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// A dotfile like `.env` has no extension to split on; its whole name isFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.expect(resolveFormat(undefined, '.env')).toBe('env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Unlike the rest of the family this never refuses: an unresolved formatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.{ label: '.env', value: 'env' },Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// A dotenv file is `.env` and everything after it. Splitting on the lastFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// dot asked `local` for a format and sent `.env.local` to the text scan,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// `.env.local` split on its last dot, asked `local` for a format andFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* `.env` and every suffix of it, and `<name>.env`. The leading dot is theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* `.env.production` and their siblings as dotenv, and a second resolver hereFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.'.env.local',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.await read('nope\n{"jsonrpc":"2.0","id":1,"method":"ping"}\n'),Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.* extension's commands read through as well. The crate reads `.env.local`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert_eq!(exit_code(&reports, false), 0, "the .env file has a number");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.'.env.local',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.'.env.test.local',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.//! number. That is the same rule as `.env` and CSV, and the opposite ofFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.