DeepSeek Harness Web Search Plugin

Source-traceable Brave + Tavily live web search and URL extraction, packaged as a native DeepSeek Harness plugin.

简体中文 · TaroCub · Security · Releases

This plugin installs one native Harness bundle into the web profile. It adds:

• web_search for routed Brave/Tavily live search;

• web_extract for clean Tavily URL extraction;

• provider_status for local, secret-safe configuration checks;

• health_check for explicit live auth/quota/rate-limit/timeout probes;

• optional /tarocub guidance when the plugin is used with the TaroCub gateway.

It works in plain DeepSeek Harness. TaroCub is optional.

Why This Plugin

Native model search is useful, but research workflows also need a stable tool contract and an inspectable source trail. This plugin returns provider, domain, rank, access time, source logs, extraction hashes, and visible fallback notices instead of hiding provider routing.

When one provider fails, results include fallbacks and notice. Extracted content includes contentHash. If a user gives an exact URL, read or extract that URL first; use search for discovery or background context.

Related MCP server: Multi-Search MCP Server

Architecture

DeepSeek Harness web profile
└── deepseek-harness-web-search-plugin
    ├── deepseek-harness-web-search  bounded search guidance
    └── mcp-cctb-search         @deepseek-ai/dsh-mcp-client
        └── node dist/search-mcp.js
            ├── Brave Search API
            └── Tavily Search + Extract APIs

The committed MCP bundle is self-contained. A Git installation does not need a build step and does not add runtime npm dependencies.

Install

Prerequisites:

• DeepSeek Harness dsh with the web profile;

• Node.js 20 or newer;

• at least one Brave or Tavily key for provider-backed tools.

dsh plugin --profile web add github:cloveric/deepseek-harness-web-search-plugin

Restart Harness after installation. Installing the plugin does not configure provider credentials, create a Feishu/Lark app, or start TaroCub.

Configure Providers

Set one or both credentials in the environment that starts Harness:

export BRAVE_API_KEY="..."
export TAVILY_API_KEY="..."
dsh web

BRAVE_SEARCH_API_KEY is accepted as an alias for BRAVE_API_KEY. Direct process environment values win. For compatibility with an existing local TaroCub/Codex setup, the MCP may read only these same named values from a Codex MCP environment section when direct values are absent.

The plugin never writes keys into a Harness profile, copies them into a workspace, or returns them from provider_status. It performs no provider request until a provider-backed tool or the explicit health_check tool is called.

Verify

Confirm that the bundle contributes exactly one Search MCP client:

dsh --profile web --dump-config | grep -A18 -B2 mcp-cctb-search

In a Harness session, ask it to call mcp__cctb_search__provider_status. This verifies configuration visibility without consuming provider quota. Use mcp__cctb_search__health_check only when you want a real provider probe.

Expected tools:

mcp__cctb_search__web_search
mcp__cctb_search__web_extract
mcp__cctb_search__provider_status
mcp__cctb_search__health_check

Update Or Remove

dsh plugin --profile web update deepseek-harness-web-search-plugin
dsh plugin --profile web remove deepseek-harness-web-search-plugin

Restart Harness after either operation and re-run dsh --profile web --dump-config.

TaroCub Integration

TaroCub is a separate Feishu/Lark-first local agent gateway. Its managed DeepSeek Hosts link the same web profile.

• With the current plugin, TaroCub validates the package capability marker, bundled entrypoint, and Harness patch registration before letting the plugin own mcp-cctb-search.

• Existing tarocub-deepseek-harness-plugin installations remain recognized by TaroCub during migration.

• With no plugin, an older companion-only plugin, or a damaged entrypoint/patch, TaroCub retains its private Search MCP fallback.

• TaroCub sets TAROCUB_SEARCH_MCP_OWNER=plugin or bridge for its private Host so exactly one client is active.

• Plain Harness does not set this internal ownership flag, so the plugin is enabled by default.

Do not set TAROCUB_SEARCH_MCP_OWNER manually in normal Harness use. Plugin installation and TaroCub service deployment are separate operations.

Migration From The Former Package Name

The project was renamed from tarocub-deepseek-harness-plugin to make its web-search purpose explicit. Existing installations continue to work with TaroCub, but do not install both package names in one profile. Migrate once, then use the new name for future updates:

dsh plugin --profile web remove tarocub-deepseek-harness-plugin
dsh plugin --profile web add github:cloveric/deepseek-harness-web-search-plugin
dsh --profile web --dump-config | grep -c "id: mcp-cctb-search"

Restart Harness after migration. The final count must be 1.

The canonical source also remains installable from TaroCub's plugin subdirectory:

dsh plugin --profile web add "github:cloveric/tarocub#path:deepseek-harness-plugin"

Troubleshooting

Scope And Security

This project is an MCP and DeepSeek Harness plugin. It does not proxy model traffic, manage a Feishu/Lark tenant, persist provider credentials, or replace Harness-native plugins/search. Extract accepts only HTTP(S) URLs; all text returned through the MCP boundary is checked for configured provider credentials and common authorization formats. See SECURITY.md for the credential boundary and reporting process.

Development

npm ci
npm run verify

Canonical development happens in deepseek-harness-plugin/ inside TaroCub, then is published to this repository with git subtree. See CONTRIBUTING.md.

License

MIT. See LICENSE.