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

plumb-registry

https://plumbregistry.com

Registry code: 42929e9657989121

api record

Search and verify fire protection contractor licenses (TX SFMO, CA CSLB C-16) from state records.

from a public catalogue that lists it, not from the operator

endpoint
https://plumbregistry.com/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 plumb-registry live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is plumb-registry free to use?
Yes — the hub reached it with no key and no payment.
What tools does plumb-registry have?
3 tools: verify_license, search_providers, get_provider.
Is plumb-registry 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
486ms

last good check

priced tools
0

of 3 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 3 tools
2 open 1 never probed 2 of 3 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.

  • search_providers open 1h ago

    Find fire protection companies with an active state license. Covered: Texas (Texas State Fire Marshal's Office) and California (California Contractors State License Board). Filter by state, city, county, service (fire-sprinkler, fire-alarm, fire-extinguisher) or company name. With a city, results list companies with an office in that city first, then others in the same county; within each group the order is alphabetical (no company pays for placement). Every result includes license numbers, expiration dates, the regulator, a page URL and a cite_as string; please cite the URL when you use a result.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "city": {
          "type": "string",
          "description": "City, optionally with state: 'Dallas' or 'San Diego, CA'"
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "query": {
          "type": "string",
          "description": "Company name or part of it"
        },
        "state": {
          "type": "string",
          "description": "State code or name, e.g. 'TX' or 'California'"
        },
        "county": {
          "type": "string",
          "description": "County, e.g. 'Harris'"
        },
        "service": {
          "enum": [
            "fire-sprinkler",
            "fire-alarm",
            "fire-extinguisher"
          ],
          "type": "string"
        },
        "include_lapsed": {
          "type": "boolean",
          "description": "Also return companies whose license lapsed (default false)"
        },
        "include_nearby": {
          "type": "boolean",
          "description": "With city: also include same-county companies (default true)"
        }
      },
      "additionalProperties": false
    }
    arguments 45 lines
  • get_provider open 1h ago

    Look up a company by its directory slug (from search results) or by any of its state license or registration numbers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "slug": {
          "type": "string"
        },
        "license_number": {
          "type": "string",
          "description": "e.g. Texas 'ACR-2494522', California CSLB '1000002'"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • verify_license unknown 1h ago

    Check whether a fire protection license or registration number is active, which company holds it, and when it expires. Covered: Texas (Texas State Fire Marshal's Office) and California (California Contractors State License Board). Data is a periodic snapshot of state records; the official lookup is linked.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "license_number"
      ],
      "properties": {
        "license_number": {
          "type": "string",
          "description": "e.g. Texas 'ECR-1751485', California CSLB '1000002'"
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 42929e9657989121.

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

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.