Model Context Protocol (MCP) server for Apollo.io API integration
DouxProcess Directory is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Is a US business licensed, bonded and insured today? From the government record. Free, no paid rank.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http douxprocess-directory-mcp https://douxprocess.directory/mcp
# 2 — ask your agent for something these tools do
# find_businesses, get_business, verify_license and 8 more
DouxProcess Directory costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http douxprocess-directory-mcp https://douxprocess.directory/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search the DouxProcess Directory for US businesses by what the person needs (roofer, electrician, insurance agency...) and where (a city and state, a ZIP, or a state). Returns the matches in the published ranking order with license, how it was checked, phone, website and listing page. covered=false with a note means the directory does not hold that kind of business or place yet: say so, do not gue
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What the person needs, in their words. |
| where | string | no | A place: 'Pasadena, CA', a 5-digit ZIP, or a state. Never the person's own address or GPS. |
| category | string | no | A category id from list_categories, e.g. roofer. |
| state | string | no | Two-letter US state. |
| city | string | no | — |
| postal_code | string | no | A 5-digit ZIP. |
| radius_miles | number | no | — |
| limit | integer | no | — |
| cursor | string | no | next_cursor from the previous call. |
| page | integer | no | Older clients: a page number. Prefer cursor. |
One business's details: licenses with their basis (issuer_file = matched against the issuer's own published file on checked_at; stated = given by the business, not yet matched, send the person to source_url), contact, whether it takes requests, and its own agent addresses (MCP and A2A).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The slug from find_businesses. |
Look up a license by number, business name or phone and say which listings carry it and how it was checked. When nothing matches, tell the person to check the issuer's own lookup; never say a license is valid without a match.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | no | The license number. |
| name | string | no | The business name. |
| phone | string | no | — |
| issuer | string | no | The issuer code, e.g. CA-CSLB. |
Every category with its id, NAICS 2022 code, plain name, Google Business Profile names, how many listings it has, and whether requests for it are sent (health is listed but never routed).
No parameter schema on file.
Ask in plain words ('licensed electrician near 92101 who does EV chargers') and get a short answer built only from listings, plus the businesses it rests on, in the published order. Same rules as find_businesses: no ranking or recommendation language, coverage stated honestly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The person's question, in their words. |
| where | string | no | A place, if it is not in the question. |
Sends the person's request to the ONE business they chose, so it can reply to them. Only claimed listings take requests, and health businesses never do. Before calling, show the person this sentence and get their agreement: 'I agree that DouxProcess sends my name, my contact details and this request to <business>, and only to them, so they can reply to me about it.' Set consent=true only if they a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The slug from find_businesses or get_business. |
| name | string | yes | The person's name. |
| string | no | An email address the business can reply to. | |
| phone | string | no | Or a phone number the business can reply to. |
| details | string | yes | What they need, in their words. No health details, card numbers, ID numbers or passwords. |
| consent | boolean | yes | True only if the person read and agreed to the consent sentence. |
Open the request form for one business the person chose (ChatGPT local services Get Quote). The form shows the consent sentence and sends only when the person ticks it. For a business that does not take requests it shows the business's own phone and website.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_id | string | yes | The business id (its slug) from find_businesses or the business feed. |
A California contractor license's record in the CSLB's public file, and every change since the directory began reading it daily: status and suspensions, workers' comp type and dates, bond amounts and dates, classes, expiry. Give a CSLB license number or a listing link. It never includes an insurer, surety or person's name, or a policy, bond or case number. Report what it says; do not judge the bus
| Parameter | Type | Required | Notes |
|---|---|---|---|
| license | string | yes | A CSLB license number (e.g. 1000002), or a listing link or slug from find_businesses. |
Emails the person a link to watch these CSLB licenses: once they open it, they get one short email on any day something changes on one (status, workers' comp, bonds, classes, expiry). Nothing is watched until the person opens the link. Use the person's own email, only when they asked. Free watches 25 licenses, Pro up to 500 for $99 a year, Unlimited every license they add for $999 a year. Not for
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The person's own email address. | |
| licenses | array | yes | CSLB license numbers or listing links, up to 500. |
Is this business licensed, bonded and insured today, from the government record. Give a listing slug, a license number, or a business name with its two-letter state. Returns licensed, bonded and insured as true, false or null (the record does not say), each with its source, checked_at day and record_url, the board's open gaps, and the listing URL. For CSLB contractors insured means workers' comp.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | A listing slug or link from find_businesses. |
| license | string | no | A license number, e.g. CSLB 1050000. |
| issuer | string | no | The issuer code with a license number, e.g. CA-CSLB. |
| name | string | no | The business name (with state). |
| state | string | no | Two-letter US state, required with name. |
Emails the person a link to watch up to 25 listings free: once they open it, they get one short email on any day the board's record changes (status, workers' comp, bonds, classes, expiry). CSLB contractors only. Use the person's own email, only when they asked. Before calling, show them this and get their yes: 'I agree that DouxProcess Directory may email <email> about changes to these licenses (s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The person's own email address. | |
| slugs | array | yes | Listing slugs (or CSLB license numbers), up to 25. |
| consent | boolean | yes | True only if the person read and agreed to the consent sentence. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DouxProcess Directory or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| find_businesses | no tags | |
| get_business | no tags | |
| verify_license | no tags | |
| list_categories | no tags | |
| ask | no tags | |
| request_contact | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| request_service | no tags | |
| license_history | no tags | |
| watch_licenses | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| verify_business | no tags | |
| watch_business | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish DouxProcess Directory can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.