Derrick
com.derrick-appPublished by derrick-app.comOfficial publisherv1.0.0Updated Oct 24, 2026
B2B data enrichment: verified work emails, phones, firmographics, tech stack, hiring signals.
Overview
Derrick is a remote MCP server that lets an assistant enrich B2B contacts and companies with verified work emails, phones, firmographics, tech stack and hiring.
- What you can do
- Derrick provides B2B data enrichment through a remote MCP endpoint. According to its description, it supplies verified work emails and phone numbers along with firmographic details, technology stack information and hiring signals. The manifest lists no individual tools, so the exact operations are not documented here. It is intended to feed contact and company data into assistant workflows.
- When to use it
- Use it when an assistant needs to look up or complete business contact and company records, for example enriching leads with verified emails, phones, firmographics or tech stack details. It suits sales, recruiting or market research workflows that depend on B2B data.
- Requirements
- A remote MCP endpoint at app1.derrick-app.com over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open Derrick in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.derrick-app%2Fderrick/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"derrick": {
"type": "http",
"url": "https://app1.derrick-app.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 24, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.