Execute automation-weaver-mcp

io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026

Premium agentic endpoint for automation-weaver-mcp.

VerifiedSSEWeb executable

Overview

AI-generated overview

Remote MCP endpoint for automation-weaver-mcp, a paid agentic service that requires an x402 USDC payment signature on Base Mainnet.

What you can do
  • Connects an assistant to a hosted automation-weaver-mcp endpoint over SSE.
  • The registry lists no tools, so the specific actions available are not documented.
  • Access is gated by a per-call payment signature rather than an account login.
When to use it
Only worth adding if you already know what automation-weaver-mcp offers and are prepared to pay per use in USDC on Base Mainnet; otherwise there is too little public detail to judge it.
Requirements
A remote SSE endpoint at api.m2mcent.com, reachable over the network. A crypto wallet able to sign EIP-3009 TransferWithAuthorization messages on Base Mainnet, with USDC available, since each request carries a Payment-Signature header for a $0.05 USDC settlement.
Before you install
Every request requires a wallet signature authorizing a USDC transfer, so using it spends real money and exposes a payment signature to the endpoint. No tools, documentation or README are published, so what the server does with your data is unknown. Treat the payment header as a secret and set spending limits.

Installation

In SourceWeft

  1. Open Execute automation-weaver-mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fautomation-weaver-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "execute-automation-weaver": {
      "type": "sse",
      "url": "https://api.m2mcent.com/automation-weaver-mcp/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.