Live on Elysium mainnetThe Tesera MCP gateway

How it works

Tesera is a hosted MCP gateway for on-chain networks, starting with Elysium. You add one URL to your AI client, and from then on you can ask it to read the chain, explain and simulate transactions, ship contracts, or act within limits you set. This page walks through what happens between your question and the answer.

Endpointmcp.teseralab.com/elysium
NetworkElysium mainnet
ReadsFree, and need no wallet
MCP in one paragraph

MCP, the Model Context Protocol, is an open protocol for connecting AI clients to tools. A client that supports it, such as Claude, Claude Code, ChatGPT, Cursor, VS Code or Devin Desktop, can be pointed at an MCP server and will then see that server's tools, with a description of what each one does and what it needs. When you ask for something, the AI decides which tool fits, calls it, and uses the answer in its reply. Tesera is an MCP server built for on-chain networks, and Elysium is the first network it serves.

01

The path of a request

What happens after you ask a question in your AI client.

Your AI clientClaude, Claude Code, ChatGPT,Cursor, VS Code, Devin Desktopyou ask in plain words TeseraHosted MCP servermcp.teseralab.com/elysiumholds no keys ElysiumRPC nodeBlock explorerOrbit L2, settles to HyperEVM Your walletsigns anything that moves funds 1 tool call 2 read or send 3 data 4 result you sign when needed
Fig. 1A read goes through steps 1 to 4 and needs nothing from you beyond the question. When a request would move funds or deploy a contract, Tesera returns an unsigned transaction with a simulation of what it will do, you sign it in your wallet, and only the signed transaction is broadcast.
01 · You ask

You type a request in your AI client in plain words, for example “why did my last deposit fail?”.

Your AI client
02 · A tool is picked

The client already knows Tesera's tools and their inputs, so the AI chooses the ones that fit, here elysium_get_transaction and elysium_trace_call, and fills in the hash.

MCP tool call
03 · Tesera works

Tesera runs the call against its own Elysium nodes, the block explorer and its index of the Elysium docs, decodes everything it can by name, and returns structured data the AI can read without guessing.

Elysium nodes, explorer, docs
04 · Back to you

The AI answers in the chat. If you asked it to move funds, the answer includes a prepared transaction and a plain preview of its effect, for you to check and sign.

Your AI client
02

Four groups of tools

Sorted by what each tool is allowed to do.

Group 019 tools

Read

Balances, transactions, blocks, contract state, events, token details, verified source and live gas prices, plus a docs search so the AI checks the source before it answers. Reads are free and need no wallet.

elysium_get_balance
elysium_get_transaction
elysium_get_block
elysium_read_contract
elysium_get_logs
elysium_token_info
elysium_contract_info
elysium_gas_price
elysium_search_docs

Group 023 tools

Understand

Simulate a transaction against live state before it is sent, decode any transaction into plain parts, and trace a failure to the exact call that caused it.

elysium_simulate
elysium_decode_transaction
elysium_trace_call

Group 035 tools

Build

Start from audited templates, compile Solidity, estimate the cost in HYPE, prepare a simulated deployment for you to sign and verify the source on the explorer.

elysium_scaffold
elysium_compile
elysium_estimate_gas
elysium_deploy
elysium_verify

Group 045 tools

Act

Turn a plain request into a transaction or a batch, preview and simulate it, send it once signed and wait for the result. Agent keys let agents act inside limits you set.

elysium_prepare_transaction
elysium_prepare_batch
elysium_send_signed
elysium_wait
elysium_key_status

Next come alerts when something happens on a contract, and HyperCore data once Kinetiq ships its HyperCore hooks, which it plans for about a month after Elysium mainnet.

See every tool →
03

How signing works

Tesera never holds private keys and never asks for a seed phrase.

Example in the default mode
You Send 25 HYPE to 0x7a3f...c91e AI calls elysium_prepare_transaction Tesera simulates it against live state to 0x7a3f...c91e value 25 HYPE fee from elysium_estimate_gas result succeeds, sends 25 HYPE You check the preview and sign in your wallet AI calls elysium_send_signed AI calls elysium_wait and reports the result
Default

Simulated, then signed by you

Anything that changes state comes back as an unsigned transaction with a plain preview of what it will do. You review it and sign it in your own wallet, and only then does Tesera broadcast it.

Optional

An agent key with limits

For agents that run without asking each time, you create an agent key in your own wallet, fund it and set hard limits. The agent can act inside those limits only, and you can revoke the key at any time.

Capper transaction and per day
Scopeallowed contracts and functions
Expirywhen the key stops working
Always

A record of every action

Every call is written to your action log in the Tesera console, with what was asked, what was prepared and what was sent. Each key has its own rate limits.

04

One gateway, many networks

Elysium first. The same shape everywhere after it.

Network 01

Elysium

Live from day one of Elysium mainnet, 9 November 2026, with all four tool groups.

Endpoints

One URL per network

Each network gets its own endpoint, such as mcp.teseralab.com/elysium, so you choose exactly which chains your AI can reach.

Portable

Same tools, same limits

Tool shapes, agent keys, logs and rate limits work the same way on every network, so an agent built for Elysium carries over without a rewrite.

Next

HyperCore data

HyperCore market data on Elysium, once Kinetiq's hooks are live.

Tesera is independent and is not affiliated with Kinetiq or Hyperliquid.

Connect your AI →