Cursor Hive Intelligence MCP validate_task_result
How to: Cursor Hive Intelligence MCP validate_task_result
Add Hive Intelligence MCP to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"mcp": {
"url": "https://mcp.hiveintelligence.xyz/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something validate_task_result does. Cursor lists the server's tools on connect and calls validate_task_result itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Hive Intelligence MCP's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
Hive Intelligence MCP will not start until these are set, so validate_task_result never becomes available.
-
COINGECKO_PRO_API_KEY -
ALCHEMY_API_KEY -
GOPLUS_APP_KEY -
GOPLUS_APP_SECRET -
HELIUS_API_KEY -
MORALIS_API_KEY -
TENDERLY_API_KEY -
TENDERLY_NODE_ACCESS_KEY -
TENDERLY_GATEWAY_ACCESS_KEY -
TENDERLY_ACCOUNT_SLUG -
TENDERLY_PROJECT_SLUG
Same tool, other clients
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.