~Alter
Related Servers
Alternatives to ~Alter
- AlicenseNot gradedqualityAmaintenanceTypeScript SDK for ALTER - identity infrastructure for the AI economy. alter-mcp-bridge exposes mcp.truealter.com as a stdio MCP: identity verification, ~handle resolution, 33-trait vectors, belonging probability, x402 micropayments30 npmApache 2.0
Related Servers
- MIT
- AlicenseNot gradedqualityBmaintenanceIdentity infrastructure for AI agents. Gives agents an evolving persona, session continuity, and self-correcting retrieval so they stop being strangers. Local-first, model-agnostic.27 PyPI8AGPL 3.0

5arz Proof-of-Humanofficial
AlicenseNot gradedqualityCmaintenanceEnables agents to prove and verify that a real, unique human performed an action, issuing machine-readable signed credentials with public verification.1Apache 2.0- FlicenseNot gradedqualityDmaintenanceEnables verifiable AI agent identity and reputation management on ICP via MCP, allowing agents to register, create handshake proofs, and verify credentials.-
- FlicenseNot gradedqualityDmaintenanceIssues accountable identities for AI agents before they interact with tools, with tools for identity management and receipt export.-
- AlicenseNot gradedqualityDmaintenanceDecentralized KYC identity protocol for AI agents. Proves there's a verified human behind any bot using Zero-Knowledge Proofs. No servers, no PII stored.7 npm5MIT
TDQS
Scored across 16 tools
Most tools have distinct purposes, especially the paired registration and vocabulary tools. However, there is some boundary overlap among identity-oriented tools (alter_resolve_handle, alter_verify, alter_presence_read, alter_whoami) and among onboarding helpers (hello_agent, get_started, recommend_tool), though descriptions do enough to separate them.
All names are snake_case, but conventions are mixed: some use verb_noun (get_network_stats, describe_traits), some use an alter_ prefix (alter_resolve_handle, alter_whoami), and a few are noun-only (golden_thread_status, thread_census). The verbs also vary (get, list, describe, recommend, register, hello), making the set feel inconsistent even though each name is readable.
At 16 tools the set is slightly above the ideal 3-15 range, but the count is still justifiable for the breadth of identity infrastructure, onboarding, and reference data. The extra tools mostly pull their weight, so the count feels only modestly heavy rather than bloated.
The surface has significant gaps: tools like describe_traits and describe_competencies explicitly reference composing query_field and create_requirement operations, but those tools are not included, leaving obvious dead ends. There is also no way to update presence, manage keys, or perform the paid data operations that the server's own descriptions imply should exist.