Vendor: derrick-app.com · entry id 01-derrick · source 01-data-enrichment.md line 758
The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-09-07 and the MCP URL has not been probed live yet.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://app1.derrick-app.com/mcp (docs: https://derrick-app.com/mcp; the same page advertises a server card at /.well-known/mcp/server-card.json) ; repo https://github.com/DerrickAppOrg/derrick-mcp
A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.
141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.
This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing.
Install, as the source shows it:
npm install -g derrick-cliquoted from https://www.npmjs.com/package/derrick-cli on 2026-09-27, via npm, a third party source
npm install -g create-derrick-project-cliquoted from https://www.npmjs.com/package/create-derrick-project-cli on 2026-09-27, via npm, a third party source
Packages seen, with the version on 2026-09-27:
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.
api_gate, verbatim from the file:
paid - the vendor's MCP page states that API keys "unlock from the PLUS plan" and prices that plan at 47.5 euros per month. The same page contradicts itself twice in the surrounding copy, and both contradictions are recorded in notes rather than resolved by guesswork.
No documentation URL recorded.
727 of 1252 entries are in the same position. Blank is legal and it is published as blank.
Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.
The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.
A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:
github.com/DerrickAppOrg tied to the vendor by rule 1, the directory already classed this repo first-party and its owner is an Organization, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| derrick-outbound-plugin | plugin or integration | 0 | 2026-07-16 | ||
| derrick-mcp | MCP server | 0 | 2026-07-12 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
No job tag on this entry.
981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.
4 source URLs. Raw sources field, verbatim:
https://derrick-app.com/mcp, https://app1.derrick-app.com/mcp, https://derrick-app.com/, https://github.com/DerrickAppOrg/derrick-mcp
Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.