IntentGuard MCP Server

IntentGuard MCP Server

Enables AI agents to submit Ethereum transactions with on-chain outcome protection by wrapping DeFi transactions with enforcement transactions that drop the bundle if balance constraints are violated.

Category
Visit Server

README

IntentGuard MCP Server

Includes a full end-to-end agent simulation test runnable locally in dry-run mode (no chain required).

A Model Context Protocol server that gives AI agents the ability to submit Ethereum transactions with on-chain outcome protection.

IntentGuard wraps any DeFi transaction with two enforcement transactions. If the declared balance constraints are violated at execution time, the transaction is dropped before inclusion — and no gas is consumed.


Architecture

The MCP server has a single, well-defined role: it builds the two protective transactions and validates the signed bundle before submission. It does not build or inspect the underlying DeFi transaction.

Protocol skill / wallet  →  builds the action transaction
IntentGuard agent skill  →  extracts and confirms protection constraints
IntentGuard MCP          →  compiles protection package, validates and submits
On-chain enforcer        →  allows or rejects execution

The MCP exposes exactly two tools:

Tool Role
prepare_protected_transaction Compiler — produces two unsigned enforcement transactions and a nonce layout
submit_protected_bundle Submitter — validates the signed bundle (pre + action + post) and submits to the relay

Prerequisites

  • Node.js >= 22
  • Access to the IntentGuard relay (default: https://sepolia.rpc.intentguard.xyz)

Install & Build

npm install
npm run build

The compiled entrypoint is dist/index.js. It includes a #!/usr/bin/env node shebang and is executable.


Configuration

The server is configured entirely via environment variables.

Variable Required Default Description
INTENTGUARD_CHAIN_ID yes EVM chain ID (e.g. 11155111 for Sepolia, 1 for mainnet)
INTENTGUARD_RPC_URL no https://sepolia.rpc.intentguard.xyz IntentGuard relay endpoint
INTENTGUARD_ENFORCER_TYPE no balance Enforcer contract type

The enforcer contract address is resolved automatically from the relay — no contract address configuration is required.


Connecting to an Agent

Add the server to your agent's MCP configuration. Example for Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "intentguard": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-server/dist/index.js"],
      "env": {
        "INTENTGUARD_CHAIN_ID": "11155111"
      }
    }
  }
}

The agent spawns the server as a subprocess over stdio. No port or hosting is required.


Tools

prepare_protected_transaction

Produces two unsigned enforcement transactions that wrap a given action transaction.

Does not receive or build the action transaction. The action transaction is constructed upstream by the wallet or protocol skill.

Input:

  • userAddress — wallet address that will sign all three transactions
  • protectionIntent — structured protections:
    • max_spend — cap outflow of a token
    • min_receive — guarantee minimum inflow of a token
    • no_balance_decrease — ensure balance does not decrease
  • validUntilBlock (optional) — protection expiry block; defaults to current block + 10

Output:

  • preTx — unsigned pre-enforcement transaction (nonce N)
  • postTx — unsigned post-enforcement transaction (nonce N+2)
  • nonceLayout{ pre: N, action: N+1, post: N+2 }
  • summary — human-readable protection list and signing instructions

The caller assigns nonceLayout.action to the action transaction and signs all three.


submit_protected_bundle

Validates and submits a fully signed bundle of three transactions.

Input:

  • signedPreTx — signed pre-enforcement transaction (nonce N)
  • signedUserTx — signed action transaction (nonce N+1, built externally)
  • signedPostTx — signed post-enforcement transaction (nonce N+2)
  • retryUntilBlock (optional) — retry deadline; defaults to current block + 25

Pre-submission validation (failures returned immediately, no submission attempt):

  1. All three transactions are EIP-1559 (type 2)
  2. All three are signed by the same address
  3. Nonces are strictly sequential: N, N+1, N+2
  4. All three target the same chain ID

Return:

  • Constraints satisfied → transaction hash, signer, confirmed nonce layout
  • Constraints violated → bundle dropped, no gas paid

Returns the final bundle outcome directly. No separate receipt polling is required.


Testing

npm test

The test suite covers:

  • Nonce layout assignment and boundary cases
  • Output shape — action transaction is never returned by the MCP
  • Default block window behaviour
  • All protection types (max_spend, min_receive, no_balance_decrease)
  • Input schema validation
  • Bundle validation (nonce ordering, signer consistency, chain ID consistency)
  • Error paths (network failures, SDK errors, malformed inputs)
  • Full end-to-end flow: prepare → sign → submit

End-to-end test (agent simulation)

This repository includes a full end-to-end test that simulates an AI agent using IntentGuard over the MCP protocol.

The script:

  • launches the MCP server as a subprocess (stdio transport, exactly as Claude / Cursor do)
  • connects as an MCP client
  • calls prepare_protected_transaction
  • assigns nonce N+1 to the action transaction (built externally, never passed to MCP)
  • signs all three transactions (preTx, actionTx, postTx)
  • optionally submits the bundle

Run locally — no chain required

INTENTGUARD_CHAIN_ID=11155111 npm run agent-e2e:dry

Verifies: MCP connectivity over stdio, nonce assignment (N, N+1, N+2), bundle construction, and transaction signing. The relay is contacted for nonce and block number but no transaction is submitted.

Full execution (Sepolia)

INTENTGUARD_CHAIN_ID=11155111 TEST_PRIVATE_KEY=0x... npm run agent-e2e

Requires a funded Sepolia wallet. Submits the signed bundle to the relay.

What this test simulates

Role Responsibility
Upstream builder constructs the action transaction and assigns nonce N+1
IntentGuard agent calls prepare_protected_transaction
Signing agent signs all three transactions
Orchestrator assembles and submits the bundle
MCP server validates and submits

This is a full protocol-level test of the IntentGuard execution flow.


Scripts

Script Description
npm run build Compile to dist/
npm run dev Run directly from source with tsx
npm test Run the test suite
npm run typecheck TypeScript type check without emit
npm run agent-e2e:dry Full agent simulation, dry-run (no submission)
npm run agent-e2e Full agent simulation with bundle submission (Sepolia)

License

MIT

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured