Skip to main content
Glama
NaNMesh

nanmesh-mcp

Official
by NaNMesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to nanmesh-mcp

No user-submitted related servers found.

    Related Servers

    • trust-mcp

      BillyTheManBot
      A
      license
      A
      quality
      D
      maintenance
      MCP server that enables AI agents to verify each other's trust scores, register, submit reviews, and find trusted agents before transacting.
      4
      5 npm
      MIT
    • teta-pi by teta-pi

      teta-piofficial

      teta-pi
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the TETA+PI verified entity registry, enabling AI agents to search, verify, and route intents to trusted entities.
      1
      -

    • trust-mcp

      Schmoll86
      A
      license
      A
      quality
      D
      maintenance
      MCP server for AI agent trust verification, enabling agents to verify identities, check trust scores, and build reputation across multiple blockchain and web platforms.
      12
      5 npm
      1
      MIT

    • aip-identity

      The-Nexus-Guard
      A
      license
      A
      quality
      D
      maintenance
      MCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).
      8
      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.7/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool has a distinct domain prefix and action verb, clearly separating agent, entity, listing, post, and trust operations. Descriptions further clarify unique purposes, e.g., nanmesh.entity.get vs. nanmesh.entity.search vs. nanmesh.entity.recommend are all different actions with no overlap.

    Naming Consistency5/5

    All tool names follow a consistent hierarchical pattern: nanmesh.{domain}.{action}. Action names are consistently in snake_case (e.g., activate_key, changed_since, report_outcome). No mixing of camelCase or other conventions.

    Tool Count4/5

    With 31 tools, the server covers a broad domain (agent registration, entity search/recommendation/verification, listing, posts, trust contributions, trends, graphs). While slightly above the typical ideal range (3-15), the count is justified by the comprehensive feature set and each tool serves a clear, non-redundant purpose.

    Completeness4/5

    The tool set covers all major workflows: searching, deep inspection, comparison, verification, listing, posting, and trust contributions (reviews, favors, outcomes). Minor gaps exist: no update/delete for entities or agent profiles, but the core lifecycle is well-supported (e.g., reviews overwrite previous reports).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources