Execute api-rate-limit-enforcer-mcp

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

Premium agentic endpoint for api-rate-limit-enforcer-mcp.

VerifiedSSEWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP endpoint for api-rate-limit-enforcer-mcp that requires a paid x402 payment signature header before use.

What you can do
The listing provides no tool list, so the assistant-facing capabilities cannot be described beyond the name: an endpoint related to API rate-limit enforcement, reached over SSE at a hosted address. Access is gated by a payment signature header rather than by a conventional account or API key.
When to use it
Only worth considering if you specifically need a hosted endpoint for API rate-limit enforcement and are prepared to pay per use in USDC on Base Mainnet. Most users have no reason to add it, since no tools or documentation are published.
Requirements
A remote SSE endpoint; no local runtime or package. A Payment-Signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, priced at $0.18 USDC per the manifest. A wallet able to sign such authorizations is implied.
Before you install
Using it means spending real money: each request is settled in USDC on Base Mainnet via the Payment-Signature header, so a misconfigured client could incur charges. The signature is a payment credential and should be treated as sensitive. No tools, README or instructions are published, so what the endpoint does with your requests is unverified.

Installation

In SourceWeft

  1. Open Execute api-rate-limit-enforcer-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-rate-limit-enforcer-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-rate-limit-enforcer": {
      "type": "sse",
      "url": "https://api.m2mcent.com/api-rate-limit-enforcer-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.