idm-mcp
Related Servers
Alternatives to idm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server for XRP Ledger identity features including DIDs, credentials, multisig, and safe transaction workflows.1234 npm1MIT
- AlicenseAqualityDmaintenanceMCP server for jis: bilateral intent identity verification. Enables users to verify identities, request mutual consent, and send verified messages within the Intent-Centric Web ecosystem.7MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT
- AlicenseAqualityDmaintenanceMCP 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).8MIT
- AlicenseAqualityCmaintenanceLocal MCP server for Bind Protocol — credential parsing, verification, and hashing tools for AI agents.36 npmMIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server that maintains and serves personal identity context to LLMs.-
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: echo/ping for testing, get_did/resolve_did for DIDs, get_vc/list_credentials/resolve_vc/verify_vc for VCs. Overlap between list_credentials and resolve_vc is resolved by parameter differences.
Tool names follow a consistent verb_noun pattern (get_did, get_vc, list_credentials, resolve_did, resolve_vc, verify_vc) with lowercase snake_case. echo and ping are conventional single-word utilities.
Eight tools cover both DID and Verifiable Credential management appropriately without being excessive or insufficient for a focused identity server.
Core workflows (create/resolve DID, issue/list/resolve/verify VC) are covered. Minor gaps like DID update/deactivation or issuer management are absent but acceptable for a basic identity server.