"A guide for reducing token count in AI requests" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Auto-Apply That Ends on an Interview. Job matches, applications sent on the employer's own hiring system, employer-receipt tracking, per-role resumes, cover letters, interview prep.
Narrated demo and tutorial videos of your web app, from a guide or your coding agent.
Google SERP as JSON: organic, AI Overview, People Also Ask, AI Mode, news, shopping. No Cloud setup.
Supplier Reliability: compares supplier snapshots and watches interfaces for material change.
Audit public webpages and supplied markup for HTML, CSS, SEO, JSON-LD, and link issues.
Inspect a public site's tracking signals, grade consent evidence, and get remediation playbooks.
Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions.
Hosted screenshot MCP for AI agents — URL in, image out. No local Chromium.
Screenshot, extract or audit any URL. Paid per call in USDC over x402; free tools need no wallet.
Turn any public website into an MCP server for agents to search, read and navigate.
Give AI assistants secure access to your organization's structured business data. Search records, create and update records, retrieve schema information, and manage workflow states using natural language. You need two values for every request: x-api-key — your Web Data Forms API Key x-group-id — your Web Data Forms Group ID You can find these in your Web Data Forms accounts group->information page. Preferred method: request header When possible, pass the credentials as HTTP headers: x-api-key: <your-api-key> x-group-id: <your-group-id> This is the preferred option because it keeps credentials out of the URL and is more secure. Fallback method: query parameters If your MCP client does not support custom headers, the server also accepts the credentials as URL query parameters. Example: https://mcp.webdataforms.com?x-api-key=abc123&x-group-id=xyz456 Detailed information here: https://github.com/Web-Data-Forms/mcp-server-docs/blob/main/README.md
Agent social posting via your logged-in Chrome. Remote MCP + OAuth. Not clawpost.dev.
All HasData scraping tools in one MCP server: Google, TikTok, Instagram, maps, e-commerce and more.
Unblocked is the context layer for agentic software development.
Kilotest leverages 12 rule engines to test web pages for front-end quality (accessibility, usability, and standards conformity) and report results with specifiable granularity.
Let Claude, Cursor or Cline fetch pages and run Google searches from a real Singapore mobile IP (Singtel/M1). Hosted; free 24-hour trial key.
Read any page or file as clean text, plus live news, weather, market holidays and timezone lookups for agents. Pay-per-call in USDC on Base via x402 — no signup, no API keys.
Timestamped public URL observations with SHA-256 fingerprints, paid in USDC on Base via x402.
Timestamped public URL observations with SHA-256 fingerprints, paid in USDC on Base via x402.
Your agent needs the open web — searched by more than one engine, and read as clean markdown rather than raw HTML. **What you can ask for** • "Search this question with two providers and tell me where they disagree." • "Scrape these 40 URLs into markdown, in one batch." • "Crawl this documentation site and give me every page." • "Do deep research on this topic and cite the sources." • "Find the academic papers behind this claim." **How to use it** Point any MCP client at https://mcp.aisa.one/search/mcp and sign in with OAuth — there is no key to create or paste. 30 tools across several independent providers: Tavily and Exa search, answers, contents and agent runs; Firecrawl scrape, batch scrape, crawl, map and search; Perplexity Sonar, Sonar Pro, reasoning and deep research; Oxylabs AI search and LLM jobs; OpenAI and Anthropic web search; and scholarly search. **Why this rather than the source** Several independent indexes behind one account, because one engine's blind spot is not visible from inside it. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the page here, then ask the same agent who links to it or how much traffic it gets — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo-serp/mcp for the Google results page itself, https://mcp.aisa.one/seo-serp-other-engines/mcp for Bing, Baidu and Naver.
