mcpbeat Sign in

AgentExec WebMCP & Base L2 Gateway MCP Server

answering

AgentExec WebMCP & Base L2 Gateway is answering right now. Last checked 13 min ago. It exposes 4 tools.

Monetization and execution gateway for autonomous AI agents on Base Mainnet

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 59 days of history · worst day 0%
59 days agonow
98.9%
Uptime 24h
90 of 91 checks
4
Tools
read from the server
244 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 12

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 September 2026. No other catalogue keeps this.

31 Oct 4 tool descriptions were rewritten5 times that day dry_run_simulation, execute_onchain_intent, get_smart_account_info and 1 more
31 Oct a tool changed the parameters it asks for2 times that day execute_onchain_intent
31 Oct a tool changed version
14 Sep 4 tool descriptions were rewritten dry_run_simulation, execute_onchain_intent, get_smart_account_info and 1 more
and 2 more, back to 14 September 2026

What the code does

We have not read this server's code yet, 55 d ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Touches key and credential files Dockerfile:4, Dockerfile.fastify:4
COPY package.json package-lock.json* .npmrc* ./
Sends data to a third-party sink monitoring/alertmanager.yml:14
      - url: "https://discord.com/api/webhooks/YOUR_WEBHOOK_URL/slack"

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add gateway --transport http https://api.agentexec.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.agentexec.dev/mcp
~/.codex/config.toml
[mcp_servers.gateway]
url = "https://api.agentexec.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "gateway": {
      "url": "https://api.agentexec.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "gateway": {
      "type": "http",
      "url": "https://api.agentexec.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

dry
dry_run_simulation
Simulates a transaction without broadcasting: on Tenderly when the operator has it enabled (gas and balance changes), otherwise an RPC gas estimate only. Works without an API key (rate-limited per client) unless the operator disables public simulation.
execute
execute_onchain_intent
Simulates and executes a gasless, sponsored Web3 transaction on Base L2 (e.g. token swaps, transfers) against operator-allowlisted targets. Simulates before broadcasting: Tenderly when the operator has it enabled, otherwise an RPC gas estimate plus a USDC amount cap. Requires an API key. When the operator charges for execution, the first call returns the x402 USDC payment requirements; sign that EIP-3009 authorization locally (never send a private key) and call again with paymentSignature. Payment settles only after the target and simulation checks pass, and only for the exact price.
issue
issue_session_key
Issue a scoped session key (time limit, USDC spend cap, target whitelist) enforced by the gateway; ZeroDev on-chain permissions only when the operator configures them. Requires an API key.
smart
get_smart_account_info
Retrieves the Agent Owner EOA address and Safe Smart Wallet address on Base, and whether the Safe is deployed. Works without an API key.

Endpoints

URLTransportStateLatencyChecked
https://api.agentexec.dev/mcp streamable-http answering 230 ms 13 min ago

Alternatives to AgentExec WebMCP & Base L2 Gateway

same job, measured the same way
ActionGate
by actiongate-api

Pre-execution safety layer for autonomous agent wallets via MCP and x402.

6 tools answering
PayGate MCP — Monetization Gateway for AI Agents
by geoacpfilho

Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.

6 tools answering
Rocketsloth
by rocketsloth

Website monetization for AI agents: apply, integrate ads, reporting, and payouts — all over MCP.

14 tools answering
Hive Swap
by srotzin

Cross-chain token swaps for autonomous agents on Base L2 and partner rails

1 tools answering
x402-market
by asaishota

Let AI agents pay-per-call for any HTTP API via x402 on Base mainnet. One tool: pay_and_call.

63 installs/wk local only
QAE Safety Certification
by tb8412

Deterministic pre-execution safety certification for autonomous AI agents.

30 installs/wk local only
Teardrop
by hasavage

Teardrop MCP gateway: paid tools for autonomous agents (x402, credits).

36 tools answering
402shield
by mitchsingh

x402 payment security and pre-execution transaction risk screening for autonomous AI agents.

1 tools answering

AgentExec WebMCP & Base L2 Gateway — questions

Answers built from our own checks of this server.

What can AgentExec WebMCP & Base L2 Gateway do?
It exposes 4 tools, read directly from the server on our last check. Among them: dry_run_simulation, execute_onchain_intent, get_smart_account_info, issue_session_key. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AgentExec WebMCP & Base L2 Gateway working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 244 ms. The bar chart above shows every period we have measured.
Is AgentExec WebMCP & Base L2 Gateway still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect AgentExec WebMCP & Base L2 Gateway?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AgentExec WebMCP & Base L2 Gateway need an API key?
No. AgentExec WebMCP & Base L2 Gateway completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AgentExec WebMCP & Base L2 Gateway?
It answers our handshake in 244 ms on average, which is faster than 58% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.