Hyperlane MCP Server

deploy-chain

Deploy a new blockchain to the Hyperlane cross-chain network by specifying chain name, ID, RPC URL, and token details to enable cross-chain messaging and asset transfers.

Instructions

Deploys a new chain to the Hyperlane network.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chainName": "<chainName>",
      "chainId": "<chainId>",
      "rpcUrl": "<rpcUrl>",
      "tokenSymbol": "<tokenSymbol>",
      "tokenName": "<tokenName>"
    },
    "name": "deploy-chain"
  }
}

Input Schema

Name	Required	Description
`chainName`	Yes	Name of the chain to deploy
`chainId`	Yes	Chain ID of the chain to deploy
`rpcUrl`	Yes	RPC URL for the chain
`tokenSymbol`	Yes	Native token symbol
`tokenName`	Yes	Native token name
`isTestnet`	No	Whether this is a testnet chain

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 29, 2025

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Deploys' which implies a write/mutation operation, but doesn't cover critical aspects like permissions needed, whether it's destructive, rate limits, or what happens on failure. This is a significant gap for a deployment tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, clearly stating the core purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a deployment tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'deploying a chain' entails operationally, what the expected outcome is, or any behavioral constraints. Given the complexity implied by 6 parameters, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 6 parameters. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Deploys') and resource ('a new chain to the Hyperlane network'), providing a specific purpose. However, it doesn't explicitly differentiate from sibling tools like 'deploy-warp-route' or 'run-relayer', which may involve different deployment aspects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on the name alone without distinguishing from sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server