Skip to main content
Glama
opennod

nod-mcp-server

by opennod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to nod-mcp-server

No user-submitted related servers found.

    Related Servers

    • nod-mcp-server by nod-protocol

      nod-mcp-serverofficial

      nod-protocol
      A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to discover and interact with businesses by reading structured NOD manifests. Provides tools to look up business capabilities and check if specific actions like ordering food or booking appointments are supported.
      2
      MIT
    • GateCore by GateCoreAI-com

      GateCoreofficial

      GateCoreAI-com
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to discover governed capabilities, inspect machine-readable contracts, and request policy-checked procurements with signed receipts and audit trails.
      Apache 2.0

    • ClawDaddy MCP Server

      gregm711
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to check domain availability, purchase domains via Stripe, and perform full DNS and nameserver management. It facilitates automated domain lifecycle tasks like record updates and transfer locks without requiring CAPTCHAs.
      1
      MIT

    • com.nessgate/nessgate

      NessGate
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a discover_domain tool that reads whatever a given domain already publishes across ARD, A2A, llms.txt, api-catalog, OpenAPI and other standards, returning one normalized resource list with a link back to each source. It lets agents resolve a domain's machine-readable capabilities in a single call instead of querying each standard separately.
      2
      Apache 2.0
    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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    Both tools deal with NOD manifests but have distinct purposes: lookup_nod retrieves the full manifest and check_capability queries a specific action. No overlap.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern with underscore_case: check_capability and lookup_nod.

    Tool Count4/5

    Two tools is appropriate for a focused purpose. While minimal, they cover the core operations for querying NOD manifests without unnecessary complexity.

    Completeness4/5

    The tools cover the main operations: retrieving the manifest and checking a specific capability. Missing tools for writing or updating manifests, but that seems out of scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources