License Verify MCP vs Texas Code
A side-by-side look at the License Verify MCP and Texas Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose License Verify MCP for legal work as a local process; choose Texas Code for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose License Verify MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
jurisdiction, license_number, business_name.
Choose Texas Code when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You want tools like
tx_statute, tx_codes.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 59/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View License Verify MCP | View Texas Code |
Tools & capabilities
License Verify MCP tools 3
jurisdictionlicense_numberbusiness_name
Texas Code tools 2
tx_statuteGet the FULL TEXT of a section of the Texas Statutes — Texas state law — by citation. "Texas Penal Code 19.02" is code "PE", section "19.02" (murder). Returns the statutory text and its amendment history. Keyless. Use for "what does Texas Penal Code 19.02 say", "text of Tex. Fam. Code 6.001", or to check a Texas statute a case relies on.tx_codesList the Texas codes with their subjects — Penal Code is PE, Family Code is FA, Tax Code is TX, and so on. Keyless. Use when you know the subject but not the code abbreviation, before calling tx_statute.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
License Verify MCP
{
"mcpServers": {
"lmaniraruta-license-verify-mcp": {
"command": "npx",
"args": [
"-y",
"apify"
]
}
}
}
Texas Code
{
"mcpServers": {
"texas-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-texas-code"
]
}
}
}
Frequently asked questions
License Verify MCP is categorized under Legal and uses a local stdio subprocess. Texas Code belongs to Legal and uses a local stdio subprocess. Pick License Verify MCP for legal work and Texas Code for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
License Verify MCP is listed as a paid service. Auth: no auth required. Texas Code has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lmaniraruta-license-verify-mcp and texas-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, License Verify MCP has a quality signal of 59/100 (Good) with 5 views, 0 installs and 0 GitHub stars. Texas Code has 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars.