Claude Desktop natively speaks the Model Context Protocol. Once Hive's MCP server is registered, Claude can call get_token_security and detect_rugpull on any contract address — pulling honeypot logic checks, owner mint permissions, LP-lock status, and a derived risk score from GoPlus before recommending a swap. The flow can run from one user prompt through a short MCP tool sequence; agents using single-provider MCPs (CoinGecko MCP, Moralis Cortex) cannot run this check because they don't expose security tools. The result is grounded in runtime data with freshness metadata when the provider returns it, so Claude is reasoning over current on-chain state rather than training-cutoff data alone.

Client: Claude Desktop · Workflow: Token security

Hive tools used

get_token_security — Returns the GoPlus security report — is_honeypot, buy_tax, sell_tax, owner_change_balance, transfer_pausable, and the full risk envelope.
detect_rugpull — Aggregates GoPlus + on-chain liquidity + contract metadata into a single rugpull_risk_score with structured signal flags.

Steps

Install Hive in Claude Desktop
Add Hive through Claude Desktop's Custom Connectors UI: Settings > Connectors > Add custom connector. Remote MCP does not use claude_desktop_config.json; that file is only for the stdio fallback covered in the Claude Desktop install guide.
```
Name: Hive
URL: https://mcp.hiveintelligence.xyz/mcp
Authentication: Bearer token
Token: YOUR_HIVE_API_KEY
```
Restart Claude Desktop
After saving the connector, start a new Claude chat. Hive's tool surface appears under the tools menu after Claude refreshes the connector; Claude calls tools/list and discovers the available Hive tools.
Ask Claude to scan a token
In a new chat, paste the contract address you want to check and tell Claude what you want. Claude reads the address, picks the right Hive tools, calls them, and synthesizes the result into plain English. No application code is required for this Claude workflow.
Read the structured response
Claude renders the GoPlus + Hive risk envelope as a readable summary: green flags for safe contracts, yellow for caution (sell tax 5-15%, recent ownership change), red for honeypot or active drain risk. Specific values (buy_tax, sell_tax, lp_holders) are quoted inline so you can verify against block explorers.
Decide based on the score
For agents that auto-execute trades, gate the swap behind rugpull_risk_score < 30 and is_honeypot === false. For human-in-the-loop usage, Claude's plain-English summary is enough to make the call in seconds.

Example prompt

Is 0x...abc safe to buy on Ethereum? Check honeypot status, ownership flags, and LP locks before I commit any USDC.

Example output shape

Example output shape (illustrative values; run the tools for live data):

I checked the token with Hive's security tools and received a fresh fetched_at timestamp.

- is_honeypot: false
- buy_tax: 1%, sell_tax: 1%
- transfer_pausable: false
- owner_change_balance: false
- can_take_back_ownership: true (deployer retains upgradeability - moderate risk)
- LP holders: 4 (LP not locked or burned - moderate risk)
- rugpull_risk_score: 38/100 (caution)

This token is not flagged as a honeypot in this example, but the owner and liquidity controls still need review before sizing a trade.

Related glossary terms

Related recipes

Pre-signing token risk checks from Windsurf

Detect rugpulls and honeypots from Claude Desktop