aiworker-data
org.duckdns.aiworkerPublished by aiworker.duckdns.orgOfficial publisherv0.2.0Updated Oct 24, 2026
Paid x402 tools (USDC per call): defi_yields, defi_protocol, scrape_markdown, scrape_summary.
Overview
Remote MCP endpoint offering paid, per-call DeFi data and web scraping tools billed in USDC via x402.
- What you can do
- Look up DeFi yield opportunities and protocol details
- Fetch a web page and return it as markdown
- Produce a summary of a scraped page
- Each tool call is billed in USDC through the x402 payment scheme
- When to use it
- When an assistant needs quick DeFi yield or protocol lookups, or wants a page converted to markdown or summarized, and you are willing to pay per call in USDC rather than run your own scraping or data pipeline.
- Requirements
- A remote MCP client connecting over streamable HTTP to the provider's endpoint. No API key or environment variables are declared; payment is expected per call in USDC via x402, so a funded wallet or x402-capable client is needed. Network access to the provider's host.
Installation
In SourceWeft
- Open aiworker-data 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/org.duckdns.aiworker%2Faiworker-data/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": {
"aiworker-data": {
"type": "http",
"url": "https://aiworker.duckdns.org/mcp"
}
}
}Tools
0Version history
1- v0.2.0LatestSep 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.