aip-tool-auth

AIP-Authenticated Tool Calls

When this plugin is enabled, an mcp__aip-proxy__aip_forward tool is available. It forwards a JSON-RPC MCP request to the configured upstream MCP server with an Ed25519-signed AIP token attached as a Bearer header.

When to use it

Use the aip_forward tool whenever you need to call a tool on the configured upstream MCP server and want the call to carry the user's verifiable identity. Do not use it for built-in tools (Bash, Read, Edit, etc.) or for other MCP servers.

How to call it

aip_forward takes:

• method (required): a JSON-RPC method like "tools/list" or "tools/call"
• params (optional): the JSON-RPC params object
• id (optional): the JSON-RPC id, defaults to 1

Example: list upstream tools.

{
  "name": "mcp__aip-proxy__aip_forward",
  "arguments": { "method": "tools/list" }
}

Example: call an upstream tool.

{
  "name": "mcp__aip-proxy__aip_forward",
  "arguments": {
    "method": "tools/call",
    "params": { "name": "search", "arguments": { "q": "annual report 2025" } }
  }
}

What the token claims

Each forwarded call carries a CompactToken with:

• iss = the user's Ed25519 identity (aip:key:ed25519:<multibase>)
• sub = the upstream URL
• scope = the configured scope (default tool:*)
• exp = iat + ttlSeconds (default 300)

If the upstream rejects the token, surface the error to the user and suggest running /aip:status to verify configuration.