← drillable.com

Drillable for developers

Make your coding agent — and your CI — ground a claim in a real, cited source, and say "no record" instead of guessing. There's one easy way in, and a few lanes if you want something specific.

▸ Start here

Make your agent ground itself — one install

The Use Drillable plugin connects your Claude Code agent to Drillable's cited reference sources and nudges it to look things up instead of guessing — the MCP spec, agent & LLM practices, networking, units, and ~60 areas. No key, no account, nothing to configure.

/plugin marketplace add drillablehq/use-drillable
/plugin install use-drillable@drillable

That's the whole setup. It ships disabled — enable it when you're ready (it connects to Drillable and logs your queries as a demand signal, so it's an explicit choice). Adding the marketplace also makes the two lanes below one command each. Tip: in /plugin, turn on auto-update for the marketplace (off by default for ones you add) so updates land without re-installing.

Or pick a lane

When you know what you want:

Ground it in your own project Claude Code plugin

The plugin above grounds general reference facts. Drillable Context grounds your agent in your own project — your CLAUDE.md, your docs, the decisions and gotchas you've written down — so it stops contradicting a choice you made last week or inventing a convention you never set. You point it at a folder of markdown; it drills those files and says "no record" instead of bluffing. It runs locally — your facts never leave your machine (unless you turn on semantic search, which embeds them via OpenAI).

/plugin install drillable-context@drillable     # same marketplace as above

It asks which folder to ground in when you enable it — that's the one bit of setup, because grounding in your docs is the whole point. Using Cursor or another MCP client instead? Add it through your client's own MCP config — the repo has the connection details.

Gate your CI against bad dependencies Service Live on npm

Drillable Check is verification you run, not a plugin — "npm audit for claims." It reads the dependencies you already commit and grades each one against the live package registry and advisory database. It catches the half npm audit can't: not just known-vulnerable packages, but ones that don't exist — the name an AI confidently invented, which an attacker then registers.

Run it once

npx drillable-check              # check this repo's lockfiles
npx drillable-check --diff       # only what changed vs the base ref

Gate every PR (GitHub Action)

- uses: actions/checkout@v4
  with: { fetch-depth: 0 }       # so --diff can see the base ref
- uses: drillablehq/drillable-check@v0
  with:
    scan-diff: true

Or block the commit (pre-commit)

- repo: https://github.com/drillablehq/drillable-check
  rev: v0.1.1
  hooks:
    - id: drillable-check

It fails the build only when a claim is contradicted. Each dependency comes back verified (real, drilled to the registry), corrected (a name that doesn't exist, an unpublished version, or a known CVE — this is the gate, exit 1), or "no record" (an ecosystem it doesn't cover yet, or the registry was unreachable). An honest "no record" never fails — so it's safe to leave on in CI, where noisy gates just get deleted.

Checks today: npm (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml), PyPI (requirements.txt, pyproject.toml), and crates (Cargo.toml) — name exists, version published, known advisories. Grading arbitrary prose claims is on the roadmap; until then it checks dependencies and stays silent on everything else, so it never false-alarms.

Use the sources from any MCP client Live

Not on Claude Code, or want the raw connection? The reference gateway is a remote MCP server — point any client (Cursor, ChatGPT, your own agent) at it and the cited sources are yours directly. This is the engine the Use Drillable plugin wraps. No key, no account.

claude mcp add --transport http drillable https://mcp.drillable.com

Any MCP client works — point it at https://mcp.drillable.com (streamable HTTP, no auth). Full tool list and per-client setup in the docs.

Which one do I want?

You want to…Reach for
Just make your agent stop guessing reference factsUse Drillable · the one-install start
Stop it inventing your project's conventions and decisionsDrillable Context · plugin
Block bad dependencies in CI or a pre-commit hookDrillable Check · npx / Action
Call the cited sources from another MCP clientthe gateway · mcp.drillable.com