
Execute delegatecall-vulnerability-mcp
io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026
Premium agentic endpoint for delegatecall-vulnerability-mcp.
Overview
A remote MCP endpoint for delegatecall-vulnerability-mcp that requires a per-call USDC payment signature on Base Mainnet.
- What you can do
- The listing gives no tool list, so the assistant-facing capabilities are not documented beyond the server's name and premium endpoint framing. The name suggests delegatecall vulnerability analysis, but no tools, inputs or outputs are described. Access is gated by a payment signature supplied in a request header.
- When to use it
- Only worth considering if you specifically need a paid, hosted endpoint for delegatecall vulnerability work and are prepared to pay per call in USDC on Base Mainnet. With no documented tools or instructions, it is hard to judge fitness for any task.
- Requirements
- A remote SSE endpoint at api.m2mcent.com. No account or API key is declared, but each request needs a Payment-Signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, costing $0.35 USDC. A funded Base Mainnet wallet capable of signing such authorizations is implied.
Installation
In SourceWeft
- Open Execute delegatecall-vulnerability-mcp in the dashboard and add it to a workspace.
- 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%2Fdelegatecall-vulnerability-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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"execute-delegatecall-vulnerability": {
"type": "sse",
"url": "https://api.m2mcent.com/delegatecall-vulnerability-mcp/sse"
}
}
}Tools
0Version history
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.