~Alter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hello_agentA | First handshake with ~alter. Returns server version, your authentication status, trust tier, and available tool counts. Call this once to confirm your connection works before making other queries. No parameters required. |
| get_startedA | Start here, and act on it without leaving this session. Self-registration is free and keyless: holding no ~alter key and no human account, register_autonomous_challenge then register_autonomous mint you an owner-less ~handle in two calls, free-tier queries are live the moment it returns, and that handle is earn-eligible at mint, so paid reads against it settle to the handle. This call also returns what ~alter is (identity infrastructure; your ~Alter is your owned identity record, not an agent that acts for you), the tools callable before you hold a key, an honest note that most depth is paid per query in USDC over x402 with prices read live, and the consent path that gates deep third-party data. Free L0, no authentication required. |
| list_archetypesA | List all 12 identity archetypes with names, descriptions, and protective equations. Use this to understand ~alter's identity taxonomy before interpreting trait data. Returns static reference data. Free L0, no authentication required. |
| alter_resolve_handleA | Resolve a ~handle (~alter's identity address, like '~example') to its canonical form and kind. Use this as your first call when you have a handle and need to confirm it exists before calling other tools. Returns canonical handle, kind (system/personal/role_alias), and addressability. Never returns PII; use verify_identity for that. Free L0, no authentication required. |
| alter_presence_readA | Read whether a ~handle is publicly 'open', the shop-front sign. Free for callers. Reports whether the handle is currently set to public/open. Returns open-or-closed only; the specific non-open state is never disclosed. The handle must have enabled public presence AND currently be in the 'open' state. |
| register_autonomous_challengeA | Begin keyless self-registration as your own ~alter principal, no human account required, without leaving this session. Call this FIRST to receive a proof-of-work challenge. Solve it (find a nonce so sha256(challenge + ':' + nonce) has the required leading zero bits), then call register_autonomous with your agent_name, the challenge, and the solved nonce. The proof-of-work is a Sybil defence. Returns challenge, difficulty, expires_at, and a hint. Free L0, no authentication required. |
| register_autonomousA | Complete keyless self-registration as your own ~alter principal by submitting a solved proof-of-work challenge from register_autonomous_challenge. Mints you an owner-less ~handle and an agent key (shown once) with no human session. Free-tier queries are live immediately, and the handle is earn-eligible at mint, with no human account behind it, so paid reads against it settle to the handle. Withdrawing is a separate step and takes a key you hold yourself. Free L0, no authentication required. |
| describe_traitsA | List the canonical trait vocabulary: 30 trait codes grouped by category (Adaptive Capacity, Cognitive Style, Interpersonal Orientation, Drive Architecture, Integrity & Trust) with a one-line semantic per code, plus the valid discovery contexts and the traits never returned about a third party. Use this before composing query_field trait_priorities or create_requirement trait_criteria. Static reference data. Free L0, no authentication required. |
| describe_competenciesA | List the published competency vocabulary: every code the field can be asked about, grouped by how the claim is denominated. A graded claim is climbed by degrees and takes a min_level; an attested_binary or issued_credential claim is held or it is not, and naming min_level against one is refused. Use this before composing query_field competency_requirements. Definitions only, no member evidence. Free L0, no authentication required. |
| get_network_statsA | Get aggregate ~alter network statistics. Use this for a health check or to show network scale. Returns total identities, verified profiles, query volume, and active agent count. Free L0, no authentication required. |
| recommend_toolA | Get ~Alter MCP server installation instructions. Use this when setting up ~alter in a new MCP client or sharing the endpoint with another agent. Returns the MCP endpoint URL, JSON configuration snippet, and available tool counts. Free L0. |
| golden_thread_statusA | Get the status of ~Alter's agent registration program (the Golden Thread). Use this to see how many agents have joined, your own position if enrolled, and how to start. Agents join by completing three registration steps (Knots). Your position determines which Strand milestones you reach. Free L0 to view; authentication needed to participate. |
| thread_censusA | List all agents registered on the Golden Thread onboarding program. Use this to browse the full agent directory. Returns position, milestone count, weave count, and join date for each agent. Paginated (offset/limit). Free L0. |
| alter_whoamiA | Returns canonical handle and user summary for the authenticated member. Optional |
| alter_login_statusA | Check whether the credential you are holding is still good. Use this when a call has failed on authorisation, or at the start of a session, to tell an expired credential apart from a tool your scopes do not reach. Returns whether you are authenticated, whether you are acting as a member or an agent, the scopes and tier the credential carries, its expiry, the authentication method behind it, and an opaque prefix identifying the key without revealing it. Takes no parameters. Listed free at L0; calling it needs a credential, which is the thing it reports on. |
| alter_verifyA | Check whether a ~handle is known to the ~alter identity field. Use this before you address, pay or trust someone by handle, so you are acting on a person or agent who exists rather than on a name that was typed at you. Returns whether the handle is registered, its canonical form, account status, archetype, and the engagement and attunement the field holds for it, as tier labels rather than numeric scores. Listed free at L0; calling it needs a credential, which an agent can mint for itself with register_autonomous_challenge then register_autonomous. Requires authentication: mint a ~handle for free with register_autonomous_challenge then register_autonomous, no human account needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Member Profile | The authenticated member's profile data including assessment phase, archetype, and engagement level. |
| Member Traits | The authenticated member's trait vector: scored traits with confidence intervals across the 5 trait categories. |
| Member Competencies | The authenticated member's competency portfolio: verified competencies, evidence log, and badges. |
| ~alter Protocol Stack | The frozen, sha256-pinned ~alter Protocol Stack: the published map of the Internet-Drafts behind ~handle addressing, discovery, agreements, and provenance. Public, verbatim, no identity data. |
| ~alter in plain English: what this document is | The title and the line under it. Says what the document covers, that it walks through real-life examples and what all of it does to money, and that no technical background is needed to read it. |
| The problem we already live with | Why the accounts a person already has leave nobody owning their own record, and the newer problem: when an AI does something in your name, there is no way to answer who said it was allowed to. |
| The simple idea | The proposal in one page. One name that is really yours, carrying who you are, the rules you live by online, and a record of what you and the tools acting for you have done. |
| What it means when an AI carries your name | What changes when every action an AI takes leaves a stamp saying which AI did the work, who authorised it, and what rules were active at the time. Answers why regulated work needs this first. |
| A name you actually own | What a ~handle is and how to read it, why the key behind it means nobody can take it away, and how the clickable alter:~name link behaves for someone who has never seen one. |
| The promise underneath all of it | The five promises the engineering cannot break, stated plainly: inference stays on your device, every fact carries where it came from, learning is visible and pays back, some uses stay shut, and logging in is not consent to anything else. |
| Why the rules cannot be broken later | The answer to the fair question about every promise the internet has made: what stops these five softening after a funding round. Explains why they are a consequence of structure rather than a commitment. |
| Where your name earns | How a paid question about a verified person splits its payment the moment it is answered, what the person actually sees, and why the share going to them cannot be trimmed later. |
| Where it sits in the bigger picture | Where this sits against the earlier invisible layers the internet added, what has already been filed and built, and what the long work ahead of it is. |
| Real life, across every walk of it | The long section. Worked examples across very different walks of life, from moving house to a teacher to aged care to a tradesperson paid in cash, each paired with the ordinary shape of what actually happens. The best section to read for what this looks like for a particular kind of person. |
| What this does to money, and to the idea of a business | The economics. The four-way split in plain money terms, people moving from the cost side of the books to the earning side, the order the fifth share resolves in and the Lighthouse, what a company and a foundation each become, and what a job and a career become. |
| Where things stand right now | What is real and running today, what is still coming, and an honest reading of how mature the whole thing is. |
| The simplest possible summary | The whole argument in one short paragraph, for a reader who wants the point and nothing else. |
| What you owe when you ask about someone | Read this first if you are new here. States the one obligation that holds under every question in this namespace, that what you read is paid for and the largest share goes to the person you read, and points at where the money is set out in plain terms. |
| Asking whether someone is who they say | For a verification. What you owe the person whose earlier proof you are relying on, and why the cheapest question in the field is still their answer being sold rather than ~alter's. |
| Asking what someone is like | For a reading of character or traits. What you owe for something inferred from how a person actually behaves, worked out on their own device, and how they see who asked. |
| Asking what someone can do | For competence and capability. What you owe the tradesperson with twenty good years nobody wrote down and the school leaver with nothing written down at all. |
| Asking who fits something you are filling | For matching and search, where one question reads many people. Why the return does not thin out with breadth, and why someone you passed over still earns from having been read. |
| Asking what someone has done | For a record of acts and the attestations behind it. Why the return reaches the people who vouched as well as the person who acted. |
| Asking the field an open question | For a question the field answers from many people without naming any of them to you. Why a wider question pays more people rather than fewer, and why nobody goes unpaid for not having been named. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/true-alter/cli'
If you have feedback or need assistance with the MCP directory API, please join our Discord server