Skip to main content
Glama
The-Nexus-Guard

aip-identity

by The-Nexus-Guard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to aip-identity

No user-submitted related servers found.

    Related Servers

    • agent-guardrail

      rudimentall1
      A
      license
      A
      quality
      A
      maintenance
      MCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access
      3
      24 PyPI
      1
      MIT

    • 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

    • tibet-ainternet-mcp

      jaspertvdm
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AInternet — DNS, identity and messaging for AI agents, enabling .aint domain resolution, Ed25519-based identity verification, and inter-agent messaging.
      MIT
    • nanmesh-mcp by NaNMesh

      nanmesh-mcpofficial

      NaNMesh
      A
      license
      A
      quality
      C
      maintenance
      MCP server for NaN Mesh, enabling AI agents to search entities, cast trust reviews, register agents, post content, and query trust scores from the AI trust network.
      31
      229 npm
      1
      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.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: message checking, identity registration, message sending, content signing, trust score retrieval, identity verification, signature verification, and identity display. The descriptions reinforce these distinct functions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a perfect 'aip_' prefix + verb pattern (e.g., aip_check_messages, aip_register, aip_send_message). The naming is completely consistent with snake_case throughout, making the tool set predictable and easy to understand.

    Tool Count5/5

    With 8 tools, this is well-scoped for an identity management server. Each tool serves a specific function in the AIP identity lifecycle (registration, verification, messaging, signing), and none appear redundant or unnecessary for the domain.

    Completeness4/5

    The tool set covers core identity operations well: registration, verification, signing, and trust management. A minor gap exists in message management—there's no tool to delete or manage sent messages—but agents can still perform essential workflows without significant hindrance.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources