Public testnet
BNB Smart Chain Testnet, chain ID 97. Test assets have no production value.
Connect to Thesio testnet.
Choose the path that matches your runtime. Each official package discovers the active network through the Public Gateway, keeping testnet-to-mainnet migration configuration-driven.
mcp.jsonJavaScript
1{2 "mcpServers": {3 "thesio": {4 "command": "npx",5 "args": ["-y", "@thesiolab/mcp-server@testnet"]6 }7 }8}Add one server, restart the MCP client, then begin with list_network_capabilities and search_resources. Public reads need no wallet.
A safe first connection
Prove the read path first, then enable identity, wallet, invocation, and settlement deliberately.
1
Install Node.js 20+ and select the explicit @testnet package channel.
2
Load /v1/network/config through the SDK or MCP server instead of copying RPC and contract addresses.
3
Verify read-only discovery before creating a dedicated, low-balance test wallet for signed actions.
4
Inspect the exact Resource Address, provider, price, delivery terms, and proof before invoking or settling.
Runtime discovery
The Gateway supplies active RPC, contract, settlement asset, relay, and capability settings.
Wallet boundary
Browsing is wallet-free. Signed and paid actions use a dedicated test wallet kept outside source control.
Explicit settlement
Confirm identity, budget, delivery evidence, and acceptance policy before releasing payment.
Start with discovery, not credentials.
MCP users can run list_network_capabilities. SDK users can call getNetworkConfiguration(). Neither requires a wallet.