rainmaker-gateway
dev.workers.mmelnyk2000.rainmaker-gatewayPublished by rainmaker-gateway.mmelnyk2000.workers.devOfficial publisherv1.0.0Updated Oct 24, 2026
Free list of Rainmaker tools + paid need-to-tool router. x402 $0.005 USDC, Base. As is, no warranty.
Overview
A remote MCP endpoint that lists Rainmaker tools and routes paid tool requests, charging $0.005 USDC per call on Base.
- What you can do
- According to its registry description, this server provides a free list of Rainmaker tools plus a paid need-to-tool router. Payment is described as x402 at $0.005 USDC on Base. No individual tools are listed in the manifest, so the exact capabilities are not documented here.
- When to use it
- Consider it only if you specifically want to discover Rainmaker tools or route requests to them through a hosted endpoint. Because the tool list is not published, it is hard to judge usefulness in advance; most users would need more documentation before adding it.
- Requirements
- A remote streamable HTTP endpoint at the provider's workers.dev address; no package, environment variables, headers, or authentication are declared. Using the paid router requires paying $0.005 USDC per call on Base, so a compatible wallet and funds are needed.
Installation
In SourceWeft
- Open rainmaker-gateway in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. 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/dev.workers.mmelnyk2000.rainmaker-gateway%2Fgateway/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": {
"rainmaker-gateway": {
"type": "http",
"url": "https://rainmaker-gateway.mmelnyk2000.workers.dev/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 16, 2026
Score
17% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- 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.