agent-toolbelt
Related Servers
Alternatives to agent-toolbelt
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceSwiss-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-

@mate-tools/mcp-serverofficial
AlicenseAqualityDmaintenanceMCP server providing 35 utility tools for AI agents including text analysis, encoding, hashing, password generation, JSON/CSV/XML parsing, regex, color, date, finance, URL metadata, SEO tags, DNS lookup, SSL inspection, and JWT decoding. Free, zero-dependency, and works with any MCP client.3558 npmMIT- AlicenseBqualityDmaintenanceProduction-ready MCP server with 40+ tools — QR codes, PDFs, text processing, TTS, web scraping, image generation and more. Built for AI agents.2528 npmMIT
- AlicenseNot gradedqualityCmaintenanceMonetizable AI agent tools - document parsing, text analysis, code generation, security scanning, format conversion, and more. 8 tools with HTTP API and MCP protocol support.MIT
- AlicenseNot gradedqualityDmaintenanceMulti-tool MCP server for AI agents with 29 tools across web scraping, SEO analysis, screenshot and PDF generation, domain intelligence, content extraction, multi-chain EVM blockchain queries, and security toolkit. Free tier available with no auth required.12 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform common utility tasks through a streamable HTTP MCP endpoint, including JSON inspection, regex testing, cron parsing, hashing, base64 encoding/decoding, URL analysis, color conversion, text diffing, CSV parsing, JWT decode/verification, Markdown-to-HTML rendering, and UUID/token generation without API keys.MIT
TDQS
Scored across 25 tools
Tools are mostly distinct despite the large set. The five financial analysis tools (bear_vs_bull, earnings_analysis, insider_signal, stock_thesis, valuation_snapshot) target different aspects of stock research, though an agent might briefly confuse stock_thesis with bear_vs_bull. Text extraction tools are well-differentiated by scope (general entities vs. contracts vs. meetings).
Approximately 80% of tools follow a consistent verb_noun pattern (e.g., extract_contract_clauses, generate_schema, normalize_address). However, the financial analysis cluster breaks convention with noun_noun naming (earnings_analysis, insider_signal, stock_thesis, valuation_snapshot) or noun_vs_noun (bear_vs_bull), creating a mixed convention that reduces predictability.
With 25 tools, this sits at the upper bound of 'borderline heavy' per the rubric. While each tool serves a distinct utility purpose (text extraction, stock analysis, data conversion), the breadth covers many unrelated domains (finance, cron syntax, image metadata, address normalization), making it a 'kitchen sink' collection that risks selection paralysis without being completely unmanageable.
For a general agent utility belt, the surface covers the targeted domains reasonably well. The financial cluster provides fundamental analysis capabilities (thesis, valuation, earnings, insider activity, bull/bear cases). Text extraction covers general entities, contracts, and meetings. Missing minor operations like json_to_csv or additional image processing don't create critical dead ends given the toolset's utility-focused nature.