
Base MCP Resolver
io.github.thgun2yerhedPublished by GitHub account thgun2yerhedv2.0.0Updated Oct 24, 2026
Free onboarding tool providing authentic live transaction analysis on Base mainnet.
Overview
Remote MCP gateway that claims to give agents live transaction signals from the Base Layer 2 mainnet, with no tools or usage details documented.
- What you can do
- The listing names no tools, so capabilities can only be inferred from the description and README.
- It presents itself as a free gateway delivering real-time signals intelligence and live transaction analysis from the Base mainnet.
- It describes JSON-RPC 2.0 MCP primitives, a discovery card endpoint and a telemetry stream endpoint.
- It says it routes through a dedicated Alchemy mainnet connection.
- When to use it
- Only worth trying if you want an agent to read live Base mainnet transaction signals and are willing to test an undocumented, unauthenticated remote endpoint first. Most users should wait for a published tool list and usage examples.
- Requirements
- A remote MCP endpoint over SSE at the provider's hosted address; nothing to install locally. No authentication, environment variables or headers are declared. Network access to the provider's host is required, and the README mentions an Alchemy mainnet connection on the provider side.
Installation
In SourceWeft
- Open Base MCP Resolver 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.thgun2yerhed%2Fbase-mcp-resolver/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": {
"base-resolver": {
"type": "sse",
"url": "https://agent-services-seven.vercel.app/api/gateway"
}
}
}README
Base Commerce Signals Gateway
Free API gateway providing real-time signals intelligence to autonomous software agents within the Base Layer 2 commerce layer.
Architecture & Integration Specs
- Protocol Standard: Model Context Protocol (MCP) compliant JSON-RPC 2.0 primitives.
- Network Infrastructure: High-throughput Base Layer 2 live ledger routing.
- Node Infrastructure: Dedicated Alchemy mainnet connection framework.
Gateway Core Endpoints
- Discovery Card:
/.well-known/mcp/server-card.json - Telemetry Stream:
/api/gateway
Source: README.md at commit de2b91c
Tools
0Version history
1- v2.0.0LatestSep 16, 2026
Score
75% 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
- License10 pts
Declare a license in the repository or the registry entry.