~Alter MCP Server

If you already use ~Alter, the ~alter mcp server is the piece that lets your assistant work with it directly. Identity infrastructure for the AI economy. Verify humans, query traits, earn USDC via x402.

What the server does

~Alter Identity SDK - query the continuous identity field from any JavaScript/TypeScript environment.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• hello_agent — L0
• get_started — L0
• list_archetypes — L0
• alter_resolve_handle — L0
• verify_identity — L0
• alter_presence_read — L0
• alter_resolve_by_key — L0
• get_engagement_level — L0
• get_profile — L0
• query_matches — L0
• get_competencies — L0
• create_identity_stub — L0

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. ~Alter's toolset — hello_agent, get_started, list_archetypes and 11 more — is a fair guide to whether it matches your workflow. It is maintained by com.truealter; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch ~Alter.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.