Company Dossier for Claude.

Research a company without leaving Claude. There's a Claude Agent Skill you can drop in, and an MCP connector you can add to Claude or Claude Code — then just ask Claude to build a dossier. Both run the same engine and return the same complete, sourced, nine-section file. Free, public sources only.

Get Company Dossier See a sample file

Public information only — gathered for you, never bought or breached.

the skill

A Claude Agent Skill

Add the company-dossier skill to Claude, then ask in plain language. Claude knows how to run the research and lay the file out for you.

# the skill is named company-dossier # a sample prompt, in plain language You: Build a dossier on Stripe. › Claude runs the company-dossier skill … Claude: Here's the file — nine sourced sections, each claim pointed back to its public source.

The skill teaches Claude the method behind a dossier — what the nine sections are, where to pull each one from the public record, and how to keep every claim sourced. You don't have to spell out the steps; name the company and ask for the file.

the connector

An MCP connector

Prefer to wire it in as a tool? Add the Company Dossier MCP connector to Claude or Claude Code and the assistant can call the engine directly while you talk.

# add the MCP connector (Claude Code shown) $ claude mcp add company-dossier -- npx company-dossier --mcp › connector registered — Claude can now call it as a tool You: Give me the money trail and risk flags for acme.com.

The MCP connector exposes Company Dossier as a tool Claude can invoke mid-conversation. Behind it, the work is the same research that npx company-dossier performs — that's what powers it — so you get an identical sourced file, driven by the model and surfaced right in your Claude session.

what it returns

The same nine-section file

Conversational on the outside, the same complete dossier underneath.

Overview & identity — what the company does, when it started, who owns it.
People & org chart — leadership and how the org is shaped.
Hiring radar — open roles and where headcount is growing.
Money trail — funding, investors, filings and revenue signals.
Locations — headquarters and offices.
Tech fingerprint — the stack they build on.
News & timeline — press and milestones in order.
Relationship web — customers, partners and rivals.
Risk flags — lawsuits, layoffs and reputation notes.

It all comes from public sources only, and every claim points back to where it came from. The target company doesn't need to be involved or aware. A dossier is a fast, honest starting map — built to be verified, not taken on faith.

good to know

Questions, answered

Q. Skill or connector — which do I use?

Either. The skill is the quickest drop-in for the Claude app; the MCP connector is ideal in Claude Code and other MCP-aware clients where you want it as a callable tool.

Q. What's actually doing the research?

The same engine as everywhere else — npx company-dossier powers both the skill and the connector. The CLI page covers it in full.

Q. Where does the data come from?

Public sources only — job boards, filings, news and the open web. No private data, no login bypass.

Get Company Dossier

Open me

Ask Claude for a dossier.

name a company. read the whole story, sourced, in the chat.

Open a dossier See a sample file