DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
E

eagle1-whereis-mcp

Eagle1 Whereis Mcp

适用于 DeepSeek Harness 的 Whereis 货件跟踪:连接 Eagle1 Whereis MCP 服务器,使代理能够查询最新货件状态,并在提供密钥后查询完整跟踪历史。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:eagle1-sys/eagle1-whereis-mcp#d535071ef309faa5f868f01f1abd3db3caa3943b
README兼容性版本

兼容性与来源证明

Eagle1 Whereis Mcp 以 eagle1-whereis-mcp 发布,当前版本为 1.0.2。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/11/4

版本

1.0.2stable
2026/11/4
1.0.1stable
2026/11/3

相关插件

正在加载相关插件…

最新版
1.0.2
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
BSD-3-Clause
发布源
github
GitHub
★ 1
周下载
0
最近提交
2026/11/4
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 integrations-communication 分类下经过校验的插件。

Acp App@deepseek-ai/dsh-acp-appdsh ACP 配置文件包:基于 dsh-base 的仅限自动化的 JSON-RPC stdio 和进程生命周期管理Remote Web Ui@linxin666/dsh-remote-web-ui通过扫码配对访问 dsh Web GUI,共享一个官方界面:设置按钮旁的二维码可将手机和 PC 配对到同一个 Web GUI(手机采用竖屏触控适配层,PC 使用完整桌面界面),通过一次性令牌和 rRemote Bridge@linxin666/dsh-remote-bridgeDSH 远程桥接:主机端通过唯一且精确的 /ios/v1 WebSocket 路由提供协议 v1——会话列表、历史记录基线、提示、包含工具活动的实时回合增量、中断以及进程内代理审批——连接到通过一次性配对的设备Ds Botds-botDS Bot:DeepSeek Harness 的一组长期运行的 Bot,支持主 Bot、Bot 间消息和群聊

README

Whereis Shipment Tracking for DeepSeek Harness

A configuration-only DSH bundle that connects the Eagle1 Whereis MCP server. Once installed, the agent can list carriers, read the latest shipment status, and — with an API key — retrieve full tracking history.

What you get

ToolWhat it doesAPI key
mcp__whereis__list_operatorsResolve fdx / sfex / eg1 carrier codesNo
mcp__whereis__get_latest_statusCurrent status, location, and last scanNo
mcp__whereis__track_shipmentFull event timeline and delivery proofYes

Plus the whereis://reference/status-codes resource.

The bundle points at the hosted endpoint:

https://api.eg1.io/mcp

No API key is needed for the connection itself. Anonymous users get list_operators and get_latest_status; a key unlocks track_shipment.

Requirements

  • DeepSeek Harness >= 0.2.1-rc.5
  • A reachable Whereis MCP endpoint at https://api.eg1.io/mcp
  • An API key only if you want full history

Install

From GitHub (available now)

plugin_manager
  action: install_bundle
  target: git+https://github.com/eagle1-sys/eagle1-whereis-mcp.git#v1.0.2

Pin the tag for a stable version, or replace v1.0.2 with a full commit SHA for an immutable install. If you previously installed a local @local/whereis-mcp, remove it first so the whereis-mcp row is not duplicated.

From the DSH Plugins page (npm, after publishing)

Open Plugins, choose Install, and enter:

eagle1-whereis-mcp

or a pinned version:

eagle1-whereis-mcp@1.0.2

With the plugin manager tool (npm)

plugin_manager
  action: install_bundle
  target: eagle1-whereis-mcp@1.0.2

After installation, the tools appear as mcp__whereis__*.

No key vs. key

CapabilityNo keyWith key
list_operatorsYesYes
get_latest_statusYesYes
track_shipmentNoYes
refresh=true carrier pullNoYes

If anonymous MCP connections are not enabled on the deployment, no-key users can still call the public status endpoint directly:

curl "https://api.eg1.io/v0/status/fdx-879448793247"

Add a key (optional)

To unlock full history, add a higher-priority override to your profile's cordis.patch.yml (or the equivalent profile patch) that restates the whole row:

- id: whereis-mcp
  name: '@deepseek-ai/dsh-mcp-client'
  config:
    serverName: whereis
    transport: streamable-http
    url: https://api.eg1.io/mcp
    headers:
      Authorization: !!js '`Bearer ${process.env.WHEREIS_API_KEY}`'
    toolCallTimeoutMs: 120000
    failOnStartupError: true

Set WHEREIS_API_KEY in the environment that launches DeepSeek Harness. The !!js expression is evaluated in the Harness process, not in the conversation, so the key does not appear in chat. If your client cannot use !!js, put a local-only literal in the profile patch instead and keep that file out of version control.

Do not put keys in this package, in cordis.patch.yml inside the bundle, or in a message.

Usage

What carriers does Whereis support?

Where is fdx-879448793247?

Track these FedEx numbers and tell me if anything is delayed:
879512749003, 879512676449, 879248502068.

Track sfex-SF1234123412341 with phone 6993.

For SF Express, include the last four digits of the recipient's phone. Tracking IDs are <operator>-<tracking_number>.

Troubleshooting

SymptomFix
Tools do not appearCheck that the bundle is installed and selected; check the MCP connection error in Plugins
401-01 / 401-02No key or a bad key. Status-only works without one; add a key only for history
403-01The key is restricted; use a full key
404-01The carrier has no data; verify the number or note retention limits
Connection fails at startupConfirm https://api.eg1.io/mcp is live and reachable
HTTP 403 from a self-hosted endpointCheck MCP_ALLOWED_HOSTS / connect from an allowed host

Privacy

The agent sends only tracking IDs and, for SF Express, the last four phone digits to the API. It should not send names, addresses, or other personal data. The package contains no credentials and no tracking data.

Uninstall

Remove eagle1-whereis-mcp from the Plugins page, or:

plugin_manager
  action: remove_bundle
  target: eagle1-whereis-mcp

License and icon

BSD-3-Clause. The icon is the EG1 logo from whereis.eagl.io, used with permission; see ICON.md.