Skip to main content
Glama
Apitomy

Apitomy Data Models MCP

Official
by Apitomy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Apitomy Data Models MCP

No user-submitted related servers found.

    Related Servers

    • OpenAPI Schema Explorer

      kadykov
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server providing token-efficient access to OpenAPI/Swagger specs via MCP Resources for client-side exploration.
      169 npm
      76
      MIT

    • mcp-openapi-schema

      hannesj
      A
      license
      Not graded
      quality
      F
      maintenance
      A MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context
      101 npm
      49
      MIT

    • JSON-RPC

      xiaobenyang-com
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server based on OpenRPC, providing JSON-RPC function invocation and method discovery services.
      2
      1
      Apache 2.0

    • MCP REST API Server

      vinaykp
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
      -

    • mcp-lint-server

      ZachDreamZ
      A
      license
      Not graded
      quality
      C
      maintenance
      Model Context Protocol (MCP) server wrapping mcp-lint to perform static analysis and schema checking on other MCP servers.
      MIT
    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/5.0

    Scored across 102 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but the enormous number combined with overlapping verbs (add/set/update/remove/delete) creates real ambiguity. Generic tools like document_set_node and document_get_node blur boundaries with their specific counterparts, and delete/remove pairs like document_delete_license vs document_remove_tag are easy to conflate.

    Naming Consistency3/5

    All tools share a consistent document_ prefix and snake_case format, which helps navigation. However, verb usage is inconsistent: delete vs remove, set vs update, and add vs create are used interchangeably for similar mutation operations, making the pattern less predictable than it could be.

    Tool Count1/5

    With 102 tools, the server far exceeds the 'too many' threshold and imposes a heavy selection burden on agents. Even for a comprehensive OpenAPI/AsyncAPI editor, this surface should be consolidated into fewer, more parameterized operations.

    Completeness4/5

    The OpenAPI side is exceptionally complete, covering paths, operations, schemas, responses, parameters, security, extensions, and lifecycle operations. However, AsyncAPI support has notable gaps such as no remove_channel or update_channel tool, and individual security requirement removal is missing.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources