io.github.cleanyield-data/clean-yield
Clean Yield Data Tools
Is the Clean Yield Data Tools MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Company enrichment, FMCSA carriers, app reviews, live ATS jobs and LatAm public tenders, via Apify.
needs auth probed 2026-11-15 · unchanged since 2026-11-14 · HTTP 401 · Bearer
The server needs auth, so these tool definitions were read from the publisher's open-source package npm:clean-yield-mcp, started in a container with placeholder values and the network off, on 2026-11-15. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Missing or invalid access token. Pass an Apify API token in the - Endpoint
- https://mcp.apify.com/?tools=cleanyield/company-enrichment-from-website,cleanyield/fmcsa-carrier-data,cleanyield/app-store-google-play-reviews,cleanyield/ats-jobs-scraper,cleanyield/latam-public-tenders (streamable-http)
- Host
- mcp.apify.com
- Of a 1M window
- 3.0 % of a 1M context window
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.apify.com/?tools=cleanyield/company-enrichment-from-website,cleanyield/fmcsa-carrier-data,cleanyield/app-store-google-play-reviews,cleanyield/ats-jobs-scraper,cleanyield/latam-public-tenders registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server console-backend.apify.com, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes full_api_access.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/cleanyield-data/clean-yield-mcp
- Website
- https://apify.com/cleanyield
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Other registry entries on mcp.apify.com, the ones next to this name; all of them.
- Podcast Transcript API io.github.catalyst-labs-dev/podcast-transcript-api · needs auth
- Website Screenshot & PDF API io.github.catalyst-labs-dev/website-screenshot-pdf-api · needs auth
- Website Tech Stack Lookup io.github.catalyst-labs-dev/website-tech-stack-lookup · needs auth
- YouTube Transcript API io.github.catalyst-labs-dev/youtube-transcript-api · needs auth
- Korean Retail Data (Daiso, Musinsa) io.github.cocomoon612/korea-retail-data · needs auth
- Naver Search, Map & Blog Data io.github.cocomoon612/naver-korea-search · needs auth
- Olive Young K-Beauty Data io.github.cocomoon612/olive-young-kbeauty · not probed
- Airbnb Host Portfolio io.github.corent1robert/airbnb-host-portfolio · needs auth
Servers that mention clean.
- CleanVector ai.cleanvector/cleanvector · alive
- file2markdown ai.file2markdown/file2markdown · alive
- Keenable Web Search ai.keenable/web-search · alive
- Servana ai.servana/servana · alive
- String Web Access ai.usestring/web-access · alive
- ai.smithery/arjunkmrm-scrapermcp_el · not found
- Cleanor app.cleanor/cleanor · alive
- Stringer CleanExtract app.getstringer/cleanextract · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.