A remote pay-per-call service giving an assistant fresh web search, keyword trend comparison, and watched public-page change checks.
What you can do
Search the fresh public web and get organic results with source URLs, priced per successful call via x402 payment. Compare keyword trend signals from a normalized supplier dataset. Check a public page for changes against a watched baseline, with retrieval evidence. Each product is billed per successful purchase rather than by subscription.
When to use it
Useful when an assistant needs current web results, keyword trend comparisons, or monitoring of a specific public page for changes, and you are willing to pay a small per-call fee. Less suited if you need free access or a subscription-based quota.
Requirements
A remote streamable HTTP endpoint; no local runtime, account, API key, or headers are declared. Calls are paid per successful purchase through x402, so a payment-capable client or wallet arrangement is needed. Network access to the endpoint is required.
Before you install
Each successful call costs money: $0.002 for change-check and $0.01 each for keyword-trends and web-search, so automated or repeated use can accumulate spending. Trend data is normalized supplier data, not Google Trends. Page checks and searches send the requested URLs and queries to a third-party service.
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/io.github.despiteryan%2Fagentwholesale/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.
Check a public page for watched changes Canonical product ID: change-check. Price: $0.002 USD per successful x402 purchase. Freshness: Fetched at request time. Provenance: Direct public HTTPS page retrieval with watched baseline evidence. Reliability: 72-hour live drift gate completed with 100% sentinel availability and zero sentinel misses across 1,168 checks. Repeat capability: Reuse the same URL and field baselines to refresh the check incrementally.
Parametersurlrequiredfieldsrequired
keyword-trends
Compare keyword trend signals
Compare keyword trend signals Canonical product ID: keyword-trends. Price: $0.01 USD per successful x402 purchase. Freshness: Current supplier dataset at request time. Provenance: Normalized supplier trend data; not Google Trends. Reliability: Production x402 product with QA and smoke coverage. Repeat capability: Reuse keywords and country to refresh the trend window.
Parameterscountryrequiredkeywordsrequired
web-search
Search the fresh public web
Search the fresh public web Canonical product ID: web-search. Price: $0.01 USD per successful x402 purchase. Freshness: Fresh search at request time. Provenance: Normalized organic web-search results with source URLs. Reliability: Production x402 endpoint backed by the shared search supplier path. Repeat capability: Reuse or refine the query, country, and limit for follow-up searches.
Parameterslimitqueryrequiredcountry
Version history
1
v1.0.0LatestSep 16, 2026
Score
83%
83% 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
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.