String Utility Belt
Related Servers
Alternatives to String Utility Belt
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceSwiss-army-knife utility MCP server for AI agents. 18 tools for JSON validation/formatting, base64 encode/decode, hash generation, UUID generation, URL parsing, regex testing, markdown↔HTML conversion, text stats, slug generation, datetime conversion, cron parsing, text diffing, CSV↔JSON conversion, and JWT decoding. Zero API Key required185-
- AlicenseAqualityCmaintenanceProvides deterministic developer utilities as MCP tools, including UUID/password generation, hashing, encoding, JWT decoding, cron scheduling, regex execution, and text analysis. Runs entirely locally with no network calls, telemetry, or API keys.20336 npmMIT
- AlicenseNot gradedqualityCmaintenanceExposes 24 deterministic developer utilities as MCP tools — encoders and hashers, UUID/ULID and timestamp helpers, color, CSS, cron and permission converters, JSON/YAML/XML/SQL/TypeScript transformers, and a web page-to-markdown fetcher. Runs locally over stdio so agents get byte-exact results instead of approximating computations, with only the markdown fetcher making network requests.MIT
- AlicenseAqualityCmaintenanceFree, fully-offline MCP utility tools for agents: base64, UUID, JSON validation, SHA hashing, timestamps, URL codec, case conversion, and secure passwords. No API keys, no tracking, works offline - stdlib-only Python stdio server.9MIT
- AlicenseAqualityCmaintenanceEnables AI agents to perform exact, reproducible mechanical computation — text diffing, hashing, JSON querying, calendar arithmetic, deadline-bounded regex extraction, CSV parsing, similarity scoring, unit and base conversion — instead of relying on probabilistic guessing. Runs dependency-free, read-only and offline over stdio, with schema validation and hard caps on every operation so no call can hang the client.1544 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides deterministic, stateless tools for common data work including JSON, CSV, text, encoding, hashing, IDs, date/time, and number statistics.MIT
TDQS
Scored across 5 tools
Each tool maps to a distinct phase of the workflow: catalog discovery (list_utilities), documentation (describe_utility), single execution (run_utility), multi-step execution (run_pipeline), and identification (detect_format). The potentially confusable pair run_utility vs run_pipeline is explicitly delineated with guidance on when to use which.
All five tools follow a clean verb_noun snake_case pattern: list_utilities, describe_utility, run_utility, run_pipeline, detect_format. No mixed conventions or vague verbs.
Five tools is exactly right for a 248-utility meta-server: the catalog is accessed via discovery, docs, single-run, pipeline, and detection rather than one tool per utility. Each tool earns its place with no redundancy.
The surface covers the full lifecycle: find, learn, run, compose, and identify. Minor gaps exist around managing reusable macros or saving/inspecting prior results independently, but core workflows are fully supported.