DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins
E

eagle1-whereis-mcp

Eagle1 Whereis Mcp

Whereis shipment tracking for DeepSeek Harness: connects the Eagle1 Whereis MCP server so agents can check the latest shipment status and, with a key, full tracking history.

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:eagle1-sys/eagle1-whereis-mcp#d535071ef309faa5f868f01f1abd3db3caa3943b
READMECompatibilityVersions

Compatibility and provenance

Eagle1 Whereis Mcp is published as eagle1-whereis-mcp and currently resolves to version 1.0.2. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
any
Release source
github
Registry updated
11/4/2026

Versions

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

Related plugins

Loading related plugins…

Latest
1.0.2
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
any
License
BSD-3-Clause
Source
github
GitHub
★ 1
Weekly downloads
0
Last push
11/4/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in integrations-communication.

Acp App@deepseek-ai/dsh-acp-appThe dsh ACP profile bundle: automation-only JSON-RPC stdio and process lifecycle over dsh-baseRemote Web Ui@linxin666/dsh-remote-web-uiScan-to-pair remote access for the dsh web GUI that shares one official interface: a QR beside the settings button pairs phones and PCs into the same Web GUI (a portrait-touch adaptation layer for phones, full desktop on PCs) through one-time tokens and rRemote Bridge@linxin666/dsh-remote-bridgeDSH remote bridge: the host half serves protocol v1 over one exact /ios/v1 WebSocket route — session roster, history baseline, prompting, live turn increments with tool activity, interrupt, and in-process agent approval — to a device paired by a one-shot Ds Botds-botDS Bot: a team of long-lived Bots for DeepSeek Harness, with Main Bots, Bot-to-Bot messages and group chats

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.