Skip to main content
Glama
ed-smartass

mcp-peek

by ed-smartass
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-peek

No user-submitted related servers found.

    Related Servers

    • mcp-slim

      Coefficient-work
      A
      license
      Not graded
      quality
      B
      maintenance
      Optimizes MCP tool menus from OpenAPI specs by grouping operations by tag and trimming schemas to reduce token usage, improving agent tool-selection accuracy.
      15 npm
      MIT

    • MCP Nexus

      Aidan-Kay
      A
      license
      Not graded
      quality
      B
      maintenance
      A single MCP endpoint for AI agents to browse, inspect, and call tools from multiple upstream MCP servers without loading all schemas upfront, reducing context overhead.
      11 npm
      ISC

    • Code Execution MCP

      marc-shade
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables efficient AI agent operations through sandboxed Python code execution with progressive tool discovery, PII tokenization, and skills persistence, achieving up to 98.7% token reduction by processing data in a sandbox rather than in context.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: http_request makes a request and returns schema, http_read reads cached body with jq masking, http_inspect re-renders cached schema in different formats, and server_info provides debug metadata. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent lowercase_underscore pattern (http_inspect, http_read, http_request, server_info), making them predictable and easy to distinguish.

    Tool Count5/5

    Four tools is well-scoped for a server focused on HTTP inspection and caching. Each tool earns its place, covering the core workflow without unnecessary bloat or gaps.

    Completeness5/5

    The tool set covers the full intended workflow: make a request, inspect schema, read cached body with jq filtering, re-render in alternative formats, and debug server state. Minor cache management features are absent but not essential for the server's stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources