Skip to main content
Glama
OtavioBarbosa

erickwendel-contributions-mcp

Related Servers

Alternatives to erickwendel-contributions-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables natural language exploration of OpenAPI/Swagger specs, allowing users to register APIs, browse endpoints, describe schemas, and detect breaking changes through conversational queries.
      9
      682 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables searching and retrieving portfolio data including experience, skills, and contact information through natural language queries.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying a stateless, read-only MCP endpoint for profile information, projects, CV details, and grounded answers based on published site content.
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients and LLM-based agents to interact with FHIR-compliant healthcare backends via natural-language prompts, supporting full CRUD operations on FHIR resources, document ingestion, semantic search, and LOINC terminology lookup.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients to perform CRUD operations on healthcare resources, process clinical documents, run semantic search, and query LOINC terminology through natural-language prompts.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Converts natural language queries into valid GraphQL queries and executes them against GraphQL APIs. Includes schema introspection, query validation, execution with authentication, and query history tracking.
      5
      26
      -

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each content tool targets a clearly distinct resource type: talks, posts, or videos. check_status is clearly separated as a health check and cannot be confused with content retrieval.

    Naming Consistency4/5

    All names use snake_case and are readable. Three tools follow a get_<resource> pattern, while check_status uses a different verb, which is a minor but understandable deviation.

    Tool Count5/5

    Four tools is a tight, well-scoped surface for a small contributions server. Each tool has a clear role: listing one of three content types or checking API health.

    Completeness4/5

    The server covers its apparent core domain of listing talks, posts, and videos, plus a health check. A detail-retrieval tool for individual items is missing, but filtering and pagination reduce the impact of that gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues