mcp server
Strings-LE
Extract string values from config files, data files and plain text.
Description as published by the maintainer. Source
- version 2.2.2
- active
- data extraction
active — Registry entry last updated 2026-08-05. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 2.2.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-05 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-05 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol |
Where to get it
Also from nolindnaidoo
-
Colors-LE
Extract colors from stylesheets and code, with their notation and position.
-
Dates-LE
Extract dates and timestamps from logs, data files and code, with their format and position.
-
EnvSync-LE
Compare dotenv files and report which keys are missing or extra, by name only.
-
Numbers-LE
Extract numeric values from config files, data files and plain text.
-
Paths-LE
Extract file and directory paths from config files and code, with their kind and position.
-
Regex-LE
Extract regular expressions from code, each with a ReDoS safety verdict.
-
Scrape-LE
Analyse robots.txt content and report whether a path may be crawled.
-
Secrets-LE
Detect hardcoded secrets in source and config. Reports masked previews, never the values.
-
URLs-LE
Extract URLs from documentation, configuration and code, with their protocol and position.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab