API
DSH Marketplace API
A public JSON API over 20,615 DeepSeek Harness plugins. No key, no sign-up, CORS open — the same endpoints this site, the CLI, the Python package and the in-harness plugin all read from.
Two endpoints
| Endpoint | Answers |
|---|---|
GET /api/v1/plugins | Tell me about this plugin. |
GET /api/v1/index | Which of these thousand repositories are plugins at all? |
Both are open over CORS and need no authentication. If you are building a directory, a chat tool or an agent that installs plugins, take them — that is what they are for, and it beats crawling the GitHub topic again.
GET /api/v1/plugins
curl -s 'https://dshmarketplace.dev/api/v1/plugins?q=memory&limit=5'| Parameter | |
|---|---|
q | Free text, matched against the repository name, both summaries and the description |
category | One of the 14 category ids |
limit | 1–100, default 20 |
installCheck | One verdict from the install-check table below. installCheck=passed returns only plugins whose command was actually run and worked — what the in-DSH store requests, so nothing it offers can fail to install. Unknown values are ignored rather than erroring. |
page | 1-based |
Every result carries both summaries, the resolved install command, the detected risk flags and the source repository:
{
"fullName": "liustack/modlens",
"summary": "…",
"summaryZh": "…",
"category": "vision",
"stars": 2325,
"license": "MIT",
"npmPackage": "@liustack/modlens",
"installKind": "npm",
"install": "dsh plugin --profile web add @liustack/modlens",
"installable": true,
"installOptions": [{ "label": "npm", "cmd": "…", "note": "…" }],
"riskFlags": ["terminal surface"],
"repoUrl": "https://github.com/liustack/modlens",
"url": "https://dshmarketplace.dev/plugins/liustack-modlens"
}The install contract
install is null rather than a placeholder when no command can install the plugin. This is the part worth reading twice if you are writing an agent. A caller that runs whatever is in that field must never be handed a string that fails, so the field is empty instead — and installable says the same thing as a boolean.
Two cases produce it, and both are real:
- A plugin in a monorepo subdirectory.
dsh plugin addforwards to pnpm, and pnpm reads everything after#as a git ref, sogithub:owner/repo#packages/thingcannot resolve. There is no one-line install, so none is offered. - A plugin published nowhere. No npm package and no installable repository root.
Every command that is returned carries --profile web. dsh plugin is a thin forward to pnpm inside a profile directory, so the flag is mandatory — without it the CLI exits with required option '--profile <name>' not specified and nothing installs. Swap web for your own profile name if you run another one.
GET /api/v1/index
curl -s 'https://dshmarketplace.dev/api/v1/index'The whole catalogue in one response, for clients that must decide whether a page full of repositories contains plugins and cannot ask about them one at a time. Rows are positional to keep it small — around 22 KB over the wire — and the column names ship with the payload:
{
"generated": "2026-08-17T09:12:44.108Z",
"count": 20615,
"site": "https://dshmarketplace.dev",
"fields": ["fullName", "category", "install", "path", "npm"],
"plugins": [
["liustack/modlens", "vision", "dsh plugin --profile web add @liustack/modlens", "/plugins/liustack-modlens", "@liustack/modlens"]
]
}path is null when a listing has no page of its own yet, and npm is null when the plugin publishes nowhere. As with install, none of them is ever a placeholder.
What is in the catalogue
20,615 listings, drawn from the community registry and the dsh-plugin GitHub topic. The topic is not a registry, so admission is gated — and the bar is published here because a filter nobody can check is not a filter:
- It declares a DSH plugin. A
dshmanifest inpackage.json, a dependency on@deepseek-ai/*or Cordis, or acordis.patch.yml. Other harnesses and agent clients tag themselvesdsh-pluginfor the attention; they are not installable here and are not listed. - Ten commits or more. Taken from awesome-dsh-plugin's own bar rather than invented here, so the standard is one you can check against someone else's. A scaffold has a valid manifest on its first commit; commit count is what tells it apart from work.
- It says what it does. A repository with no description at all is a link, and a link is what every other directory already gives you.
Applying that bar removed 1,415 rows in one pass — 754 of them repositories with fewer than five commits. A directory's value is what it leaves out.
Every listing is install-tested
This is the one thing a scraper cannot copy. Each install command is run in a throwaway container that has never seen the plugin, and the result is recorded against that exact command — it is installCheck on the API and a badge on every card and page. A name in a repository is not evidence that it installs; the run is.
| Verdict | |
|---|---|
passed | Installed and registered as a plugin, no intervention. |
needs-approval | Installs once a build script is allowlisted, which dshmarketplace-cli does for you. Counted as installable. |
not-a-layer | The package installs but declares no plugin layer — not a failure, not a plugin. Left out of the rate entirely. |
incompatible | DeepSeek Harness refused the latest release before installing anything: its engines.dsh, or its @deepseek-ai/dsh* peer ranges, do not cover the dsh we ran. We then install the newest release that dsh accepts and publish that result as installFallback. dshmarketplace-cli picks that release for whatever dsh you run, so a working fallback counts as installable; no fallback counts against. |
failed / timeout | Did not install. The few percent we flag instead of letting you find out. |
Every verdict says which DeepSeek Harness produced it ( installCheckDsh), because from 0.2 the harness refuses plugins built for another version of it, and the same command can pass on one release and be refused by the next. The headline N% install-verified counts only verdicts that carry a version — everything before 18 Oct 2026 ran on dsh 0.1 and is being re-run — and is passed, needs-approval and incompatible with a working fallback, over everything run. not-a-layer and untested rows are excluded from both sides, so it is a rate over tested plugins, not a claim about the whole catalogue. Verdicts are produced under a pinned pnpm 10.
Browse it inside DeepSeek Harness
From dsh 0.2.1 the harness can browse a third-party plugin index in a Discover tab on its Plugins page. This catalogue publishes one at https://dshmarketplace.dev/market/index.json, in the harness's own format 1. To add it: open Plugins, select More beside Experimental plugins, switch on Custom plugin markets, then in Discover choose Add index source and paste the URL.
Only releases the sandbox installed are listed, each with the engines.dsh range the harness checks it against, so the tab offers a plugin only where it will install. When dsh refused a plugin's latest release and an older one installed, the older one is listed and labelled as such. Plugins that install from source are not in it: a source install needs a build approved first, which the Discover tab cannot do.
Use it from an agent (MCP)
https://dshmarketplace.dev/mcp is a remote MCP server — Streamable HTTP, no key, read-only. Five tools: search_plugins, get_plugin, install_command, list_categories and list_presets. Their answers come from the same records as /api/v1, sandbox verdicts and fallback releases included, so an agent can tell a user whether a command installs before running it.
# Claude Code
claude mcp add --transport http dshmarketplace https://dshmarketplace.dev/mcp
# Cursor, Windsurf and most other clients (mcp.json)
{ "mcpServers": { "dshmarketplace": { "url": "https://dshmarketplace.dev/mcp" } } }Caching and fair use
Responses carry Cache-Control and are served from Cloudflare's edge. There is no rate limit and no key, which only works if clients behave like clients: cache the index rather than fetching it per page view, and prefer one /api/v1/index call over a thousand /api/v1/plugins calls. The userscript below refreshes at most every six hours, and that is the intended shape.
Four reference implementations
Every one of these reads the endpoints above, and all of them are MIT on GitHub. If you are wiring this into something, one of them has already solved your problem:
| Client | |
|---|---|
| npm | npx dshmarketplace-cli find memory — a stable --json contract for agents |
| PyPI | pip install dshmarketplace — zero dependencies, sync and async |
| In DSH | dsh plugin --profile web add dshmarketplace-plugin — /store, plus two agent-callable tools |
| Userscript | Marks plugins on GitHub and npm — one file, no build, no dependency |
Terms
Free to use, including commercially. No key, no sign-up, no attribution required — a link back is appreciated and never demanded. The data is public repository metadata plus summaries written here; it carries no warranty, and a listing is not a security review. See what this site is not.
Found a listing that is wrong, or want yours removed? Say so and it will be fixed.