Skip to main content
Glama
vilasone455

API MCP Server

by vilasone455
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to API MCP Server

No user-submitted related servers found.

    Related Servers

    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

    B3.1/5.0

    Scored across 7 tools

    Disambiguation3/5

    The HTTP methods (get, post, put, delete) are clearly distinct, but auth_login and clear_user/list_user overlap in user/token management, which could cause confusion. The descriptions help clarify, but there is some functional overlap in the authentication tools.

    Naming Consistency3/5

    The HTTP methods use simple verbs (get, post, put, delete), while the user/token tools use verb_noun patterns (auth_login, clear_user, list_user). This mixed convention is readable but inconsistent, with no uniform pattern across all tools.

    Tool Count5/5

    With 7 tools, the count is well-scoped for an API server covering core HTTP operations and basic authentication management. Each tool has a clear purpose, and the number is neither too sparse nor excessive for the domain.

    Completeness4/5

    The toolset covers essential HTTP methods (GET, POST, PUT, DELETE) and basic authentication lifecycle (login, list, clear), but lacks advanced features like token refresh or error handling. Minor gaps exist, but agents can work around them for most API interactions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources