hivetrust_verify_bond — HiveTrust MCP Tool
hivetrust_verify_bond
(hivetrust verify bond) 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_verify_bond from your client
- Claude Code HiveTrust hivetrust_verify_bond run in your project directory
- Claude Desktop HiveTrust hivetrust_verify_bond ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor HiveTrust hivetrust_verify_bond ~/.cursor/mcp.json
- VS Code HiveTrust hivetrust_verify_bond .vscode/mcp.json
- Zed HiveTrust hivetrust_verify_bond ~/.config/zed/settings.json
- Windsurf HiveTrust hivetrust_verify_bond ~/.codeium/windsurf/mcp_config.json
- Cline HiveTrust hivetrust_verify_bond ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI HiveTrust hivetrust_verify_bond ~/.gemini/settings.json
- Grok HiveTrust hivetrust_verify_bond .mcp.json (in your project root)
- ChatGPT HiveTrust hivetrust_verify_bond Settings → Connectors → Advanced → Developer mode
- Claude.ai HiveTrust hivetrust_verify_bond Settings → Connectors → Add custom connector
- LangChain HiveTrust hivetrust_verify_bond 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_file_dispute
- hivetrust_get_platform_stats
- hivetrust_create_lease
- hivetrust_stake_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.