QHOOKS / SUPPORT
Get connected.
Keep control.
One public MCP endpoint. Start with a read, then prepare the action you need.
Prepared for the signing wallet: the agent's own wallet or yours. No custody. We never hold keys.
01 / CONNECT
Choose your client
Use https://qhooks.com/mcp with no authentication. QHooks does not need an API key. Availability in your client depends on its account and workspace settings.
Claude Desktop
Connect Claude Desktop
Open Customize → Connectors → Add custom connector. Name it QHooks, paste this URL and choose No sign in. Enable it in your conversation. Workspace policy may control custom connectors.
https://qhooks.com/mcpClaude Web
Use QHooks in Claude on the web
Add a custom remote connector in Customize → Connectors. Enter QHooks and the URL below, choose No sign in, then enable it in the conversation. No local bridge is required.
https://qhooks.com/mcpChatGPT
Connect ChatGPT
In Plugins, choose + → Add custom MCP server. Name it QHooks, paste this public endpoint and select no authentication. Review its tools and create the plugin. Account and workspace policies apply.
https://qhooks.com/mcpCursor
Add QHooks to Cursor
Use Add to Cursor and review the connection in the editor. Or merge this into your project’s .cursor/mcp.json. No environment variables or credentials.
{
"mcpServers": {
"qhooks": {
"url": "https://qhooks.com/mcp"
}
}
}Codex
Give Codex the QHooks tools
Run the CLI command, or add the TOML entry to your Codex config. The default is ~/.codex/config.toml; trusted projects may use .codex/config.toml.
[mcp_servers.qhooks]
url = "https://qhooks.com/mcp"VS Code
Use QHooks with VS Code
Merge this into .vscode/mcp.json, or use MCP: Add Server → HTTP and paste the endpoint. Review the server, then enable its tools in your agent conversation.
{
"servers": {
"qhooks": {
"type": "http",
"url": "https://qhooks.com/mcp"
}
}
}For Eliza, GOAT, AgentKit and plain REST examples, open all agent setups. The tool contract contains current chains, tools and signing flows.
02 / RECOVER
When something gets stuck
- The client asks for an API key
- Select No authentication / No sign in. Use the remote HTTPS endpoint, not an invented local command or token.
- Tools do not appear
- Check that the URL ends in
/mcp, refresh the connector's tools, and restart or reload the client if needed. An organization admin may need to allow custom connectors. Do not buy a plan just to troubleshoot this page. - HTTP 429
- Wait for the returned
Retry-Afterwhen present. Avoid retry loops and parallel duplicate requests. - “Refreshing” or missing data
- The stored record or upstream data is unavailable. Wait and try again later. Missing data is not zero or a clean safety result.
- The tool is not in the catalog
- Read
tools/listagain. Some tools and chains are held or unavailable. Do not invent a replacement endpoint or report a preparation as completed. - A quote or prepared plan expired
- Re-read state and prepare again after changing the wallet, network, amount, approvals or terms. Review the returned fees and exact calls before the intended wallet signs.
- Can I paste a key here?
- No. Keep signing in the wallet you control. Never send a key, seed phrase, password or wallet backup to QHooks, feedback or support.
03 / KNOW THE BOUNDARIES
Reads, plans and public data
Cached/D1 tool reads have no hourly or daily quota, with abuse protection of 60 requests per minute per IP. Actual upstream fills and fresh state reads have a separate 20-per-minute IP guard; public-only cold portfolio fills allow 5 per minute. Cache hits skip the upstream guard. Rate-limit responses include Retry-After. Feedback, signed submissions and paid-attempt limits stay unchanged. Existing market routes can apply additional limits. The live tool response and API documentation are authoritative.
A prepared transaction is not a signed or completed trade. Launches and Solana use the documented site flows; perpetual orders use their venue's signing flow. Stored QProof records are evidence, not a guarantee.
QHooks records aggregate API counts. Optional feedback stores the text you explicitly choose to send. Wallet-verified profiles, board posts and competition entry require separate signatures. Read the privacy policy and terms.
04 / ASK US
Tell us where it stopped.
Email team@qhooks.com with your client name, the tool or route, approximate UTC time, and the error. Share only the public inputs needed to reproduce it. Remove keys, tokens and unrelated private data.
Feedback is optional. Ask your agent to send it only when you want the team to receive your text.