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