Skip to main content
Glama
Watanabebashi

BeefChicken MCP

Related Servers

Alternatives to BeefChicken MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.
      8 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server that exposes API endpoints as tools for AI assistants by proxying requests to a target API defined in an OpenAPI specification. It supports various authentication methods and utilizes Server-Sent Events (SSE) to facilitate integration with clients like Claude and ChatGPT.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      This tool creates a Model Context Protocol (MCP) server that acts as a proxy for any API that has an OpenAPI v3.1 specification. This allows you to use Claude Desktop to easily interact with both local and remote server APIs.
      335 npm
      904
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Point it at an OpenAPI 3.x document and get an MCP server that exposes the API's endpoints as typed, validated tools for Claude or any MCP client.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted, OAuth-fronted MCP proxy that lets Claude custom connectors reach RapidAPI's MCP endpoints by injecting API credentials, with per-upstream tool filtering and rate limiting.
      AGPL 3.0

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a distinct operation: list, create, get by ID, and delete by ID. There is no meaningful overlap, and the names make the resource and action clear.

    Naming Consistency5/5

    All tool names follow the same resource_verb pattern, with tasks_id_get and tasks_id_delete clearly indicating the ID path parameter. The consistent snake_case and operation-based suffixes make the set predictable.

    Tool Count5/5

    Four tools is an appropriate, focused count for a simple task management server. Each tool covers a core operation without unnecessary bloat.

    Completeness4/5

    The server covers list, create, read, and delete operations for tasks, but notably lacks an update operation. This is a minor gap since delete-and-recreate is a possible workaround, but update is a standard task lifecycle need.

    Maintenance

    ActivityNo data
    ResponsivenessUnresponsive