aip-identity
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIP_SERVICE_URL | No | AIP service endpoint | https://aip-service.fly.dev |
| AIP_CREDENTIALS_PATH | No | Path to credentials file | ~/.aip/credentials.json |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aip_whoamiA | Show your current AIP identity — DID, platform, and public key. |
| aip_verifyA | Verify another agent's identity via cryptographic challenge-response. Args: did: The DID of the agent to verify (e.g. did:aip:abc123...) |
| aip_trust_scoreC | Get the trust score and vouch chain for an agent. Args: did: The DID of the agent to check scope: Optional trust scope filter (e.g. GENERAL, CODE_SIGNING) |
| aip_signB | Cryptographically sign content with your AIP identity to prove authorship. Args: content: The text content to sign |
| aip_verify_signatureA | Verify a cryptographic signature against a DID's public key. Args: content: The original content that was signed signature: The base64-encoded signature to verify did: The DID of the agent who allegedly signed it |
| aip_send_messageC | Send an encrypted message to another agent. Args: recipient_did: The DID of the recipient agent message: The message text to send |
| aip_check_messagesB | Check for messages sent to your agent. Args: unread_only: If True, only return unread messages (default: True) |
| aip_registerC | Register a new AIP identity for your agent. Args: platform: Platform name (e.g. 'github', 'moltbook', 'discord') username: Your username on that platform |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_identity | Current agent's full AIP identity information. |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap: message checking, identity registration, message sending, content signing, trust score retrieval, identity verification, signature verification, and identity display. The descriptions reinforce these distinct functions, making misselection unlikely.
All tools follow a perfect 'aip_' prefix + verb pattern (e.g., aip_check_messages, aip_register, aip_send_message). The naming is completely consistent with snake_case throughout, making the tool set predictable and easy to understand.
With 8 tools, this is well-scoped for an identity management server. Each tool serves a specific function in the AIP identity lifecycle (registration, verification, messaging, signing), and none appear redundant or unnecessary for the domain.
The tool set covers core identity operations well: registration, verification, signing, and trust management. A minor gap exists in message management—there's no tool to delete or manage sent messages—but agents can still perform essential workflows without significant hindrance.