com.wellstatelabs/sb1150-screening
Registry code: 96a1323f61b176d9
WellState Labs SB 1150 screening, read-only. Every figure comes from one content-addressed publication: wellstate-iwar-20261006-e20270901, root 2e4a3f385fea40a355ac418fc8c31348df4c9acc8f0e8b0004a07add9748509c, contract 1.7.0, evaluation date 2027-09-01, built from the Railroad Commission of Texas Inactive Well Aging Report iwar-20261006.txt.
Boundary: Screening results are cost proxies. They are not ARO, not legal determinations, not bond amounts. Production, legal and financial reliance are on HOLD. Every tool result carries this text in its boundary field; keep it with any figure taken from…
- endpoint
- https://mcp.wellstatelabs.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 com.wellstatelabs/sb1150-screening live?
- Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
- Is com.wellstatelabs/sb1150-screening free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does com.wellstatelabs/sb1150-screening have?
- 9 tools: search_operators, list_operator_wells, get_operator_exposure, get_well, screen_operators, screen_book, get_plug_record, verify_publication, ….
- Is com.wellstatelabs/sb1150-screening 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.
90 days 100%· all time 100%
last good check
of 9 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
get_plug_record open 5h ago
Returns the publication's plug record (contract 1.4.0 and later): W-3 plug dates on the Railroad Commission of Texas Full Wellbore file, counted by the calendar year the operator reported and by district, as published. Without a district it returns the statewide count for each year and each district's count for each year. With a district it returns that district's years with state-funded plug numbers, well types and district bases. With rows_limit it pages the per-wellbore rows one district and one year's count is made of, each with the line of the Full Wellbore file it was read from. Every response carries the publication's claims with their labels (DOCUMENTED_FACT, INFERENCE, UNKNOWN), the two UNKNOWN claims that travel with every count, and the publication's statement of what the record is not. This server computes no figure from these counts and combines none with the screening counts. On an edition without a plug record the plug_record field is null.
{ "type": "object", "properties": { "district": { "type": "string", "pattern": "^[0-9A-Z_]{2,20}$", "description": "A district key of the plug record: a Commission district (e.g. 08, 7C, 8A) or NOT_IN_SOURCE for wellbore-years the file gives no district. Omit for the statewide years and every district's counts." }, "last_year": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "Last calendar year returned. Default: the last year of the plug record's window." }, "first_year": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "First calendar year returned. Default: the first year of the plug record's window." }, "rows_limit": { "type": "integer", "default": 0, "maximum": 200, "minimum": 0, "description": "Per-wellbore rows to return, 0-200. Default 0 (counts only). Rows are served for one district and one year per call: pass district, and first_year equal to last_year." }, "rows_offset": { "type": "integer", "default": 0, "maximum": 9007199254740991, "minimum": 0, "description": "Rows to skip before the first one returned, for paging. Default 0." } }, "additionalProperties": false }arguments 37 linesverify_publication open 5h ago
Recomputes the publication root hash from the manifest copy bundled with this server, reports the SHA-256 and byte count of each manifest data file as verified against the manifest when the server was built (all files, or the given paths), and re-hashes every bundled derived index file against its build attestation. Also returns the manifest URL and file URL template for an independent check, and the manifest's Full Wellbore cross-check counts when the edition carries them.
{ "type": "object", "properties": { "paths": { "type": "array", "items": { "type": "string", "pattern": "^(?:data|source)\\/[A-Za-z0-9_.-]{1,80}$" }, "maxItems": 20, "minItems": 1, "description": "Manifest data_files paths to report (e.g. data/operator.ndjson). Omit to report every file." } }, "additionalProperties": false }arguments 16 linesget_publication open 5h ago
Describes the WellState SB 1150 screening publication served here: root hash, publication id, contract (schema) version, evaluation date, the Railroad Commission of Texas source file with its SHA-256, the screening rule parameters and headline counts, the Commission rate table the plugging costs were computed from, the manifest's Full Wellbore cross-check counts and, from contract 1.4.0, the plug record's basis with its claims and their labels (DOCUMENTED_FACT, INFERENCE, UNKNOWN), each when the edition carries it. The verified field is true when the bundled copy of the manifest recomputes to the pinned root hash and the derived-data attestation matches the digest pinned at build time.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linessearch_operators unknown never probed
Finds operators whose Railroad Commission of Texas name contains the given text, case-insensitive. Returns up to 20 matches with operator number, display name, wellbore claims and affected count, ordered by affected count descending, then by name.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 20, "maximum": 20, "minimum": 1, "description": "Maximum results, 1-20. Default 20." }, "query": { "type": "string", "pattern": "^[A-Za-z0-9 &.,'()/#+-]+$", "maxLength": 64, "minLength": 2, "description": "Part of the operator name, e.g. formentera. 2-64 characters." } }, "additionalProperties": false }arguments 23 lineslist_operator_wells unknown never probed
Lists one operator's wellbore claims from the publication, filtered by outcome (AFFECTED, APPROACHING or ALL; default AFFECTED) and sorted by Commission-published plugging cost descending, unpriced wellbores last, then by API number. Returns one page of at most 100 rows plus the number matching and the Commission-published cost total over all matching rows (the same on every page). When more rows remain, next_cursor is set: pass it back as cursor, with the same operator_number and outcome, for the next page. A cursor is bound to the publication root that issued it.
{ "type": "object", "required": [ "operator_number" ], "properties": { "limit": { "type": "integer", "default": 25, "maximum": 100, "minimum": 1, "description": "Maximum rows on this page, 1-100. Default 25." }, "cursor": { "type": "string", "maxLength": 512, "minLength": 1, "description": "next_cursor from the previous page, unchanged. Omit for the first page. Refused when it was issued for another publication root, operator or outcome." }, "outcome": { "enum": [ "AFFECTED", "APPROACHING", "ALL" ], "type": "string", "default": "AFFECTED", "description": "AFFECTED: affected at the evaluation date. APPROACHING: not affected then but affected by 2042-09-01 (compliance-plan horizon). ALL: every claim. Default AFFECTED." }, "operator_number": { "type": "string", "pattern": "^\\d{6}$", "description": "Six-digit Railroad Commission of Texas operator number, with leading zeros (e.g. 276959)." } }, "additionalProperties": false }arguments 37 linesget_operator_exposure unknown never probed
Returns one operator's SB 1150 screening exposure from the publication, by six-digit Railroad Commission of Texas operator number: wellbore claim counts (affected, approaching by 2042-09-01 (compliance-plan horizon), review, contested, shared), the Commission-published plugging cost summed over affected wellbores with its rate label, the crossing schedule by year as published and, on editions that carry the Full Wellbore cross-check, the affected claims whose wellbore that file flags as plugged (a cross-check only; it changes no outcome, count or cost).
{ "type": "object", "required": [ "operator_number" ], "properties": { "operator_number": { "type": "string", "pattern": "^\\d{6}$", "description": "Six-digit Railroad Commission of Texas operator number, with leading zeros (e.g. 276959)." } }, "additionalProperties": false }arguments 14 linesget_well unknown never probed
Returns one wellbore's screening record by its 8-digit API number as the Commission's Inactive Well Aging Report records it (county code + unique number, no 42 state prefix): lease, well number, district, county, months inactive, oldest well record date (RRC), screening outcome, date affected, per-operator evaluations, Commission-published plugging cost with the per-foot rate it was computed from (fiscal year, district, USD per foot) when the edition publishes it, the Full Wellbore plug flag and latest W-3 plug date as a cross-check when the edition carries it (it changes no outcome, count or cost), and source line references.
{ "type": "object", "required": [ "api" ], "properties": { "api": { "type": "string", "pattern": "^\\d{8}$", "description": "Eight-digit API number as recorded in the IWAR: county code + unique number, no 42 prefix, no dashes (e.g. 00100001)." } }, "additionalProperties": false }arguments 14 linesscreen_operators unknown never probed
Screens up to 200 Railroad Commission of Texas operator numbers at once and returns one row per requested operator, in request order: inactive wellbores on the IWAR, affected, approaching by 2042-09-01 (compliance-plan horizon), contested, review and shared claims, Commission-published plugging cost on affected wellbores with its rate label, unpriced affected count, on editions that carry the Full Wellbore cross-check the affected claims whose wellbore that file flags as plugged (a cross-check only; it changes no outcome, count or cost), the crossing schedule by bucket (empty buckets left out of the rows), the raw P-5 status code, and a 16 TAC §3.78 blanket-assurance floor computed from inactive wells only (a lower bound, not a bond amount). Operators not in the publication come back as found:false rows. Includes totals over the found rows.
{ "type": "object", "required": [ "operator_numbers" ], "properties": { "operator_numbers": { "type": "array", "items": { "type": "string", "pattern": "^\\d{1,6}$" }, "maxItems": 200, "minItems": 1, "description": "1-200 Railroad Commission of Texas operator numbers as strings (e.g. [\"276959\", \"760218\"]). Shorter numeric strings are left-padded to 6 digits; duplicates are removed, keeping the first occurrence." } }, "additionalProperties": false }arguments 19 linesscreen_book unknown never probed
Screens a surety broker's book of up to 25 Railroad Commission of Texas operator numbers (principals) with the surety-book-v1 semantics: one row per principal in request order with the P-5 letter verbatim (A labelled active, D delinquent, any other letter unlabelled), claims on file, AFFECTED on the evaluation date, approaching within 24 months, the Commission-published cost proxy with the priced claim count and the rate label read from the publication's cost_rate_basis (a fiscal year's Commission rates, or the publication's own label verbatim when it establishes no table year), unpriced claims, the Full Wellbore flagged counts (a cross-check only) and the 16 TAC §3.78 blanket floor from inactive wells only (a lower bound, not a bond amount). Book totals are given only where a sum is valid; unpriced claims and the floors are NOT_SUMMED, with the reason. Wellbores two principals of the book both claim are disclosed with the claims and cost the totals count more than once. A principal not in the publication refuses the whole book rather than leave a row out.
{ "type": "object", "required": [ "operator_numbers" ], "properties": { "operator_numbers": { "type": "array", "items": { "type": "string", "pattern": "^\\d{6}$", "description": "Six-digit Railroad Commission of Texas operator number, with leading zeros (e.g. 276959)." }, "maxItems": 25, "minItems": 1, "description": "1-25 six-digit Railroad Commission of Texas operator numbers as strings, each once (e.g. [\"276959\", \"760218\"]). The rows keep this order." } }, "additionalProperties": false }arguments 20 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id96a1323f61b176d9.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/96a1323f61b176d9/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/96a1323f61b176d9?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.