← Back to directory

Hookr MCP

HookTech Labs, Inc. · Crypto & Digital Assets

MCP ServerCommunity

Hookr MCP exposes pool, quote, liquidity-position and revenue-token data from Hookr on Robinhood Chain, with separate servers for Monad, Arbitrum and Elysium. It prepares unsigned calls for swaps, limit orders, liquidity changes, launches and income claims, while the user's wallet signs and sends transactions. Digital-asset investment and operations teams could use it to research DeFi positions, prepare transactions and retrieve wallet income records.

cryptodefiuniswap v4pool analyticsunsigned transactionsliquidityrevenue tokens
Status
Community
Auth
None
Hosting
Remote
Community rating
Not rated yet
Role

Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers → All seven roles →

Open documentation →

Caveats

  • Capabilities and safeguards are vendor-reported and have not been independently verified. The server prepares transaction calls but does not itself sign, send transactions or place orders; the user's wallet must execute them.
  • The vendor reports that the server holds no signing key. Wallet addresses are supplied for wallet-specific reads and transaction preparation; the page does not describe request retention or data-handling policies.
  • Coverage is network- and tool-specific. The default server reads Robinhood Chain; the vendor lists smaller tool sets on separate Monad, Arbitrum and Elysium endpoints. Many reads cover only Hookr-listed pools or tokens.
  • Vendor-reported limits include a burst of 24 tool calls followed by one call every two seconds, 64 KB request bodies and 512 KB responses. Edge throttling can also affect tool discovery, and cross-site browser calls are blocked.
  • HookrScan is described by the vendor as a screening tool, not an audit: it does not run hooks or simulate trades. Missing readings can return unknown or unavailable, which must not be treated as approval or zero.
  • Transaction costs and contract restrictions remain relevant despite unauthenticated MCP access. Onchain fees apply, approvals may require separate transactions, and the vendor says tokenizing liquidity positions without termDays locks them permanently.
  • Start with read-only scopes and keep client-side approval prompts on until the connection is proven.
Rate this server

How to connect Hookr MCP

Step 1

Remote server: paste a URL

Hookr MCP publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.

Endpoint

https://hookr.fun/api/mcp

Client config snippet

{
  "mcpServers": {
    "c6c611d0-f759-4a5e-a09e-8fa6d6abfe53": {
      "url": "https://hookr.fun/api/mcp"
    }
  }
}

Step 2

Authenticate with no credentials

No credentials are required for public data. Rate limits still apply, so avoid bulk pulls from a chat client.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Crypto & Digital Assets.

Digital asset holdings snapshot

One consolidated view across exchanges and wallets.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: consolidate my digital asset holdings across every connected source, exchange accounts, on-chain wallet or explorer tools, and any brokerage account holding crypto or crypto ETPs, into one table: asset, quantity, venue, source tool, USD value and share of total. Show a per-source subtotal so I can see which tool reported what, and flag any asset that appears in more than one source so it is not double-counted. Mask wallet addresses beyond the first and last four characters. Do not trade, transfer, approve or sign anything.

Guardrail · Read-only keys only. Never give a chat tool withdrawal or signing permissions.

Cost basis and realised gains review

A tax-ready view of what was sold and when.

Crypto & Digital AssetsCrypto & Digital AssetsAccounting & Tax

Read-only: list realised gains and losses on digital assets for <tax year> by combining exchange transaction history with on-chain transfer data, then compare the result to what is already recorded in my accounting or tax system. Show acquisition date, disposal date, proceeds, basis and the source tool for each line, and flag every transaction where basis is missing, inferred, or disagrees between the exchange and the books. Do not file, submit, amend or post any journal entry. This is a working draft for the tax preparer.

Guardrail · Draft only. Crypto basis data is often incomplete, verify before filing.

Venue and counterparty risk review

Where the assets actually sit and what that exposes you to.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: map where my digital asset exposure actually sits by combining exchange or custodial venue data, on-chain wallet and staking or DeFi data, and any crypto exposure held through brokerage accounts. For each venue describe the counterparty, smart-contract and liquidity risk, and note any concentration above <threshold>% of total digital assets across all sources combined. State which figures came from which tool and what you could not verify on-chain. No recommendations to move funds and no transactions.

Guardrail · Read-only. Never approve token allowances or transactions from a chat session.

Read the full connection guide →