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.

Strings-LE

NPM · STRING-LE-MCP · SCANNED AUG 15

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

Available components

npm · string-le-mcp 76
+5 this week 76 Trust /100
Trust breakdown (6 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 →

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 & Transparency45
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 178 tokens (~178/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · string-le-mcp

# add to Claude Code
claude mcp add nolindnaidoo-string-le -- npx -y string-le-mcp
# add to Codex CLI
codex mcp add nolindnaidoo-string-le -- npx -y string-le-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nolindnaidoo-string-le": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "string-le-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nolindnaidoo-string-le --command npx --arg -y --arg string-le-mcp
# ~/.hermes/config.yaml
mcp_servers:
  nolindnaidoo-string-le:
    command: "npx"
    args: ["-y", "string-le-mcp"]
// mcp.json
{
  "mcpServers": {
    "nolindnaidoo-string-le": {
      "command": "npx",
      "args": [
        "-y",
        "string-le-mcp"
      ]
    }
  }
}
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.

  • 15 Aug 26 +1

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

  • 14 Aug 26 0
    • Stability: 0.23 → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Package version: 2.2.4 → 2.3.0 functional
  • 13 Aug 26 +1

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

  • 11 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Aug 26 +1

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

  • 8 Aug 26 +32
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.07 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 7 Aug 26 −31
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 2.2.2 → 2.2.4 functional
  • 6 Aug 26 +31
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 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 15 Aug 2026 · Analysed npm/string-le-mcp@2.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 0 packages
Packages resolved 0
Tree resolution Complete
MCP tools · 1 exposed · ~178 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.

Tool Tokens
extract_strings ~178

Extract every string value from a document. Parses JSON, YAML, CSV, TOML, INI and dotenv; for any other format it falls back to quoted strings — single, double or backtick — so a format is optional but unquoted prose yields nothing. Returns the values themselves, in document order, not their positions.

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 falls back to extracting quoted strings.
maxResultsinteger–Cap on returned strings (default 500). meta.truncated reports whether any were dropped.

No output schema declared.

No examples provided.