150,000+ agents registered. Trust scores show their math.Explore →
Explorer/MCP/anysearch-ai/anysearch
REMOTE

AnySearch

anysearch-ai/anysearch

Unified real-time search engine skill for AI agents.

4 tools available
The Newcomer
Hasn't been around long. Nothing caught our attention, but there isn't much history to go on yet.
Time indexed (12d)
4toolsRemote/ HTTP12dindexed
100% uptime · 270ms avgChecked May 20, 2026
Quality Score
33/95
Emerging
Risk Score
0/100
Clean
How is this calculated?
Quality Breakdown
Tenure7/20
12 days indexed
Capability15.6/25
Tools: 3.6/13 (4 tools)
Description: 5/5
Endpoint: 7/7
Adoption0/25
Use count: 0/20 (0 uses)
Multi-registry: 0/5 (1 registry)
Reliability10/25
Currently live: 10/10
Uptime history: 0/15 No checks yet
Security scan: 0 pts in v1.0; ready to weight when coverage improves
Incomplete Data Cap (60)
Usage data is not available for this server. Quality is capped until adoption can be measured.
Risk
0Clean
No signals detected.
The scanner shows
4 tools. Nothing caught our attention.
First indexed May 7, 2026
Server Profile
Tools catalogued
4
4 tools available. Full list below.
Hosting
Remote / HTTP
Runs on the internet. No access to your filesystem, SSH keys, or environment variables.
Registry presence
Not verified
Not yet verified by the Official MCP Registry.
Liveness
100%
Based on 24 checks. Average response: 270ms.
Publisher Verification
Not yet verified by the Official MCP Registry.
Endpoint
https://anysearch.run.tools
Tools (4)
batch_search
Run multiple searches in parallel and return all results merged into one response. ## When to use Use batch_search instead of multiple sequential search calls when you have 2–5 independent queries. This saves context window space by returning all results in a single tool call. ## Constraints - Maximum 5 queries per call - Each query item has the same structure as the search tool parameters - Queries run in parallel; a single query failure does not block others ## Example Instead of: search(query=A) → search(query=B) → search(query=C) Use: batch_search(queries=[{query:A,...}, {query:B,...}, {query:C,...}])
extract
Fetch a URL and return its full content as clean Markdown. ## When to use — call extract after search whenever: - The search snippet is too short or truncated to answer the question - User asks to 'read', 'open', 'summarize', or 'get details from' a specific URL - You need to verify a specific claim, statistic, or fact from the original source - The result points to a full article, report, documentation page, or paper worth reading in full - The answer requires data visible only in the page body (tables, sections, code blocks not captured in snippet) - User provides a URL directly and asks about its content ## When NOT to use - The search snippet already contains a complete, sufficient answer - You only need the URL or title (not the page body) ## Constraints - url must start with http:// or https:// - Only HTML pages are supported; PDF/binary files will return an error - Content is truncated at 50,000 characters
list_domains
Call this before search to get the sub-domain catalog and MANDATORY query format rules for a given domain. ## When to call — pick the domain that matches what the user is asking about: finance → stocks, ticker, ETF, forex, exchange rate, currency, commodities, oil/gold price, crypto, Bitcoin, earnings, SEC filing, IPO, bond yield, financial news academic → paper, research, journal, thesis, citation, DOI, abstract, peer review, arxiv, pubmed, scholar, literature, study, dataset ip → patent, prior art, invention, CPC, IPC, EPO, WIPO, assignee, inventor, trademark legal → law, statute, regulation, case, ruling, judgment, court, legislation, compliance, civil code, criminal code travel → flight, airline, departure, arrival, delay, airport, IATA, POI, attraction, hotel, itinerary, travel guide, visa gaming → game, Steam, price, discount, esports, player stats, rank, champion, LOL, DOTA, CS2 security → malware, virus, CVE, vulnerability, IP reputation, threat, IOC, hash, VirusTotal, OSINT, phishing, ransomware geo → address, coordinates, geocode, POI, nearby, restaurant, walkability, transit score environment → weather, forecast, AQI, air quality, PM2.5, satellite, NDVI, carbon, emission, agriculture energy → electricity price, power grid, oil price, gas price, energy market business → job, hiring, salary, company contact, B2B, lead, recruiter, HR code → library docs, API reference, npm, pip, cargo, code snippet, function, repo search health → clinical trial, diagnosis, drug, symptom, medical literature, WHO stats, psychology education → course, lecture, textbook, tutorial video, MOOC, open courseware tech → product specs, barcode, HackerNews, ProductHunt, tech review ecommerce → price comparison, Walmart, shopping, product search film → movie, TV show, anime, torrent, streaming music → album, artist, lyrics, music torrent fashion → cosmetics ingredients, beauty, trend, streetwear release home → recipe, repair guide, food safety, walkability, appliance religion → bible, quran, torah, buddhist texts, manuscripts ugc → Bilibili video, YouTube video ## Returns Markdown table filtered to the specified domain: sub_domain | description | query_format | zone ## CRITICAL: How to use results - sub_domain is the PRIMARY routing key — always pass it to search - query_format column is MANDATORY — wrong format = wrong data source = wrong results Hard constraints examples: finance.us_stock requires Stock:/Forex:/News:/Commodities: prefix; security.noise requires single IPv4; geo.weather requires city name or lat,lon - If multiple sub_domains match different aspects, make PARALLEL search calls — one per sub_domain - zone=CN → set zone="cn" in search; zone=ALL/US/EU → omit zone ## Cache Rule — NEVER repeat list_domains for the same domain Once you have called list_domains for a domain in this conversation, the result is valid for the ENTIRE session. Do NOT call list_domains again for the same domain — reuse the sub_domain and query format you already received. If you need info for multiple domains, pass them all in the domains array in a single call.
search
Execute a search and return ranked Markdown results (title, URL, snippet). ## Two modes ### Mode 1 — General web search (no list_domains needed) Omit domain and sub_domain entirely. Use when the query is open-ended and does not target a specific structured data source. Example: search(query="what is quantum computing") ### Mode 2 — Vertical search (call list_domains first) Use when the query targets a specific domain: stocks, patents, flights, CVEs, weather, academic papers, etc. Steps: 1. Call list_domains to get the sub_domain and mandatory query format for the target domain. 2. Pass domain + sub_domain from list_domains output. Never guess them. 3. Format query exactly as specified in the query_format column — wrong format = wrong results. ## Decision rule — which mode to use Use Mode 2 (vertical) when ANY of these apply: - Query involves a ticker, DOI, CVE, IATA code, patent number, address, or other structured identifier - Query targets a specific vertical: finance, legal, academic, travel, security, geo, environment, etc. - User asks for real-time or specialized data (stock price, weather, flight status, drug info, etc.) Use Mode 1 (general) when the query is purely conversational or open-ended with no structured lookup. ## After getting results — when to call extract Search returns titles + snippets only. Call extract when: - The snippet is truncated or insufficient to answer the question - User asks to read, summarize, or get details from a specific URL - You need to verify a claim or fact from the source page - The answer requires data only visible in the page body (tables, sections not in snippet) ## Query decomposition One intent per search call. For 2–5 independent queries use batch_search instead. WRONG: search(query="AAPL price and earnings and analyst rating") RIGHT: batch_search(queries=[{query:"AAPL price",...}, {query:"AAPL earnings",...}])

Is this your server?

Create a free RNWY account to connect your on-chain identity to this server. MCP server claiming is coming; register now and you'll be first in line.

Create your account →
More from anysearch-ai
AnySearch
Unified real-time search engine skill for AI agents.
Similar servers
ai.autoblocks/contextlayer-mcp
Personal context management for AI assistants
Akebono MCP
Provides scored and reasoned Kyoto temple data optimized for AI travel agents to deliver personalized recommendations based on natural language queries. It enables agents to retrieve detailed temple information including historical significance, pricing, and crowd levels.
adver-optimizer-prod
keris_edumcp
qingxi
Fodda Knowledge Graphs
Expert-curated knowledge graphs for AI agents — PSFK Retail, Beauty, Sports and more.
Indexed from Smithery · Updates nightlyView on Smithery →