AnySearch MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow provider behavior and search-tool coverage as sources change

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Agents needing real-time web and vertical search plus full-page extraction.

What we know

A remote search MCP for general/vertical search, batch queries and URL-to-Markdown extraction.

Maintenance / activity evidence

Observed Sep 17, 2026 (UTC)Create feature-request.yml

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Search/fetch only within service capabilities.
Optional bearer API key
Sensitive access: Search queries, Requested URLs/page content

Remote search is read-oriented but sends user queries and requested content to the provider.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

1,860 repository stars

Stars observed Oct 6, 2026.

All limitations / Review context

Which search verticals and full-page extraction paths are currently maintained?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Remote search is read-oriented but sends user queries and requested content to the provider.
Search/fetch only within service capabilities.
Optional bearer API key
Queries and fetched URLs/page content go to AnySearch.
Sensitive access: Search queries, Requested URLs/page content
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Anonymous access has lower rate limits.
Queries and fetched URLs are sent to a remote service.

Original activity observations

2026-09-17T10:11:29Z: Create feature-request.yml

Technical identity

github.com/anysearch-ai/anysearch-mcp-server

Exact implementation source: https://github.com/anysearch-ai/anysearch-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: anysearch-ai/anysearch-mcp-server
Service endpoint: https://api.anysearch.com/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
anysearch-ai/anysearch-mcp-server
Recorded repository material and project history.

Setup · Watchlist

Connect remote MCP service

Claude Code

Publisher instructions with a documented client setup path.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Use the publisher-documented command or connection method below; complete the prerequisites and client configuration before expecting a usable MCP connection.
claude mcp add --transport http anysearch https://api.anysearch.com/mcp --scope user --header 'Authorization: Bearer ${ANYSEARCH_API_KEY}' --header 'X-Anysearch-Client: mcp/1.0.0'
Configure / authenticate
Publisher instructions
Use the official remote Streamable HTTP URL https://api.anysearch.com/mcp. API key can be optional; Codex config.toml supports bearer_token_env_var=ANYSEARCH_API_KEY and http_headers X-Anysearch-Client. Do not copy JSON clients formats into Codex TOML as if interchangeable.
Check connection
Suggested check
Publisher directs Codex users to codex mcp list or /mcp inside the Codex TUI to confirm AnySearch server and its tools. An API search may incur provider usage; registration alone does not prove auth or request quota.
Remove / uninstall / revoke
MCP100 setup guide
Remove this registration in the same MCP client and the scope used when it was added, after checking that client configuration; no unqualified removal command is published here. Registration removal does not uninstall software or revoke provider credentials. Client disconnect (claude-code, only if registered using the name `anysearch`): `claude mcp remove anysearch`. This unregisters the client entry; it does not uninstall packages or revoke remote service credentials.

Official Documentation & Sources

What it does

A remote search MCP for general/vertical search, batch queries and URL-to-Markdown extraction.

Capability: Search & Web
Resource type: MCP Server
Best fit: Agents needing real-time web and vertical search plus full-page extraction.

Representative uses

General web search
Finance/academic/security/legal/code vertical search
Parallel batch search
Fetch full-page content

Limitations

Anonymous access has lower rate limits.
Queries and fetched URLs are sent to a remote service.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Optional bearer API key
Permissions: Search/fetch only within service capabilities.
Data handling: Queries and fetched URLs/page content go to AnySearch.
Cost: unknown
Risk and cautions: Remote search is read-oriented but sends user queries and requested content to the provider.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Search queries Requested URLs/page content
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: General web search; Finance/academic/security/legal/code vertical search; Parallel batch search; Fetch full-page content.

What setup and authentication are documented?

Recorded endpoint: https://api.anysearch.com/mcp. Recorded transport: streamable_http. Recorded environment-variable notes: ANYSEARCH_API_KEY. No configuration values are supplied here. Prerequisites: HTTP-capable MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Optional bearer API key; anonymous access supported.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Search/fetch only within service capabilities.

What data-handling boundary should I consider?

Queries and fetched URLs/page content go to AnySearch. Recorded sensitive-access context: Search queries; Requested URLs/page content.

What limitations and risks should I check before use?

Remote search is read-oriented but sends user queries and requested content to the provider. Anonymous access has lower rate limits. Queries and fetched URLs are sent to a remote service. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

AnySearch is listed as First-party MCP in MCP100’s current evidence.