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

gocodebook-codes

https://gocodebook.com

Registry code: f08df234ba18db3b

api record

Verbatim California building, residential, fire, plumbing, mechanical, green and energy code text, plus city and county zoning ordinances, looked up by section number. Results are verbatim excerpts, each with a citation and a Source link to the full section. This server does not decide whether a project complies. lookup_california_code_section and list_california_code_documents are free; search_california_codes finds sections by topic, needs the user's GoCodebook account and uses 1 credit per search — prefer the free lookup whenever the user already has a section number.

endpoint
https://gocodebook.com/api/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 gocodebook-codes live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is gocodebook-codes free to use?
Yes — the hub reached it with no key and no payment.
What tools does gocodebook-codes have?
3 tools: search_california_codes, lookup_california_code_section, list_california_code_documents.
Is gocodebook-codes 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 99.3%· all time 99.3%

latency
1,429ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 446 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • look up a california building code section
  • look up a zoning ordinance
  • list available codes
takes → gives
text → text
tools
2 reads
_ 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
1 open 2 never probed 1 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.

  • list_california_code_documents reads open 6h ago

    List the California codes and local ordinances available for lookup, and what is not covered. Useful before concluding that a code is unavailable, and for finding the exact document or jurisdiction slug that a lookup takes.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "jurisdiction": {
          "type": "string",
          "description": "Optional. A California city or county slug — returns the documents held for that jurisdiction instead of the statewide list."
        }
      }
    }
    arguments 9 lines
  • search_california_codes unknown never probed

    Search California building codes (Title 24), state housing law and California city and county zoning/municipal codes by TOPIC, when the user does not already have a section number — e.g. "minimum attic access opening", "ADU setbacks in San Jose". Requires the user's GoCodebook account and uses 1 credit per search (also when nothing is found). If the user already cites a section number, use lookup_california_code_section instead — it is free. Returns ranked excerpts with citations and links. It does NOT decide whether a project complies.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "What to find, in plain words. Up to 300 characters."
        },
        "sources": {
          "type": "array",
          "items": {
            "enum": [
              "federal",
              "state",
              "local"
            ],
            "type": "string"
          },
          "description": "Optional. Limit to federal law, state codes, or local ordinances."
        },
        "code_edition": {
          "enum": [
            "current",
            "2022",
            "2019"
          ],
          "type": "string",
          "description": "Optional. Which Title 24 cycle to search; a permit filed in 2024 is enforced under \"2022\". Defaults to \"current\"."
        },
        "jurisdiction": {
          "type": "string",
          "description": "Optional. A California city or county slug (\"san-jose\", \"marin-county\") to search that place's own code together with the state codes. Omit for statewide."
        }
      }
    }
    arguments 37 lines
  • lookup_california_code_section reads unknown 6h ago

    Look up the VERBATIM text of a California building, residential, fire, plumbing, mechanical, green (CALGreen), energy or existing-building code section, or a section of a California city or county zoning/municipal ordinance, by its section number. Use this whenever the user cites a section number ("CRC R602.10.2.3", "CBC 1004", "§ 17.60.090") or asks what a specific section says. Returns the official text with its citation, edition and a link to the full section. It returns code text only and does not determine whether a specific project complies.

    mcp-tool

    {
      "type": "object",
      "required": [
        "section"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "Optional. The code the user named, so a number that exists in several codes returns the right one. An abbreviation or a name: \"CBC\", \"CRC\", \"CFC\", \"CMC\", \"CPC\", \"CEC\", \"CEBC\", \"CALGreen\", \"CHBC\", \"California Fire Code\". Omit when the user gave no code name."
        },
        "section": {
          "type": "string",
          "description": "The section number exactly as cited, without the code name. Examples: \"R602.10.2.3\", \"1004\", \"507.2\", \"17.60.090\", \"11B-206\"."
        },
        "code_edition": {
          "enum": [
            "current",
            "2022",
            "2019"
          ],
          "type": "string",
          "description": "Optional. Which Title 24 cycle to read. California enforces the edition in force when the permit application was submitted, so a project filed in 2024 is enforced under \"2022\". Defaults to \"current\" (the 2025 cycle, in force since 2026-01-01)."
        },
        "jurisdiction": {
          "type": "string",
          "description": "Optional. A California city or county slug to scope the lookup to its own municipal code — \"los-angeles\", \"san-jose\", \"marin-county\". Omit for statewide Title 24 codes."
        }
      }
    }
    arguments 29 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 f08df234ba18db3b.

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