ALTER Identity
Server Details
Psychometric identity verification for humans, queryable by AI agents over MCP. x402 micropayments.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 37 of 38 tools scored. Lowest: 3.3/5.
The tools cover distinct domains like messaging, identity assessment, and golden thread participation, but there is significant overlap within domains. For example, multiple tools retrieve trait data (get_trait_snapshot, get_full_trait_vector, assess_traits) and match information (query_matches, get_match_recommendations), which could confuse agents about which to use for specific tasks. Descriptions help clarify, but the sheer number of similar tools increases ambiguity.
Most tools follow a consistent verb_noun pattern (e.g., alter_message_send, get_agent_portfolio, check_assessment_status), with clear actions like 'alter', 'get', 'check', 'initiate'. There are minor deviations such as 'assess_traits' (verb_noun but not prefixed) and 'golden_thread_status' (noun_noun), but overall the naming is predictable and readable across the set.
With 38 tools, the count is excessive for a single server, making it heavy and potentially overwhelming for agents. While the server covers broad identity-related functions, many tools could be consolidated (e.g., multiple trait retrieval tools) or split into separate servers for better scoping. This large number risks inefficiency and confusion in tool selection.
The tool set provides comprehensive coverage for identity management, messaging, assessment, and network interaction. It includes CRUD-like operations (e.g., messaging with grant/send/revoke), data retrieval (profiles, traits, matches), and program participation (golden thread). There are no obvious gaps; agents can perform full workflows from identity verification to analysis and engagement without dead ends.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!