VS Code Imperium Pre-Flight Readiness Auditor — A2A, MCP & x402 Validator audit_x402_and_a2a_endpoint
How to: VS Code Imperium Pre-Flight Readiness Auditor — A2A, MCP & x402 Validator audit_x402_and_a2a_endpoint
Add Imperium Pre-Flight Readiness Auditor — A2A, MCP & x402 Validator to VS Code
-
01
Open .vscode/mcp.json and merge this in. Keep any servers already there.
{
"servers": {
"preflight": {
"type": "http",
"url": "https://preflight.agentdiet.dev/mcp"
}
}
}-
02
Save the file and restart VS Code.
-
03
Ask for something audit_x402_and_a2a_endpoint does. VS Code lists the server's tools on connect and calls audit_x402_and_a2a_endpoint itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Imperium Pre-Flight Readiness Auditor — A2A, MCP & x402 Validator's identifier in your config matches the one above exactly.
Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 21 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.