Identity MCP server
{
"mcpServers": {
"truealter-identity": {
"type": "http",
"url": "https://mcp.truealter.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"truealter-identity": {
"type": "http",
"url": "https://mcp.truealter.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"truealter-identity": {
"type": "http",
"url": "https://mcp.truealter.com/api/v1/mcp"
}
}
}{
"servers": {
"truealter-identity": {
"type": "http",
"url": "https://mcp.truealter.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"truealter-identity": {
"type": "http",
"url": "https://mcp.truealter.com/api/v1/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.5.10
What it does
The ~alter SDK allows applications to verify user identities and read consented identity data from ~alter records. It's for developers building applications that need to know who their users are without storing personal data themselves.
- Check whether a ~alter handle exists for free to verify basic presence
- Read identity traits that a user has consented to share, with the read cost split 75/25 between user and application
- Settle paid identity reads in USDC directly from your application
Tools this server exposes
| Tool | Does |
|---|---|
| get_started | Returns information about current status and next steps in the ~alter flow |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.