hivetrust_file_dispute — HiveTrust MCP Tool
hivetrust_file_dispute
(hivetrust file dispute) is one of 17 tools on the
HiveTrust
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call hivetrust_file_dispute from your client
- Claude Code HiveTrust hivetrust_file_dispute run in your project directory
- Claude Desktop HiveTrust hivetrust_file_dispute ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor HiveTrust hivetrust_file_dispute ~/.cursor/mcp.json
- VS Code HiveTrust hivetrust_file_dispute .vscode/mcp.json
- Zed HiveTrust hivetrust_file_dispute ~/.config/zed/settings.json
- Windsurf HiveTrust hivetrust_file_dispute ~/.codeium/windsurf/mcp_config.json
- Cline HiveTrust hivetrust_file_dispute ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI HiveTrust hivetrust_file_dispute ~/.gemini/settings.json
- Grok HiveTrust hivetrust_file_dispute .mcp.json (in your project root)
- ChatGPT HiveTrust hivetrust_file_dispute Settings → Connectors → Advanced → Developer mode
- Claude.ai HiveTrust hivetrust_file_dispute Settings → Connectors → Add custom connector
- LangChain HiveTrust hivetrust_file_dispute pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hivetrust https://hivetrust.onrender.com/mcpOther tools on this server
- hivetrust_register_agent
- hivetrust_get_agent
- hivetrust_verify_identity
- hivetrust_get_trust_score
- hivetrust_verify_agent_risk
- hivetrust_ingest_telemetry
- hivetrust_issue_credential
- hivetrust_verify_credential
- hivetrust_revoke_credential
- hivetrust_get_insurance_quote
- hivetrust_bind_insurance
- hivetrust_file_claim
- hivetrust_get_platform_stats
- hivetrust_create_lease
- hivetrust_stake_bond
- hivetrust_verify_bond
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.