# Trudex (remote · trudex.dev)

Verified Texas business records for AI agents: entities, licenses, openings and enforcement history.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-07

## Components

- remote · `trudex.dev`: 39/100, [markdown](https://verifymcp.io/servers/dev-trudex-trudex/api-mcp.md), [page](https://verifymcp.io/servers/dev-trudex-trudex/api-mcp)
- remote · `trudex.dev`: 86/100 (this document), [markdown](https://verifymcp.io/servers/dev-trudex-trudex/api-mcp-open.md), [page](https://verifymcp.io/servers/dev-trudex-trudex/api-mcp-open)

## Channel facts

- Endpoint: `https://trudex.dev/api/mcp/open`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `0.2.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-07.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1928 tokens (~275/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 Trudex MCP server?

Trudex is a hosted endpoint at https://trudex.dev/api/mcp/open, 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 dev-trudex-trudex 'https://trudex.dev/api/mcp/open'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-trudex-trudex": {
      "url": "https://trudex.dev/api/mcp/open"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-trudex-trudex": {
      "type": "http",
      "url": "https://trudex.dev/api/mcp/open"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-trudex-trudex]
url = "https://trudex.dev/api/mcp/open"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-trudex-trudex": {
      "type": "remote",
      "url": "https://trudex.dev/api/mcp/open",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-trudex-trudex --url 'https://trudex.dev/api/mcp/open' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-trudex-trudex:
    url: "https://trudex.dev/api/mcp/open"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-trudex-trudex": {
      "Transport": "http",
      "Url": "https://trudex.dev/api/mcp/open"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-trudex-trudex -t streamable-http -u 'https://trudex.dev/api/mcp/open'
```

### Other

```json
{
  "mcpServers": {
    "dev-trudex-trudex": {
      "type": "http",
      "url": "https://trudex.dev/api/mcp/open"
    }
  }
}
```

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-06 (score 86, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 85, 0)

- [security] Tool “find_new_activity” rewrote its description, which is the text the model reads
- [cosmetic] “find_new_activity” added an optional parameter “min_confidence”
- [cosmetic] “find_new_activity” added an optional parameter “opening_types”

### 2026-11-03 (score 85, +1)

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

### 2026-11-01 (score 84, +1)

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

### 2026-10-30 (score 83, +1)

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

### 2026-10-28 (score 82, +1)

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

### 2026-10-26 (score 81, +1)

- [security] Tool “find_new_activity” rewrote its description, which is the text the model reads
- [cosmetic] “find_new_activity” reworded the description of “city”
- [cosmetic] “find_new_activity” reworded the description of “since”

### 2026-10-24 (score 80, +1)

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

## MCP tools (7)

### `resolve_business` (~220 tokens)

Identify a Texas business

Which Texas business is this? Turns a brand, trade name or legal name into ranked candidates with entity_id, legal name, trade names, an address, confidence (0-1) and match_reasons. Texas only; businesses registered with the Texas Comptroller or TABC, refreshed nightly from Texas state datasets. status is match, possible, ambiguous (add a city or address) or not_found; weak guesses are never returned. Example: {"name": "Heim Barbecue", "city": "Fort Worth"}. Pass the entity_id to the other tools.

Input parameters:

- `address` (string): Street address, e.g. "1109 W Magnolia Ave".
- `city` (string): Texas city, e.g. "Fort Worth". Strongly improves ranking.
- `limit` (integer): Candidates to return, 1-25. Default 10.
- `name` (string, required): Business, brand or legal name, e.g. "Heim Barbecue".
- `zip` (string): ZIP code, e.g. "76104".

### `get_entity` (~323 tokens)

Legal profile of a Texas business

What is this business legally, and is it in good standing? Returns the legal profile for an entity_id: legal name, organization type, SOS file number, charter date, SOS status, right to transact business (forfeited means franchise tax forfeiture), mailing address, and counts of locations, TABC licenses and affiliates. Also returns state_permits (Comptroller fuels, IFTA, interstate trucker, tobacco, hotel occupancy tax and direct-pay permits, flagging suspended permits and hotel locations gone out of business) and tabc_credit_law_delinquency (appearances on TABC's Credit Law Delinquent List: a wholesaler reported unpaid alcohol deliveries, so the retailer may buy for cash only while listed), federal_exclusions (active SAM.gov debarments and suspensions, shown only where the excluded firm has this entity's exact name and street address; an empty list is not a clearance), motor_carriers (FMCSA USDOT numbers with the same name and street address, each flagging an out-of-service order in force; get_motor_carriers has the full record), and labor_summary (five-year OSHA and wage-and-hour totals for records with the same name and street address; get_labor_record has the records). Texas only; businesses registered with the Texas Comptroller or TABC, refreshed nightly from Texas state datasets. Example: {"entity_id": "32057926266"}.

Input parameters:

- `entity_id` (string, required): entity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.

### `find_affiliates` (~204 tokens)

Related Texas businesses

Which other entities are likely under common control with this one, and who did it take over from or hand over to? Returns affiliates with relation_type (shared trade name, shared mailing address, similar name in the same city), confidence and the evidence that matched; plus took_over_from and taken_over_by: businesses that followed one another at the same premises under the same or a similar trade name (a sale or a reorganisation, not common control), each handover dated. Texas only; businesses registered with the Texas Comptroller or TABC, refreshed nightly from Texas state datasets. Inferred links, not ownership records. Example: {"entity_id": "32057926266"}.

Input parameters:

- `entity_id` (string, required): entity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.
- `min_confidence` (number): Only affiliates at or above this confidence, 0.5-1. Default 0.5.

### `get_locations` (~188 tokens)

Locations of a Texas business

Where does this business operate? Returns its locations (sales-tax outlets, plus closed ones known from mixed-beverage receipts) with trade name, address, NAICS code, permit and first-sale dates, and whether each is current or ended. Texas only; businesses registered with the Texas Comptroller or TABC, refreshed nightly from Texas state datasets. Example: {"entity_id": "32057926266", "include_affiliates": true}.

Input parameters:

- `entity_id` (string, required): entity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.
- `include_affiliates` (boolean): Also include affiliated entities (likely common control, confidence >= 0.5). Default false.
- `limit` (integer): Locations to return, 1-50. Default 50.
- `status` (string): Only current or only ended locations. Default both.

### `get_licenses` (~207 tokens)

Alcohol licenses of a Texas business

What alcohol licenses does this business hold or has it held? Returns TABC licenses with type, trade name, status and issue, status-change and expiration dates, each with how it was linked to the entity and the link's confidence, and any TABC Credit Law Delinquent List appearances (unpaid wholesaler credit). Texas only; businesses registered with the Texas Comptroller or TABC, refreshed nightly from Texas state datasets. Example: {"entity_id": "32057926266", "active_only": true}.

Input parameters:

- `active_only` (boolean): Only licenses whose primary status is Active. Default false.
- `entity_id` (string, required): entity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.
- `include_affiliates` (boolean): Also include affiliated entities (likely common control, confidence >= 0.5). Default false.
- `limit` (integer): Licenses to return, 1-50. Default 50.

### `get_timeline` (~190 tokens)

History of a Texas business

What has happened to this business, and when? Returns dated events, newest first: formed, location opened or closed, licensed, license surrendered or expired, location transferred between entities, license applied for. Texas only; businesses registered with the Texas Comptroller or TABC, refreshed nightly from Texas state datasets. Each event names its source record. Example: {"entity_id": "32057926266", "include_affiliates": true}.

Input parameters:

- `entity_id` (string, required): entity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.
- `include_affiliates` (boolean): Also include affiliated entities (likely common control, confidence >= 0.5). Default false.
- `limit` (integer): Events to return, 1-50. Default 50.
- `since` (string): Only events on or after this date, YYYY-MM-DD.

### `find_new_activity` (~439 tokens)

New and opening businesses in a Texas area

What is opening in this Texas city or ZIP? Returns pre-opening and new-outlet signals since a date, one row per address, each with a stage (applied, licensed, permitted, opened) and its source records. With no city or zip it searches all of Texas over the last 7 days (31 at most). Texas only; businesses registered with the Texas Comptroller or TABC, refreshed nightly from Texas state datasets. Filter by NAICS code or category (restaurant, bar, liquor_store, convenience_store, brewery_winery_distillery). Each row carries opening_context: what kind of opening it is (takeover of a closed business's site, ownership_change, expansion by an owner with other locations, existing_business, new_owner, ...), a confidence (high, medium, low) and a plain-language reason. Filter with opening_types and min_confidence. entity_id is null on rows owned by an individual or not linked to a taxpayer. Example: {"city": "Fort Worth", "since": "2026-07-01", "category": "restaurant", "opening_types": ["takeover"], "min_confidence": "high"}.

Input parameters:

- `category` (string): Business category. Ignored when naics is given.
- `city` (string): Texas city, e.g. "Fort Worth". Omit city and zip for all of Texas.
- `limit` (integer): Addresses to return, 1-50. Default 25.
- `min_confidence` (string): Keep only rows whose opening_context confidence is at least this.
- `naics` (string): NAICS code or prefix, e.g. "722511" (full-service restaurants).
- `opening_types` (array): Keep only these kinds of opening, e.g. ["takeover", "ownership_change"]. Drops rows with no opening_context (owned by individuals).
- `since` (string): Earliest signal date, YYYY-MM-DD, within the last two years (31 days statewide). Default 90 days ago (7 statewide).
- `zip` (string): ZIP code, e.g. "76104".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-trudex-trudex/api-mcp-open#diagnostics

## Score history

- 2026-11-07: 86
- 2026-11-06: 86
- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 82
- 2026-10-28: 82
- 2026-10-27: 81
- 2026-10-26: 81
- 2026-10-25: 80
- 2026-10-24: 80
- 2026-10-23: 79
- 2026-10-22: 79
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 76
- 2026-10-15: 76
- 2026-10-14: 76

## Common questions

### What is the Trudex MCP server?

Trudex is an MCP server listed in the public MCP registry as dev.trudex/trudex. Verified Texas business records for AI agents: entities, licenses, openings and enforcement history. This page covers its hosted endpoint (https://trudex.dev/api/mcp/open).

### Is the Trudex MCP server safe to use?

Trudex scores 86 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 Trudex MCP server expose?

Trudex exposes 7 tools: resolve_business, get_entity, find_affiliates, get_locations, get_licenses, and 2 more. Their descriptions and schemas cost roughly 1,771 tokens of context every time the server is loaded.

### Does the Trudex MCP server require authentication?

Yes. Trudex asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Trudex MCP server still maintained?

Trudex is still listed as active in the MCP registry. We last reached this channel on 7 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 Trudex MCP server?

VerifyMCP ran 13 checks on Trudex, 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://trudex.dev/api/mcp/open
- Website: https://trudex.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-trudex-trudex/api-mcp-open.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-trudex-trudex/api-mcp-open/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-trudex-trudex/api-mcp-open.json
- HTML version of this page: https://verifymcp.io/servers/dev-trudex-trudex/api-mcp-open