DEVELOPER DOCUMENTATION / V0.3

Connect your agent.

HYPEGENT offers a hosted, authenticated HyperCore MCP endpoint and a local MCP server for HyperCore, HyperEVM and Kinetiq Elysium testnet. No private keys or transaction signing required.

01 / Connect to hosted MCP

Remote MCP uses Streamable HTTP. The hosted preview exposes seven read-only tools across HyperCore, HyperEVM, and Kinetiq Elysium Testnet. Obtain an individually provisioned API key from the operator; never paste tokens into a public website or repository.

Endpoint: https://hypegent-mcp-production.up.railway.app/mcp
Authorization: Bearer YOUR_PERSONAL_API_KEY

For clients that support custom HTTP headers, configure the endpoint and Authorization header. Example client configuration (only if your client supports this format):

{
  "mcpServers": {
    "hypegent": {
      "type": "http",
      "url": "https://hypegent-mcp-production.up.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PERSONAL_API_KEY"
      }
    }
  }
}

The remote server supports an operator token and separately provisioned SHA-256-hashed client keys. Self-service signup, key management, and public issuance are not yet available. Internal MCP initialize, tools/list, HyperCore mid-price tool call, and both EVM block-number checks passed. Third-party desktop client compatibility is not yet verified.

02 / Operator key provisioning

Until self-service accounts are available, an authorized operator can generate a client key locally with the command below. Give the raw key to the intended client through a secure channel and append only its SHA-256 digest to MCP_API_KEY_SHA256 on the Railway MCP service. Existing hashes are comma-separated. Redeploy to apply additions or revocations. Never expose the operator token or the raw client key in a browser.

node packages/mcp/scripts/generate-api-key.mjs

Keys are rate-limited per credential in each server process. This is not yet a distributed or database-backed quota system.

03 / Local install

git clone https://github.com/imaaiagent/hypegent.git
cd hypegent
npm install
npm run build -w @hypegent/mcp

Node.js 20+ required. The repository is currently private: GitHub access is needed to clone it. This package is not published to npm.

04 / Configure a local MCP client

Configure your MCP-compatible desktop client to launch the compiled local stdio server. Replace the absolute path with the path on your computer.

{
  "mcpServers": {
    "hypegent": {
      "command": "node",
      "args": [
        "/ABSOLUTE/PATH/hypegent/packages/mcp/dist/index.js"
      ]
    }
  }
}

Restart the MCP client after saving the configuration. Do not point an MCP client at the marketing website URL; the website is not an MCP transport endpoint.

05 / Available local tools

The hosted server exposes list_networks, hypercore_markets, hypercore_spot_markets, hypercore_mid_prices, hypercore_orderbook, evm_block_number, and evm_native_balance. The full list below describes the local server; funding history, account state, and tool search are local-only.

05 / Network configuration

Optional environment variables: HYPERCORE_API_URL, HYPEREVM_RPC_URL, ELYSIUM_TESTNET_RPC_URL. HyperEVM chain ID 999; Elysium testnet chain ID 99801. Elysium mainnet is not enabled.

06 / Safety & limitations

This preview does not place trades, sign transactions, bridge assets, or custody wallets. Data is requested from third-party APIs and RPCs and may be delayed or unavailable. Verify information independently before making financial decisions.