Skip to main content
Glama
ruffymk3

Notory MCP server

by ruffymk3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Notory MCP server

No user-submitted related servers found.

    Related Servers

    • NetMap MCP Server by netmap-app

      NetMap MCP Serverofficial

      netmap-app
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI assistant such as Claude to read and edit the self-hosted network inventory: search and manage entries, check live TCP reachability, map hosts, link and derive relationships, inspect topology, compare configured read-only sources like Docker, OPNsense, AdGuard and Traefik against what is declared, surface conflicts and new devices, and review the audit log.
      MIT

    • Netdisco MCP

      omichelbraga
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with the Netdisco network management platform through its complete REST API, supporting device inspection, port queries, VLAN searches, and job management.
      MIT

    • mcp-openapi

      avidianity
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover, search, and call any REST API described by an OpenAPI or Swagger document. Supports multiple API endpoints with authentication and parameter handling.
      10 npm
      MIT

    • mcp-swagger

      awssam
      A
      license
      A
      quality
      D
      maintenance
      Exposes Swagger/OpenAPI API documentation to AI models, enabling exploration, search, and interaction with endpoints, schemas, and execution of API calls.
      14
      4 npm
      2
      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

    A3.8/5.0

    Scored across 5 tools

    Disambiguation2/5

    The generic tools notory_get and notory_request overlap for GET operations, and the specific asset tools (notory_list_assets, notory_get_asset) are thin wrappers over the same endpoints, creating functional redundancy. An agent could easily select the wrong tool for simple read tasks.

    Naming Consistency4/5

    All tools use the notory_ prefix with underscore-separated snake_case, and specific tools follow a verb_noun pattern (list_endpoints, list_assets, get_asset). The generic notory_get and notory_request deviate slightly from the noun-bearing structure but maintain a consistent style, making the naming mostly predictable.

    Tool Count5/5

    Five tools is an appropriate number for an API wrapper server, providing both generic access methods and convenient specific wrappers without excessive bloat or thinness.

    Completeness5/5

    The generic notory_request tool supports any HTTP method, enabling full CRUD operations on any endpoint, while notory_list_endpoints facilitates API discovery. The specific asset tools are redundant but do not create gaps in the surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources