Skip to main content
Glama

Related Servers

Alternatives to multi-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a wide range of tools including math, image processing, filesystem, git, text utilities, network, date/time, security, and browser console capture. Designed as a clean, modular foundation for building MCP servers with comprehensive error handling and testing.
      406 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Open-source web scraper and extraction MCP server with JavaScript rendering, markdown output, PDF/DOCX parsing, structured errors, and validated extraction contract diagnostics for agents.
      2
      AGPL 3.0
    • F
      license
      A
      quality
      B
      maintenance
      Swiss-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 required
      18
      5
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 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
    • A
      license
      A
      quality
      C
      maintenance
      Provides 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.
      20
      40 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation3/5

    The utility tools are clearly distinct, but scrape, scrape-dom, and dom overlap in fetching URLs and working with HTML/DOMs, so an agent could select the wrong one. Descriptions clarify raw HTML vs structured extraction vs in-memory DOM operations, but the boundaries are not immediately obvious from names alone.

    Naming Consistency3/5

    All names are lowercase, but the set mixes single-word nouns (timestamp, math, uuid), single-word verbs (echo, scrape), and hyphenated verb-noun names (list-tools, scrape-dom). The naming is readable and predictable in tone, but not structurally consistent.

    Tool Count4/5

    Ten tools is within a reasonable scope for a multi-purpose server, and each tool has a defined function. The utility side adds some trivial tools, but the overall count is not excessive or too thin.

    Completeness4/5

    The utility side covers common helper operations, and the scraping side provides raw fetch, structured extraction, and DOM manipulation with pagination support. There are minor gaps like limited HTTP request customization, but no critical dead ends for the apparent purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues