agent-web-search-mcp

MCPcommunity
v0.7.5io.github.JerryLiu369UnknownUpdated 18d agoGitHub

Provider-neutral web_search for AI agents. Grounding + agent search APIs, keyless defaults.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
18d agoLast update
Reads these credentials
  • ARK_API_KEYAPI keyoptional

    Volcengine Ark API key for Doubao grounding

  • GEMINI_API_KEYAPI keyoptional

    Google Gemini API key for Google Search grounding

  • XAI_API_KEYAPI keyoptional

    xAI API key for Grok web/X search

  • DEEPSEEK_API_KEYAPI keyoptional

    DeepSeek API key for native web search

  • TAVILY_API_KEYAPI keyoptional

    Tavily API key for agent-oriented search

  • BRAVE_SEARCH_API_KEYAPI keyoptional

    Brave Search API key

  • PERPLEXITY_API_KEYAPI keyoptional

    Perplexity API key for structured search

  • YDC_API_KEYAPI keyoptional

    You.com API key

  • EXA_API_KEYAPI keyoptional

    Optional Exa key; free MCP fallback without it

  • PARALLEL_API_KEYAPI keyoptional

    Optional Parallel key; free MCP fallback without it

  • ZHIPU_WEB_SEARCH_API_KEYAPI keyoptional

    Zhipu standalone Web Search API key

  • ZHIPU_CHAT_SEARCH_API_KEYAPI keyoptional

    Zhipu Chat Completions native web search key

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.JerryLiu369
LicenseUnknown
Version0.7.5
Sourcemcp-registry
GitHubJerryLiu369/agent-web-search
SBOMCycloneDX 1.6 ↓
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
—Prompt-injection scan · not run+0/30
→ Not yet scanned — the repository archive is scanned on the next cron run
—Obfuscation / exfil scan · not run+0/20
→ Not yet scanned — the repository archive is scanned on the next cron run
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot runHow well does this scan work?
EvalsNone
IndexedSep 8, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Not scanned yet

Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.

About

Provider-neutral web_search for AI agents. Grounding + agent search APIs, keyless defaults.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.

Topics

Related in search & retrieval