mcpbeat Sign in

WellState Labs SB 1150 Screening (read-only) MCP Server

by wellstatelabs Your server? Claim it
not responding

WellState Labs SB 1150 Screening (read-only) is listed as active in the registry but did not answer our last check. It exposes 9 tools.

Signed Texas SB 1150 screens. Cost proxies, not ARO, not legal determinations, not bond amounts.

Uptime history 9 days of history · worst day 0%
9 days agonow
3.3%
Uptime 24h
3 of 91 checks
9
Tools
read from the server
295 ms
Response time
average over 24h
open, no key
Access
streamable-http

WellState Labs SB 1150 Screening (read-only) does not always answer

Over the last week it answered 4.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add sb1150-screening --transport http https://mcp.wellstatelabs.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.wellstatelabs.com/mcp
~/.codex/config.toml
[mcp_servers.sb1150-screening]
url = "https://mcp.wellstatelabs.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sb1150-screening": {
      "url": "https://mcp.wellstatelabs.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "sb1150-screening": {
      "type": "http",
      "url": "https://mcp.wellstatelabs.com/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

operator
get_operator_exposure
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).
list_operator_wells
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.
screen
screen_book
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.
screen_operators
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.
operators
search_operators
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.
plug
get_plug_record
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.
publication
get_publication
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.
verify
verify_publication
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.
well
get_well
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.wellstatelabs.com/mcp streamable-http answering 79 ms 10 min ago

Alternatives to WellState Labs SB 1150 Screening (read-only)

same job, measured the same way
Acquis
by acquislaw

Verified EU law: verbatim, signed provisions with EUR-Lex links. Read-only, not legal advice.

answering
Arc & Ledger Tax Reference
by arcandledger

Read-only US tax reference for notices, deadlines, filing screens, and clearly labeled estimates.

13 tools answering
TRA
by bijectivelabs

Read-only gates of autonomous trading agents with deterministic execution: cost, data, validation.

834 installs/wk local only
OFAC SDN Screening
by bonissystems

Screen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination.

2 tools answering
trading-research-agents
by bijectivelabs

Read-only gates of autonomous trading agents with deterministic execution: cost, data, validation.

997 installs/wk local only
SmartCLI — drive terminal TUIs
by dwgx

Let agents drive vim, htop, lazygit: send keys, wait on screen state, read the rendered cell grid.

139 installs/wk local only
Agent Core
by kinbinghua-lgtm

Deterministic computation tools for AI agents. Zero dependencies, no network, read-only.

43 installs/wk local only
RegAI Legal MCP (Taiwan)
by regai

Taiwan law and court decisions for your AI: statutes, articles and rulings, read-only.

answering

WellState Labs SB 1150 Screening (read-only) — questions

Answers built from our own checks of this server.

What can WellState Labs SB 1150 Screening (read-only) do?
It exposes 9 tools, read directly from the server on our last check. Among them: get_operator_exposure, get_plug_record, get_publication, get_well, list_operator_wells, screen_book and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is WellState Labs SB 1150 Screening (read-only) mostly used for?
Its tools cluster around screen and operator. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is WellState Labs SB 1150 Screening (read-only) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 3 of 91 checks got a reply (3.3%), average response time 295 ms. The bar chart above shows every period we have measured.
The registry lists WellState Labs SB 1150 Screening (read-only) as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect WellState Labs SB 1150 Screening (read-only)?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does WellState Labs SB 1150 Screening (read-only) need an API key?
No. WellState Labs SB 1150 Screening (read-only) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is WellState Labs SB 1150 Screening (read-only)?
It answers our handshake in 295 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.