io.github.projectworks007/ai-agent-web-tools
Web Tools for AI Agents
Is the Web Tools for AI Agents MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Web tools for AI agents: URL to clean Markdown, site crawl, screenshots, PDF/Office to text, OCR.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
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=highbrow_fame/web-fetch-api,highbrow_fame/website-screenshot-api,highbrow_fame/pdf-to-markdown-api,highbrow_fame/markdown-site-crawler,highbrow_fame/url-to-markdown-api,highbrow_fame/url-status-checker-api,highbrow_fame/ocr-api,highbrow_fame/office-document-to-text-api,highbrow_fame/seo-audit-api (streamable-http)
- Host
- mcp.apify.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.apify.com/?tools=highbrow_fame/web-fetch-api,highbrow_fame/website-screenshot-api,highbrow_fame/pdf-to-markdown-api,highbrow_fame/markdown-site-crawler,highbrow_fame/url-to-markdown-api,highbrow_fame/url-status-checker-api,highbrow_fame/ocr-api,highbrow_fame/office-document-to-text-api,highbrow_fame/seo-audit-api 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/projectworks007/apify-data-mcp
- Website
- https://github.com/projectworks007/apify-data-mcp#ai-agent-web-tools
- Registry
- active, updated 2026-10-22 · 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.
- io.github.pavel-tashev/email-verifier · needs auth
- io.github.pavel-tashev/rss-feed-reader · needs auth
- io.github.pavel-tashev/sitemap-url-extractor · needs auth
- io.github.pavel-tashev/website-change-watcher · needs auth
- AI Search Brand Visibility io.github.projectworks007/ai-search-visibility · needs auth
- App & Game Store Data io.github.projectworks007/app-store-data · needs auth
- Australia & New Zealand Grocery Prices io.github.projectworks007/au-nz-grocery-prices · not probed
- Company Data io.github.projectworks007/company-data · needs auth
Servers that mention projectworks007.
- E-commerce Product Data io.github.projectworks007/ecommerce-products · needs auth
- Events Data io.github.projectworks007/events-data · needs auth
- Finance & Filings Data io.github.projectworks007/finance-data · needs auth
- Google Maps Business Leads io.github.projectworks007/google-maps-leads · needs auth
- Hotel Prices Data io.github.projectworks007/hotel-prices · needs auth
- Job Boards Data io.github.projectworks007/job-boards · needs auth
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.