Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Trudex

REMOTE · TRUDEX.DEV · 2 COMPONENTS

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

+3 this week 86 Trust /100

Last scanned (10 hours ago)

Scores higher than 92% of remote servers

Reachable. Last reached 7 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Tool “find_new_activity” rewrote its description, which is the text the model reads security
    • “find_new_activity” added an optional parameter “min_confidence” cosmetic
    • “find_new_activity” added an optional parameter “opening_types” cosmetic
  • 3 Nov 26 +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.

  • 1 Nov 26 +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.

  • 30 Oct 26 +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.

  • 28 Oct 26 +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.

  • 26 Oct 26 +1
    • Tool “find_new_activity” rewrote its description, which is the text the model reads security
    • “find_new_activity” reworded the description of “city” cosmetic
    • “find_new_activity” reworded the description of “since” cosmetic
  • 24 Oct 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Nov 2026 · Probed https://trudex.dev/api/mcp/open

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=trudex.dev CN=YR2,O=Let's Encrypt,C=US 7 Oct 2026 5 Jan 2027 RSA 2048 SHA256-RSA 5f26ec7c6bee0eb337eab4f20cf4d747cca
SANs: trudex.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of trudex.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
trudex.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://trudex.dev/api/mcp/open Verified 200
http (plaintext) http://trudex.dev/api/mcp/open HTTPS enforced 308 https://trudex.dev/api/mcp/open
MCP tools · 7 exposed · ~1,771 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_affiliates ~204

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"}.

NameTypeReqDescription
entity_idstringyesentity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.
min_confidencenumber–Only affiliates at or above this confidence, 0.5-1. Default 0.5.

No output schema declared.

No examples provided.

find_new_activity ~439

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"}.

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

No output schema declared.

No examples provided.

get_entity ~323

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"}.

NameTypeReqDescription
entity_idstringyesentity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.

No output schema declared.

No examples provided.

get_licenses ~207

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}.

NameTypeReqDescription
active_onlyboolean–Only licenses whose primary status is Active. Default false.
entity_idstringyesentity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.
include_affiliatesboolean–Also include affiliated entities (likely common control, confidence >= 0.5). Default false.
limitinteger–Licenses to return, 1-50. Default 50.

No output schema declared.

No examples provided.

get_locations ~188

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}.

NameTypeReqDescription
entity_idstringyesentity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.
include_affiliatesboolean–Also include affiliated entities (likely common control, confidence >= 0.5). Default false.
limitinteger–Locations to return, 1-50. Default 50.
statusstring–Only current or only ended locations. Default both.

No output schema declared.

No examples provided.

get_timeline ~190

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}.

NameTypeReqDescription
entity_idstringyesentity_id from resolve_business (11-digit Texas taxpayer number), or a 10-digit SOS file number.
include_affiliatesboolean–Also include affiliated entities (likely common control, confidence >= 0.5). Default false.
limitinteger–Events to return, 1-50. Default 50.
sincestring–Only events on or after this date, YYYY-MM-DD.

No output schema declared.

No examples provided.

resolve_business ~220

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.

NameTypeReqDescription
addressstring–Street address, e.g. "1109 W Magnolia Ave".
citystring–Texas city, e.g. "Fort Worth". Strongly improves ranking.
limitinteger–Candidates to return, 1-25. Default 10.
namestringyesBusiness, brand or legal name, e.g. "Heim Barbecue".
zipstring–ZIP code, e.g. "76104".

No output schema declared.

No examples provided.

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.

remote · trudex.dev

# add to Claude Code
claude mcp add --transport http dev-trudex-trudex 'https://trudex.dev/api/mcp/open'
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.