Execute auth-sentinel-mcp

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

Premium agentic endpoint for auth-sentinel-mcp.

VerifiedSSEWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint called auth-sentinel-mcp that requires a per-request payment signature header before it can be used.

What you can do
The listing gives no tool list, so the concrete capabilities are not documented. The only described function is access control: each request must carry a Payment-Signature header, a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet. The registry describes it only as a premium agentic endpoint.
When to use it
Only worth considering if you already know what this endpoint offers and have a wallet setup able to produce x402 payment signatures on Base Mainnet. Without that, there is nothing documented to evaluate.
Requirements
A remote SSE endpoint at api.m2mcent.com; no local package or runtime is needed. Every request needs the Payment-Signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature, which implies a Base Mainnet wallet and x402 V2 client support. No other authentication is declared.
Before you install
Using it spends money: each settlement is $0.05 USDC on Base Mainnet, and the signature authorizes a transfer, so treat the wallet and signing key as sensitive. The tool set is undocumented, so what the endpoint does with your data cannot be verified from this listing.

Installation

In SourceWeft

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