Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/one-search-mcp/issues.md or /mcp/one-search-mcp/issues.json, or Pod over MCP.

Reported issues for one-search-mcp

Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to one-search-mcp.

Most discussed

SearchSchema 能否加入指定搜索引擎的参数engines

SearchSchema 能不能加入指定搜索引擎的参数engines ，看local.ts是支持索引擎的参数engines ，SearchSchema 不支持的话没办法指定

Read the thread · 2026-08-25 · open · external user · 0 comments

DuckDuckGo safeSearch mapping inverted vs documented 0=off/1=moderate/2=strict

Problem

DuckDuckGo safeSearch value is inverted relative to the documented semantics.

Cite

src/interface.ts:17-18 documents:

// 0: off, 1: moderate, 2: strict
safeSearch?: 0 | 1 | 2;

src/search/process-search.ts:94 maps in the opposite order:

const safeSearchOptions = [SafeSearchType.STRICT, SafeSearchType.MODERATE, SafeSearchType.OFF];
...
safeSearch: safeSearchOptions[safeSearch],

Steps

  1. `SEARCH_PROVIDER=duckduckgo SAFE_SEARCH=0 npx one-searc

Read the thread · 2026-07-04 · open · external user · 0 comments

searxng无法使用，提示SearxNG API URL is required

从1.1.3版本开始，searxng这个provider就无法使用，不管是否配置SEARCH_API_URL，都提示SearxNG API URL is required。

看源码发现processSearch中searxng的实现没有传递apiUrl下去。

Read the thread · 2026-04-13 · open · external user · 1 comment

openclaw-gateway accumulates leftover child processes (chrome/python) and memory growth when web search MCP tools are enabled

Summary

On the host, openclaw-gateway shows repeated restarts and repeated leftover process warnings after shutdown/ restart, with child processes like chrome/python3 persisting in the service control group. This appears correlated with search/web tooling enabled in the one-search MCP path and results in memory growth over time (not immediate OOM, but upward drift).

Environment

Read the thread · 2026-03-13 · open · external user · 1 comment

Security Issue: Hardcoded API Key Found in Repository

Hi,

I found a hardcoded secret in your repository. This may expose sensitive credentials or allow unauthorized access to external services.

Location: yokingma-one-search-mcp-main/one-search-mcp-main/deploy/searxng/settings.yml

Type: Default API Key

Description: The settings.yml configuration file contains a hardcoded string under the key secret_key, which appears to be used for access control in a Google Apps Script project. Although it may be intended as a default example, its presence in a

Read the thread · 2025-06-09 · closed · external user · 0 comments

Glama listing is missing Dockerfile

Your MCP server is currently listed on the Glama MCP directory, but it is not available for others to use because it does not have a Dockerfile.

It takes only a few minutes to fix this:

  1. Go to your server's listing: yokingma/one-search-mcp
  2. Click "Claim" to verify ownership.
  3. Once claimed, navigate to the [admin Dockerfile page](https://glama.ai/mcp/servers/yokingma/one-searc

Read the thread · 2025-04-22 · closed · external user · 1 comment

failed to run

D:\AI\agents>bunx one-search-mcp --force error: No version matching "^0.0.2-beta.0" found for specifier "@agent-infra/logger" (but package exists) error: @agent-infra/logger@^0.0.2-beta.0 failed to resolve

D:\AI\agents>npx -y one-search-mcp npm error code ETARGET npm error notarget No matching version found for @agent-infra/logger@^0.0.2-beta.0. npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A co

Read the thread · 2025-04-04 · closed · external user · 1 comment

Most recent

The remaining reports are on the project's issue tracker.