audit_agent_readiness — invinoveritas MCP Tool
audit_agent_readiness
(audit agent readiness) is one of 31 tools on the
invinoveritas
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call audit_agent_readiness from your client
- Claude Code invinoveritas audit_agent_readiness run in your project directory
- Claude Desktop invinoveritas audit_agent_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor invinoveritas audit_agent_readiness ~/.cursor/mcp.json
- VS Code invinoveritas audit_agent_readiness .vscode/mcp.json
- Zed invinoveritas audit_agent_readiness ~/.config/zed/settings.json
- Windsurf invinoveritas audit_agent_readiness ~/.codeium/windsurf/mcp_config.json
- Cline invinoveritas audit_agent_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI invinoveritas audit_agent_readiness ~/.gemini/settings.json
- Grok invinoveritas audit_agent_readiness .mcp.json (in your project root)
- ChatGPT invinoveritas audit_agent_readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai invinoveritas audit_agent_readiness Settings → Connectors → Add custom connector
- LangChain invinoveritas audit_agent_readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http invinoveritas https://api.babyblueviper.com/mcpOther tools on this server
- reason
- decision
- review
- signals
- markets_act
- agent_economy_brief
- seller_intel
- memory_store
- memory_get
- memory_list
- memory_search
- memory_delete
- workspace_list
- workspace_delete
- workspace_status
- marketplace_buy
- message_post
- browse
- execute
- prove
- witness
- validate
- residence_me
- feedback_submit
- feedback_list
- feedback_vote
- ledger
- ledger_submit
- conformance_certify
- verify_proof
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.