get_benchmark — aibvf mcp MCP Tool Read-only
get_benchmark
(get benchmark) is one of 13 tools on the
aibvf mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_benchmark from your client
- Claude Code aibvf mcp get_benchmark run in your project directory
- Claude Desktop aibvf mcp get_benchmark ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor aibvf mcp get_benchmark ~/.cursor/mcp.json
- VS Code aibvf mcp get_benchmark .vscode/mcp.json
- Zed aibvf mcp get_benchmark ~/.config/zed/settings.json
- Windsurf aibvf mcp get_benchmark ~/.codeium/windsurf/mcp_config.json
- Cline aibvf mcp get_benchmark ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI aibvf mcp get_benchmark ~/.gemini/settings.json
- Grok aibvf mcp get_benchmark .mcp.json (in your project root)
- ChatGPT aibvf mcp get_benchmark Settings → Connectors → Advanced → Developer mode
- Claude.ai aibvf mcp get_benchmark Settings → Connectors → Add custom connector
- LangChain aibvf mcp get_benchmark pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aibvf-mcp https://mcp.aibvf.com/api/mcpOther tools on this server
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.