Execute cleancode-ai-mcp

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

Premium agentic endpoint for cleancode-ai-mcp.

VerifiedSSEWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint for cleancode-ai-mcp, described only as a premium agentic endpoint, paid per call in USDC on Base Mainnet.

What you can do
  • The listing provides no tool list, instructions or README, so the assistant-facing capabilities cannot be described.
  • The only documented behaviour is access control: each request must carry a payment signature header for x402 V2 settlement.
  • No other functions, data sources or outputs are stated.
When to use it
Only worth considering if you already know what cleancode-ai-mcp offers and are prepared to pay per request in USDC on Base Mainnet. Without a tool list or documentation, there is little basis to add it.
Requirements
A remote SSE endpoint at api.m2mcent.com; no local package or runtime. A Payment-Signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet. A funded Base Mainnet wallet able to sign such authorizations, and network access.
Before you install
Every call is paid: the header settles $0.05 USDC per request on Base Mainnet, so usage spends real funds. The header carries a cryptographic payment signature from your wallet; treat it as a secret and check what the endpoint does with it. No tools, documentation or privacy terms are published, so the data sent to this third-party service is unverified.

Installation

In SourceWeft

  1. Open Execute cleancode-ai-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%2Fcleancode-ai-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-cleancode-ai": {
      "type": "sse",
      "url": "https://api.m2mcent.com/cleancode-ai-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.