_ registry / mcp streamable-http · checked 12h ago

douxprocess-directory

https://douxprocess.directory

Registry code: e5060fa92a681cb7

api record

DouxProcess Directory lists businesses of every kind so a person can find one, check its licence and contact it. find_businesses returns every match in one published order (nobody pays for placement); show the person the options and let them choose. request_contact sends their request to the business they chose, only after they agree. Listings affiliated with DouxProcess's owner carry a disclosure; pass it on.

endpoint
https://douxprocess.directory/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is douxprocess-directory live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is douxprocess-directory free to use?
Yes — the hub reached it with no key and no payment.
What tools does douxprocess-directory have?
4 tools: request_contact, get_business, list_categories, find_businesses.
Is douxprocess-directory safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
487ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_categories open 12h ago

    Every category with its NAICS 2022 code, plain name and Google Business Profile names.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • find_businesses open 12h ago

    Search the DouxProcess Directory for businesses by what the person needs (e.g. roofer, dentist, insurance agency), city and two-letter US state. Returns every match in the published ranking order with phone, website, licence and listing page. Nobody pays for placement; listings affiliated with DouxProcess's owner carry a disclosure.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string"
        },
        "page": {
          "type": "integer",
          "minimum": 0
        },
        "query": {
          "type": "string",
          "description": "What the person needs, in their words."
        },
        "state": {
          "type": "string",
          "description": "Two-letter US state."
        },
        "category": {
          "type": "string",
          "description": "A category id from list_categories, e.g. roofer."
        }
      }
    }
    arguments 24 lines
  • request_contact unknown never probed

    Sends the person's request to the ONE business they chose, so it can reply to them. Call only after the person has read and agreed to this: '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 agreed. Do not include health details, card numbers, ID numbers or passwords.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug",
        "name",
        "details",
        "consent"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The person's name."
        },
        "slug": {
          "type": "string"
        },
        "email": {
          "type": "string"
        },
        "phone": {
          "type": "string"
        },
        "consent": {
          "type": "boolean",
          "description": "True only if the person agreed to the consent sentence."
        },
        "details": {
          "type": "string",
          "description": "What they need, in their words."
        }
      }
    }
    arguments 32 lines
  • get_business unknown 12h ago

    One business's details, licences and how to contact it. Each licence carries its 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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The slug from find_businesses."
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e5060fa92a681cb7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e5060fa92a681cb7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e5060fa92a681cb7/badge.svg)](https://brick.blue/agent/e5060fa92a681cb7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.