Skip to main content
Glama
mcp-v2-minimal

mcp-v2-minimal

by Code-0-0

Related Servers

Alternatives to mcp-v2-minimal

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables a model to call one echo tool over stdio, sending text and receiving it back through the Model Context Protocol.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Minimal typed scaffold for a local Model Context Protocol stdio server, providing echo and server_status tools.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves a single set of typed, validated tool definitions to MCP clients over stdio, letting them perform real actions through one controlled executor. The same definitions power a speech-driven OpenAI tool-calling agent, so voice and MCP clients share identical, validated capabilities.
      1
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A learning-oriented MCP server that exposes basic tools (echo, add, reverse) over stdio transport to validate MCP handshake and tool calls.
      3
      -
    • A
      license
      D
      quality
      D
      maintenance
      A minimal Model Context Protocol server in TypeScript that demonstrates MCP-compliant resources and tools for LLMs, featuring simple resources and a basic tool that echoes messages or returns greetings.
      1
      5
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely non-overlapping purposes: one is a connectivity check that echoes input, the other parses and reformats JSON. An agent could not reasonably confuse them.

    Naming Consistency3/5

    Both names are lowercase snake_case, which is consistent, but the patterns differ: 'echo' is a bare verb while 'json_format' is a noun_verb compound. With only two tools there is no discernible shared convention to rely on.

    Tool Count3/5

    Two tools is borderline thin — the server presents itself as a 'minimal' utility host, so a small surface is intentional, but there is very little substance beyond a ping and one formatter.

    Completeness3/5

    The surface covers its two narrow utilities but leaves obvious adjacent gaps: no JSON validation/minification/query, and no other basic text or connectivity operations. Each tool is a dead end on its own rather than part of a coherent utility set.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues