hiveconsult_reason
Structured Reasoning
Submit a question or problem for structured chain-of-thought reasoning. Returns step-by-step analysis with confidence score and recommendations.
didrequireddomaincontextquestionrequiredreasoning_depth
io.github.srotzinPublished by GitHub account srotzinv1.0.0Updated Oct 25, 2026
Agent-to-agent reasoning-as-a-service: chain-of-thought, analysis, and decision support.
A remote reasoning-as-a-service endpoint that gives an assistant tools for structured chain-of-thought, data analysis, weighted decision support and document or
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.srotzin%2Fhiveconsult/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"hive-consult": {
"type": "http",
"url": "https://hiveconsult.onrender.com/mcp"
}
}
}Agent-to-agent reasoning-as-a-service. Provides structured reasoning, data analysis, decision support, and code/document review via REST API and MCP protocol.
Internal (platform-to-platform):
Bypasses payment for inter-service calls.
External (agent-to-agent):
Uses x402 micropayment protocol. If no payment is provided, the API returns 402 Payment Required with a payment challenge including USDC amount, recipient address, and accepted methods. Include payment proof in the X-Payment header.
HiveConsult exposes an MCP-compatible JSON-RPC 2.0 endpoint at /mcp.
hiveconsult_reason — Structured reasoning with configurable depthhiveconsult_analyze — Data analysis (trend, anomaly, forecast, comparison)hiveconsult_decide — Multi-criteria decision supporthiveconsult_review — Code/contract/document/strategy reviewThe server starts on port 3000 (configurable via PORT env var).
MIT
Hive Civilization is the cryptographic backbone of autonomous agent commerce — the layer that makes every agent transaction provable, every payment settable, and every decision defensible.
This repository is part of the PROVABLE · SETTABLE · DEFENSIBLE pillar.
Source: README.md at commit 6965be6
Structured Reasoning
Submit a question or problem for structured chain-of-thought reasoning. Returns step-by-step analysis with confidence score and recommendations.
didrequireddomaincontextquestionrequiredreasoning_depthData Analysis
Analyze data for trends, anomalies, forecasts, or comparisons. Returns structured findings with confidence scores.
didrequireddatarequiredanalysis_typeDecision Support
Decision support: rank options against weighted criteria. Returns scored and ranked options with reasoning.
didrequiredoptionsrequiredweightscriteriarequiredContent Review
Review code, contracts, documents, or strategies. Returns issues, recommendations, and risk score.
didrequiredcontentrequiredreview_type100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
x-hive-internal: <service_key>POST /mcp{ "jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {}}POST /mcp{ "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "hiveconsult_reason", "arguments": { "did": "did:hive:my_agent", "question": "Should we migrate from REST to GraphQL?", "reasoning_depth": "standard", "domain": "architecture" } }}npm installnpm startcurl -X POST http://localhost:3000/v1/consult/reason \ -H "Content-Type: application/json" \ -H "x-hive-internal: <service_key>" \ -d '{ "did": "did:hive:my_agent", "question": "What is the optimal caching strategy for a read-heavy API?", "reasoning_depth": "standard", "domain": "backend" }'curl -X POST http://localhost:3000/v1/consult/decide \ -H "Content-Type: application/json" \ -H "x-hive-internal: <service_key>" \ -d '{ "did": "did:hive:my_agent", "options": ["Redis", "Memcached", "CDN edge cache"], "criteria": ["latency", "cost", "complexity", "scalability"], "weights": [0.4, 0.2, 0.15, 0.25] }'