io.github.iridite/bing-search-free

MCPcommunity
v0.2.0io.github.iriditeUnknownUpdated 7mo agoGitHub

Free Bing search MCP server - No API key required

免费的 Bing 搜索 MCP 服务器,通过抓取 Bing 搜索结果提供搜索功能。无需 API key,完全免费! 🆓 完全免费 - 无需 Bing API key,无需付费订阅 🌍 智能语言检测 - 自动识别中英文查询,选择最佳搜索引擎 🚀 即开即用 - 一行命令安装,无需复杂配置 🔧 灵活配置 - 支持自定义结果数量(1-50)、语言偏好 💪 健壮可靠 - 完善的错误处理、超时机制和重试逻辑 📦 标准 MCP 协议 - 兼容所有 MCP 客户端(Claude Desktop、Claude Code、Cursor 等) 🎯 精准解析 - 返回标题、URL 和摘要,格式化输出 特性 | mcp-bing-scraper (本项目) | bing-search-mcp | 其他搜索 MCP |…

source link failingno successful check on record
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 →
7mo agoLast update
Package
Authorio.github.iridite
LicenseUnknown
Version0.2.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv0.2.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

No tool declarations found in the source3mo ago

Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

免费的 Bing 搜索 MCP 服务器,通过抓取 Bing 搜索结果提供搜索功能。无需 API key,完全免费! 🆓 完全免费 - 无需 Bing API key,无需付费订阅 🌍 智能语言检测 - 自动识别中英文查询,选择最佳搜索引擎 🚀 即开即用 - 一行命令安装,无需复杂配置 🔧 灵活配置 - 支持自定义结果数量(1-50)、语言偏好 💪 健壮可靠 - 完善的错误处理、超时机制和重试逻辑 📦 标准 MCP 协议 - 兼容所有 MCP 客户端(Claude Desktop、Claude Code、Cursor 等) 🎯 精准解析 - 返回标题、URL 和摘要,格式化输出 特性 | mcp-bing-scraper (本项目) | bing-search-mcp | 其他搜索 MCP | ------|---------------------------|-----------------|--------------| 💰 费用 | 完全免费 | 需要 Bing API Key (付费) | 大多需要 API Key | 🔑 API Key | 不需要 |…

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