# WellState Labs SB 1150 Screening (read-only) (remote · mcp.wellstatelabs.com)

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

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.wellstatelabs.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-wellstatelabs-sb1150-screening/mcp.md), [page](https://verifymcp.io/servers/com-wellstatelabs-sb1150-screening/mcp)

## Channel facts

- Endpoint: `https://mcp.wellstatelabs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2786 tokens (~232/item across 12 items; 9 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the WellState Labs SB 1150 Screening (read-only) MCP server?

WellState Labs SB 1150 Screening (read-only) is a hosted endpoint at https://mcp.wellstatelabs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-wellstatelabs-sb1150-screening 'https://mcp.wellstatelabs.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-wellstatelabs-sb1150-screening": {
      "url": "https://mcp.wellstatelabs.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-wellstatelabs-sb1150-screening": {
      "type": "http",
      "url": "https://mcp.wellstatelabs.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-wellstatelabs-sb1150-screening]
url = "https://mcp.wellstatelabs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wellstatelabs-sb1150-screening": {
      "type": "remote",
      "url": "https://mcp.wellstatelabs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wellstatelabs-sb1150-screening --url 'https://mcp.wellstatelabs.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wellstatelabs-sb1150-screening:
    url: "https://mcp.wellstatelabs.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-wellstatelabs-sb1150-screening": {
      "Transport": "http",
      "Url": "https://mcp.wellstatelabs.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-wellstatelabs-sb1150-screening -t streamable-http -u 'https://mcp.wellstatelabs.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-wellstatelabs-sb1150-screening": {
      "type": "http",
      "url": "https://mcp.wellstatelabs.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 74)

First indexed and scored.

## MCP tools (9)

### `get_publication` (~153 tokens)

Get publication details

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.

Output parameters:

- `affected_commission_published_cost` (object)
- `basis` (string)
- `boundary` (string)
- `contract_version` (string)
- `cost_rate_basis`
- `counts` (object)
- `data_file_count` (integer)
- `evaluation_date` (string)
- `full_wellbore_crosscheck`
- `how_to_cite` (string)
- `plug_record_basis`
- `produced_at` (string)
- `publication_id` (string)
- `publication_root` (string)
- `rule` (object)
- `source_files` (array)
- `terms` (string)
- `verification` (object)
- `verified` (boolean)
- `vintage` (object)

### `verify_publication` (~131 tokens)

Verify publication hashes

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.

Input parameters:

- `paths` (array): Manifest data_files paths to report (e.g. data/operator.ndjson). Omit to report every file.

Output parameters:

- `all_match` (boolean)
- `boundary` (string)
- `derived` (object)
- `elapsed_ms` (integer)
- `files` (array)
- `files_checked` (integer)
- `files_matched` (integer)
- `full_wellbore_crosscheck`
- `independent_check` (object)
- `publication_root` (string)
- `root` (object)
- `terms` (string)

### `get_operator_exposure` (~155 tokens)

Get operator SB 1150 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).

Input parameters:

- `operator_number` (string, required): Six-digit Railroad Commission of Texas operator number, with leading zeros (e.g. 276959).

Output parameters:

- `affected_cost` (object)
- `boundary` (string)
- `count_unit` (string)
- `counts` (object)
- `crossing_schedule` (array)
- `crossing_schedule_basis` (object)
- `display_name` (string)
- `full_wellbore_crosscheck_note` (string)
- `link` (string)
- `name` (string)
- `operator_number` (string)
- `publication_root` (string)
- `terms` (string)

### `search_operators` (~100 tokens)

Search operators by name

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.

Input parameters:

- `limit` (integer): Maximum results, 1-20. Default 20.
- `query` (string, required): Part of the operator name, e.g. formentera. 2-64 characters.

Output parameters:

- `boundary` (string)
- `publication_root` (string)
- `query` (string)
- `results` (array)
- `returned` (integer)
- `terms` (string)
- `total_matches` (integer)
- `truncated` (boolean)

### `get_well` (~188 tokens)

Get wellbore screening record

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.

Input parameters:

- `api` (string, required): Eight-digit API number as recorded in the IWAR: county code + unique number, no 42 prefix, no dashes (e.g. 00100001).

Output parameters:

- `affected_from` (object)
- `api` (string)
- `approaching` (boolean): Not AFFECTED at the evaluation date, and AFFECTED on the same rule, with no other change, by 2042-09-01 (compliance-plan horizon).
- `boundary` (string)
- `commission_cost` (object)
- `cost_basis`
- `county`
- `district`
- `evaluations` (array)
- `field_name`
- `full_wellbore_crosscheck`
- `lease_name`
- `link` (string)
- `months_inactive`
- `oldest_well_record_date` (object)
- `operator` (object)
- `outcome` (string)
- `plug_status`
- `publication_root` (string)
- `source_lines` (array)
- `source_lines_total` (integer)
- `terms` (string)
- `total_depth_ft`
- `well_number`
- `well_type`

### `list_operator_wells` (~269 tokens)

List an operator's wellbores

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.

Input parameters:

- `cursor` (string): next_cursor from the previous page, unchanged. Omit for the first page. Refused when it was issued for another publication root, operator or outcome.
- `limit` (integer): Maximum rows on this page, 1-100. Default 25.
- `operator_number` (string, required): Six-digit Railroad Commission of Texas operator number, with leading zeros (e.g. 276959).
- `outcome` (string): AFFECTED: affected at the evaluation date. APPROACHING: not affected then but affected by 2042-09-01 (compliance-plan horizon). ALL: every claim. Default AFFECTED.

Output parameters:

- `boundary` (string)
- `display_name` (string)
- `link` (string)
- `matching_commission_published_total` (object)
- `matching_unpriced_count` (integer)
- `next_cursor` (string|null): Pass as cursor for the next page; null on the last page.
- `offset` (integer): Position of this page's first row in the full sorted listing, from 0.
- `operator_number` (string)
- `outcome_filter` (string)
- `publication_root` (string)
- `returned` (integer)
- `sort` (string)
- `terms` (string)
- `total_matching` (integer)
- `truncated` (boolean): True when rows remain after this page.
- `wells` (array)

### `screen_operators` (~247 tokens)

Screen a list of 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.

Input parameters:

- `operator_numbers` (array, required): 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.

Output parameters:

- `blanket_floor_basis` (object)
- `boundary` (string)
- `cost_label` (string)
- `count_unit` (object)
- `duplicates_removed` (integer)
- `full_wellbore_crosscheck_note` (string)
- `p5_status_code_note` (string)
- `publication_root` (string)
- `requested` (integer)
- `rows` (array)
- `screened` (integer)
- `terms` (string)
- `totals` (object)

### `screen_book` (~284 tokens)

Screen a surety book of principals

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.

Input parameters:

- `operator_numbers` (array, required): 1-25 six-digit Railroad Commission of Texas operator numbers as strings, each once (e.g. ["276959", "760218"]). The rows keep this order.

Output parameters:

- `blanket_floor_note` (string)
- `boundary` (string)
- `cost_note` (string)
- `count_unit` (string)
- `evaluation_date` (string)
- `format_version` (string)
- `full_wellbore_crosscheck_note` (string)
- `iwar_as_of` (string)
- `overlap` (object)
- `p5_note` (string)
- `principals` (integer)
- `publication` (object)
- `publication_root` (string)
- `rate_basis` (object)
- `reliance` (string)
- `rows` (array)
- `terms` (string)
- `totals` (object)
- `within_24_months_by` (string)

### `get_plug_record` (~391 tokens)

Get the 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.

Input parameters:

- `district` (string): 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.
- `first_year` (integer): First calendar year returned. Default: the first year of the plug record's window.
- `last_year` (integer): Last calendar year returned. Default: the last year of the plug record's window.
- `rows_limit` (integer): 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` (integer): Rows to skip before the first one returned, for paging. Default 0.

Output parameters:

- `boundary` (string)
- `contract_version` (string)
- `note` (string)
- `plug_record`
- `publication_root` (string)
- `terms` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-wellstatelabs-sb1150-screening/mcp#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 74

## Common questions

### What is the WellState Labs SB 1150 Screening (read-only) MCP server?

WellState Labs SB 1150 Screening (read-only) is an MCP server listed in the public MCP registry as com.wellstatelabs/sb1150-screening. Signed Texas SB 1150 screens. Cost proxies, not ARO, not legal determinations, not bond amounts. This page covers its hosted endpoint (https://mcp.wellstatelabs.com/mcp).

### Is the WellState Labs SB 1150 Screening (read-only) MCP server safe to use?

WellState Labs SB 1150 Screening (read-only) scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the WellState Labs SB 1150 Screening (read-only) MCP server expose?

WellState Labs SB 1150 Screening (read-only) exposes 9 tools: get_publication, verify_publication, get_operator_exposure, search_operators, get_well, and 4 more. Their descriptions and schemas cost roughly 1,918 tokens of context every time the server is loaded.

### Does the WellState Labs SB 1150 Screening (read-only) MCP server require authentication?

No. We connected to WellState Labs SB 1150 Screening (read-only) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the WellState Labs SB 1150 Screening (read-only) MCP server still maintained?

WellState Labs SB 1150 Screening (read-only) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the WellState Labs SB 1150 Screening (read-only) MCP server?

VerifyMCP ran 13 checks on WellState Labs SB 1150 Screening (read-only), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.wellstatelabs.com/mcp
- Website: https://mcp.wellstatelabs.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-wellstatelabs-sb1150-screening/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wellstatelabs-sb1150-screening/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-wellstatelabs-sb1150-screening/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-wellstatelabs-sb1150-screening/mcp