_ registry / mcp streamable-http · checked 25m ago

hive-mcp-server

https://hiveintelligence.xyz

Registry code: f46c0ccc6915f314

api record

Hive serves live crypto data to AI agents through 9 tools, one per research job: find_token, get_token_price, check_token_safety, research_token, analyze_wallet, market_positioning, market_overview, defi_yields, prediction_markets. Pick the tool whose job matches the question; each runs the right data providers on the server and returns one answer. Every section of an answer carries its own source (provider, fetched_at, runtime_status) and every response a _hive receipt; cite them. A section under missing failed: say so, never fill it in. Follow next_action; never retry an unchanged failing…

endpoint
https://hiveintelligence.xyz/mcp also at https://www.hiveintelligence.xyz/mcp
door code
323329c8592b9aef
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is hive-mcp-server live?
Yes — it answered the hub's last check (checked 25m ago). It answered 100% of checks over the last 30 days.
Is hive-mcp-server free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does hive-mcp-server have?
9 tools: prediction_markets, check_token_safety, find_token, research_token, market_overview, get_token_price, analyze_wallet, market_positioning, ….
Is hive-mcp-server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
672ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 32 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
9 auth-required 9 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • prediction_markets auth-required 14h ago

    Odds from Polymarket and Kalshi: search a topic on both venues, or look up one market, with optional price history and order book. Prices are market-implied probabilities, not ground truth; matching the same question across venues is best effort. Example: {"query":"fed december"} or {"market":"KXFED-26DEC","include":["odds","history"]}. Costs 2 credits; each optional include entry (history, orderbook) adds 1. Every section carries its own source receipt (provider, fetched_at, runtime_status); a section that fails is listed under missing and never guessed.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "A topic to search, for example \"fed december\" or \"bitcoin 150k\"."
    },
    "venue": {
      "enum": [
        "polymarket",
        "kalshi",
        "both"
      ],
      "type": "string",
      "description": "Default both for a search; a market is looked up on the venue its id fits."
    },
    "detail": {
      "enum": [
        "summary",
        "full"
      ],
      "type": "string"
    },
    "market": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "One market: a Polymarket slug or a Kalshi ticker."
    },
    "include": {
      "type": "array",
      "items": {
        "enum": [
          "odds",
          "history",
          "orderbook"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Default: odds. Optional: history (price history of the top market per venue), orderbook."
    },
    "response_format": {
      "enum": [
        "json",
        "markdown"
      ],
      "type": "string",
      "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text."
    }
  },
  "additionalProperties": false
}
    arguments 55 lines
  • check_token_safety auth-required 25m ago

    Token security screen for a contract address: honeypot, taxes, ownership, and related GoPlus risk datapoints, plus a summary of LP lock status, top-holder concentration, and creator/owner balances with plain-language verdicts. EVM chains use chain + address; Solana addresses are detected automatically.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "maxLength": 40,
      "description": "Chain name or EVM chain id, for example \"eth\", \"bsc\", \"8453\", or \"solana\". Defaults to eth for 0x addresses; Solana is auto-detected."
    },
    "address": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Required. Token contract address (0x… for EVM, base58 for Solana)."
    },
    "response_format": {
      "enum": [
        "concise",
        "detailed",
        "json",
        "markdown"
      ],
      "type": "string",
      "description": "concise (default) returns the trimmed essentials; detailed returns the full provider payload. json and markdown, the platform-wide values every other tool advertises, are accepted and treated as concise."
    }
  },
  "additionalProperties": true
}
    arguments 27 lines
  • find_token auth-required 10h ago

    Resolve a token name, ticker or contract address to the token people mean: its CoinGecko id, symbol, market cap and contract on each chain. When several tokens share a name or ticker it returns ranked candidates instead of picking one (copycat tokens reuse names). Call it before research_token or check_token_safety when you only have a name. Example: {"query":"PEPE","chain":"base"}. Costs 1 credit. Every section carries its own source receipt (provider, fetched_at, runtime_status); a section that fails is listed under missing and never guessed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "maxLength": 40,
      "description": "Chain to return the contract for, for example \"eth\", \"base\", \"bsc\" or \"solana\"."
    },
    "query": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "A name, ticker or contract address, for example \"PEPE\", \"pepe\" or \"0x6982…\"."
    },
    "response_format": {
      "enum": [
        "json",
        "markdown"
      ],
      "type": "string",
      "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text."
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • research_token auth-required 10h ago

    One due-diligence report on a token: identity, market (price, market cap, FDV, volume), liquidity (top DEX pools), holder concentration and contract safety, each with its own source. Use it for "is this token real, liquid and safe?" A name that several tokens share returns the candidates instead of a report. Example: {"token":"PEPE"} or {"token":"0x6982508145454ce325ddbe47a25d4ec3d2311933","chain":"eth"}. Costs 5 credits; each optional sections entry (supply, insights, top_traders) adds 1. Every section carries its own source receipt (provider, fetched_at, runtime_status); a section that fails is listed under missing and never guessed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "token"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "maxLength": 40,
      "description": "Chain of the contract, for example \"eth\", \"base\" or \"solana\". A 0x address with no chain is read as Ethereum."
    },
    "token": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "A ticker, CoinGecko id, name or contract address."
    },
    "detail": {
      "enum": [
        "summary",
        "full"
      ],
      "type": "string",
      "description": "summary (default) trims each section; full returns more rows."
    },
    "sections": {
      "type": "array",
      "items": {
        "enum": [
          "identity",
          "market",
          "liquidity",
          "holders",
          "safety",
          "supply",
          "insights",
          "top_traders"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Default: identity, market, liquidity, holders, safety. Optional: supply, insights (CoinGecko AI summary, unverified), top_traders."
    },
    "response_format": {
      "enum": [
        "json",
        "markdown"
      ],
      "type": "string",
      "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text."
    }
  },
  "additionalProperties": false
}
    arguments 54 lines
  • market_overview auth-required 14h ago

    What is moving in crypto: trending coins, top gainers and losers, hot DEX pools, and optionally Fear & Greed, market totals, new pools and headlines, each with its own source. Example: {} or {"scope":"solana","window":"1h","sections":["hot_pools","new_pools"]}. Costs 3 credits; each optional sections entry (sentiment, totals, new_pools, news) adds 1. Every section carries its own source receipt (provider, fetched_at, runtime_status); a section that fails is listed under missing and never guessed.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "scope": {
      "type": "string",
      "maxLength": 40,
      "description": "\"global\" (default) or a chain such as \"solana\", \"base\" or \"eth\" for the DEX pool sections."
    },
    "detail": {
      "enum": [
        "summary",
        "full"
      ],
      "type": "string"
    },
    "window": {
      "enum": [
        "1h",
        "24h",
        "7d"
      ],
      "type": "string",
      "description": "Window for movers and hot pools. Default 24h."
    },
    "sections": {
      "type": "array",
      "items": {
        "enum": [
          "trending",
          "movers",
          "hot_pools",
          "sentiment",
          "totals",
          "new_pools",
          "news"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Default: trending, movers, hot_pools. Optional: sentiment (Fear & Greed), totals (global market cap and dominance), new_pools, news."
    },
    "response_format": {
      "enum": [
        "json",
        "markdown"
      ],
      "type": "string",
      "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text."
    }
  },
  "additionalProperties": false
}
    arguments 52 lines
  • get_token_price auth-required 25m ago

    Current price for one token. Pass token as a CoinGecko id or symbol ("bitcoin", "BTC"), or pass chain + address for a specific contract. Returns price, market cap, and 24h change with provider provenance.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "maxLength": 40,
      "description": "Chain name for the contract-address variant, for example \"eth\", \"base\", \"bsc\", or \"solana\"."
    },
    "token": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "CoinGecko coin id or ticker symbol, for example \"bitcoin\" or \"BTC\". Omit when passing chain + address."
    },
    "address": {
      "type": "string",
      "maxLength": 100,
      "description": "Token contract address; requires chain."
    },
    "vs_currency": {
      "type": "string",
      "maxLength": 20,
      "description": "Quote currency. Default \"usd\"."
    },
    "response_format": {
      "enum": [
        "concise",
        "detailed",
        "json",
        "markdown"
      ],
      "type": "string",
      "description": "concise (default) returns the trimmed essentials; detailed returns the full provider payload. json and markdown, the platform-wide values every other tool advertises, are accepted and treated as concise."
    }
  },
  "additionalProperties": true
}
    arguments 37 lines
  • analyze_wallet auth-required 14h ago

    What a wallet holds and what it has been doing: holdings with USD values by default, plus optional PnL, recent activity, Hyperliquid perps, Polymarket positions, NFTs, a known-malicious check and token approvals, each with its own source. Replaces get_wallet_portfolio (still callable). Example: {"address":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","include":["holdings","pnl"]}. Costs 1 credit; each optional include entry (pnl, activity, perps, predictions, nfts, risk, approvals) adds 1. Every section carries its own source receipt (provider, fetched_at, runtime_status); a section that fails is listed under missing and never guessed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "maxLength": 40,
      "description": "EVM chain for the chain-specific sections (activity, nfts, risk, approvals). Default \"eth\". Solana is detected from the address."
    },
    "detail": {
      "enum": [
        "summary",
        "full"
      ],
      "type": "string"
    },
    "address": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Wallet address: 0x… for EVM chains, base58 for Solana."
    },
    "include": {
      "type": "array",
      "items": {
        "enum": [
          "holdings",
          "pnl",
          "activity",
          "perps",
          "predictions",
          "nfts",
          "risk",
          "approvals"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Default: holdings. Optional: pnl (DEX trading PnL), activity (recent transfers), perps (Hyperliquid positions), predictions (Polymarket positions), nfts, risk (known-malicious check), approvals (token approvals)."
    },
    "response_format": {
      "enum": [
        "json",
        "markdown"
      ],
      "type": "string",
      "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text."
    }
  },
  "additionalProperties": false
}
    arguments 53 lines
  • market_positioning auth-required 10h ago

    How a coin's derivatives market is positioned, across venues, now or over a window: funding rates, open interest, liquidations by side, long/short ratios, and optionally predicted funding, basis and volume leaders. Liquidations are totalled per venue and side on the server. Example: {"asset":"BTC"} or {"asset":"ETH","window":"7d","metrics":["funding","open_interest","basis"]}. Costs 4 credits; each optional metrics entry (predicted_funding, basis, volume_leaders) adds 1. Every section carries its own source receipt (provider, fetched_at, runtime_status); a section that fails is listed under missing and never guessed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "maxLength": 20,
      "minLength": 1,
      "description": "Base coin, for example \"BTC\", \"ETH\" or \"SOL\"."
    },
    "detail": {
      "enum": [
        "summary",
        "full"
      ],
      "type": "string"
    },
    "venues": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 30,
        "minLength": 1
      },
      "maxItems": 10,
      "description": "CCXT exchange ids for live funding, default [\"binance\",\"bybit\",\"okx\",\"bitget\"]."
    },
    "window": {
      "type": "string",
      "maxLength": 30,
      "description": "\"now\" (default: latest values and the last 24h of liquidations), \"24h\", \"7d\", \"30d\", or a start date (YYYY-MM-DD). History comes from the Hive Archive."
    },
    "metrics": {
      "type": "array",
      "items": {
        "enum": [
          "funding",
          "open_interest",
          "liquidations",
          "long_short",
          "predicted_funding",
          "basis",
          "volume_leaders"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Default: funding, open_interest, liquidations, long_short. Optional: predicted_funding (Hyperliquid), basis, volume_leaders (Hyperliquid)."
    },
    "response_format": {
      "enum": [
        "json",
        "markdown"
      ],
      "type": "string",
      "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text."
    }
  },
  "additionalProperties": false
}
    arguments 62 lines
  • defi_yields auth-required 25m ago

    DeFi from DeFiLlama: compare one or two protocols on TVL and fees, or find the best yields with a minimum TVL, a chain and a stablecoin filter, each with its own source. Example: {"protocols":["aave","compound"]} or {"stablecoin_only":true,"chain":"Ethereum"}. Costs 2 credits; each optional metrics entry (stablecoins) adds 1. Every section carries its own source receipt (provider, fetched_at, runtime_status); a section that fails is listed under missing and never guessed.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "maxLength": 40,
      "description": "Filter yields to one chain (DeFiLlama name, for example \"Ethereum\", \"Arbitrum\", \"Solana\"); also the chain for stablecoins. Default all chains, and Ethereum for stablecoins."
    },
    "detail": {
      "enum": [
        "summary",
        "full"
      ],
      "type": "string"
    },
    "metrics": {
      "type": "array",
      "items": {
        "enum": [
          "tvl",
          "fees",
          "yields",
          "stablecoins"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Default: tvl and fees for protocols, yields otherwise. Optional: stablecoins (supply on the chain)."
    },
    "protocols": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 60,
        "minLength": 1
      },
      "maxItems": 2,
      "description": "One or two DeFiLlama protocol slugs to compare, for example [\"aave\",\"compound\"]. Omit for a yield search."
    },
    "min_tvl_usd": {
      "type": "number",
      "minimum": 0,
      "description": "Yields: minimum pool TVL in USD. Default 1,000,000, which filters out most traps."
    },
    "response_format": {
      "enum": [
        "json",
        "markdown"
      ],
      "type": "string",
      "description": "Output format: 'json' for structured data (default) or 'markdown' for human-readable text."
    },
    "stablecoin_only": {
      "type": "boolean",
      "description": "Yields: only stablecoin pools."
    }
  },
  "additionalProperties": false
}
    arguments 59 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f46c0ccc6915f314.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f46c0ccc6915f314/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f46c0ccc6915f314/badge.svg)](https://brick.blue/agent/f46c0ccc6915f314?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on hiveintelligence.xyz 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.