Where it fits
Readers checking what the retired ProofFetch Lite tunnel exposed; it cannot be installed.
- Fetch a URL and receive its status, final URL, title, markdown, and SHA-256 receipt.
- Clean extracted web content into markdown for downstream processing.
- Watch a URL and detect changes between checks.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with ProofFetch Lite (ProofFetch, ReadClean, UrlWatch)
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Researches what people actually say about any topic in the last 30 days. It pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub and the web. A doctor health check diagnoses broken or missing sources.
Submits a product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Use when the user mentions 'directory submissions,' 'submit to directories,' 'backlinks from directories,' 'list my product,' 'submit to Product Hunt,' 'BetaList,' 'TAAFT,' 'Futurepedia,' 'G2 listing,' 'Capterra listing,' 'AlternativeTo,' 'SaaSHub,' 'AI directories,' 'MCP registry,' 'publish my MCP server,' 'awesome list,' 'llms.txt directory,' 'Claude plugin directory,' 'agent directory,' 'dofollow backlinks,' or 'launch directories.'
Creates SEO-driven pages at scale using templates and data. Use when the user mentions 'programmatic SEO,' 'template pages,' 'pages at scale,' 'directory pages,' 'location pages,' '[keyword] + [city] pages,' 'comparison pages,' 'integration pages,' 'building many pages for SEO,' 'pSEO,' 'generate 100 pages,' 'data-driven pages,' 'templated landing pages,' or 'which CMS for pSEO.' Use it when someone wants many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit.
No skills found
Try a different search term or clear the filters.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The server connects but no tools appear. Confirm the URL and transport, then restart the client.
- The first tool call times out. Try a smaller request and check the provider's status or rate limits.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
ProofFetch Lite (ProofFetch, ReadClean, UrlWatch) documentationhttps://favor-skilled-ben-plugin.trycloudflare.com/llms.txt