Execute api-key-load-balancer-mcp

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

Premium agentic endpoint for api-key-load-balancer-mcp.

VerifiedSSEWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint that fronts an API key load balancer and charges per request in USDC on Base.

What you can do
This server is a hosted endpoint at api.m2mcent.com that exposes the api-key-load-balancer-mcp service to an assistant over SSE. The registry entry describes it only as a premium agentic endpoint; no tool list is published, so the concrete operations are not documented here. Access is metered: each request is settled through x402 V2 on Base Mainnet for 0.05 USDC, authorized by a signed payment header.
When to use it
Consider it only if you already know the api-key-load-balancer-mcp service and want an assistant to reach it without running anything locally. It is not a general-purpose tool, and the lack of a published tool list makes it hard to evaluate before trying it.
Requirements
A remote MCP client that supports SSE and can reach over the network. A crypto wallet able to sign EIP-3009 TransferWithAuthorization messages on Base Mainnet, plus USDC balance to cover the 0.05 USDC per-request charge. The Payment-Signature header must be supplied; no environment variables are declared.
Before you install
Every request spends real money: 0.05 USDC per call on Base Mainnet, settled through x402 V2. The Payment-Signature header carries a Base64-encoded EIP-3009 TransferWithAuthorization signature, which authorizes a transfer from your wallet; treat it as a spending credential and never share it. The endpoint is third-party hosted, so requests and any data in them go to that operator, and no tool list or README is published to review first.

Installation

In SourceWeft

  1. Open Execute api-key-load-balancer-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%2Fapi-key-load-balancer-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-api-key-load-balancer": {
      "type": "sse",
      "url": "https://api.m2mcent.com/api-key-load-balancer-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.