_ registry / mcp streamable-http · checked 36m ago

dev.workers.quietworklabs.txlicense-leads/txlicense-leads

https://txlicense-leads.quietworklabs.workers.dev

Registry code: 4cb0072ebd8bc615

api record

Daily new-business lead data from public records. list_datasets describes the 8 feeds. *_sample tools (including new_business_leads_sample) are free and delayed by 7 days. The *_fresh tools return current records at $0.99 per call via x402 (USDC on Base). buy_info explains the 30-day feed passes.

endpoint
https://txlicense-leads.quietworklabs.workers.dev/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 dev.workers.quietworklabs.txlicense-leads/txlicense-leads live?
Yes — it answered the hub's last check (checked 36m ago). It answered 100% of checks over the last 30 days.
Is dev.workers.quietworklabs.txlicense-leads/txlicense-leads free to use?
No — it charges per call, from 0.99 USDC, quoted in its own 402 answers.
What tools does dev.workers.quietworklabs.txlicense-leads/txlicense-leads have?
8 tools: new_trucking_authorities_sample, list_datasets, buy_info, new_trucking_authorities_fresh, texas_liquor_licenses_fresh, texas_liquor_licenses_sample, new_business_leads_sample, new_business_leads_fresh.
Is dev.workers.quietworklabs.txlicense-leads/txlicense-leads 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
140ms

last good check

priced tools
7

of 8 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, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 4 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
1

distinct

settlements
1

last 2026-10-18

received on chain
0.001 USDC

counted from three payers (thin, concentrated, shared-payto)

_ what it can do 8 tools
7 paid 1 never probed 7 of 8 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_datasets paid never probed

    The 8 public-record lead feeds: key, title, source agency, freshness, volume, license terms, regions and record counts. Free.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • buy_info paid never probed

    Pricing and purchase links for 30-day feed passes (card/Apple Pay/USDC) and x402 day passes. Free.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • new_trucking_authorities_fresh 0.99 USDC paid 36m ago

    Current FMCSA events: granted, applied, insurance_lapse, with phone, address and insurance on file. Filters: state, event (comma list), days (1-30, default 2). Up to 300 records. Price: $0.99 USDC per call via x402 (Base).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "string",
      "description": "1-30, default 2"
    },
    "event": {
      "type": "string",
      "description": "granted,applied,insurance_lapse (default granted)"
    },
    "state": {
      "type": "string",
      "description": "two-letter state"
    }
  }
}
    arguments 17 lines
  • texas_liquor_licenses_fresh 0.99 USDC paid 36m ago

    Current TABC new license applications and newly issued permits (no delay). Filters: county, days (1-30, default 3). Up to 300 records. Price: $0.99 USDC per call via x402 (Base).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "string",
      "description": "1-30, default 3"
    },
    "county": {
      "type": "string",
      "description": "Texas county"
    }
  }
}
    arguments 13 lines
  • texas_liquor_licenses_sample paid never probed

    New TABC liquor license applications and issued permits in Texas, delayed 7 days. Optional county filter. Phone numbers removed. Up to 100 records. Free.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "string",
      "description": "window in days, 1-60 (default 14)"
    },
    "county": {
      "type": "string",
      "description": "Texas county, e.g. Harris"
    }
  }
}
    arguments 13 lines
  • new_business_leads_sample paid never probed

    Free 7-day-delayed sample from one feed: ny = New York liquor license applications (SLA pending); ca = California ABC new liquor license applications; fl = Florida new alcohol & tobacco licenses (DBPR); co = New Colorado business filings (LLCs & corporations); wa = New Washington contractor licenses (L&I); chi = New Chicago business licenses. Optional region (county, city or Chicago community area). Individuals' names, phones and some street addresses removed. Up to 100 records. Free.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feed"
  ],
  "properties": {
    "days": {
      "type": "string",
      "description": "window in days, 1-60 (default 14)"
    },
    "feed": {
      "enum": [
        "ny",
        "ca",
        "fl",
        "co",
        "wa",
        "chi"
      ],
      "type": "string",
      "description": "feed key"
    },
    "region": {
      "type": "string",
      "description": "county, city or community area"
    }
  }
}
    arguments 28 lines
  • new_business_leads_fresh paid never probed

    Current records (no delay) from one feed: ny, ca, fl, co, wa, chi. Filters: region, kind (type text match), days (1-30, default 3). Up to 300 records with full details. Price: $0.99 USDC per call via x402 (Base).

    mcp-tool

    {
  "type": "object",
  "required": [
    "feed"
  ],
  "properties": {
    "days": {
      "type": "string",
      "description": "1-30, default 3"
    },
    "feed": {
      "enum": [
        "ny",
        "ca",
        "fl",
        "co",
        "wa",
        "chi"
      ],
      "type": "string"
    },
    "kind": {
      "type": "string",
      "description": "type text match, e.g. Restaurant"
    },
    "region": {
      "type": "string",
      "description": "county, city or community area"
    }
  }
}
    arguments 31 lines
  • new_trucking_authorities_sample unknown 36m ago

    FMCSA operating authorities granted, delayed 7 days. Optional two-letter state. Phone and street removed. Up to 100 records. Free.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "string",
      "description": "window in days, 1-30 (default 7)"
    },
    "state": {
      "type": "string",
      "description": "two-letter state, e.g. TX"
    }
  }
}
    arguments 13 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 4cb0072ebd8bc615.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4cb0072ebd8bc615/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/4cb0072ebd8bc615/badge.svg)](https://brick.blue/agent/4cb0072ebd8bc615?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
100%

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.