Gemini CLI Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory assay_get_ledger_policy
How to: Gemini CLI Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory assay_get_ledger_policy
Add Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"assay": {
"httpUrl": "https://assay.agentdiet.dev/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Ask for something assay_get_ledger_policy does. Gemini CLI lists the server's tools on connect and calls assay_get_ledger_policy itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory's identifier in your config matches the one above exactly.
Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 19 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.