# Lex API MX (pypi · lex-api-mx-mcp)

Legislación federal mexicana vigente con fuente, checksum y vigencia para agentes de IA

- Trust score: 24/100 (low)
- Change this week: −15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-20

## Components

- pypi · `lex-api-mx-mcp`: 24/100 (this document), [markdown](https://verifymcp.io/servers/julio-patron-lex-api-mx/lex-api-mx-mcp.md), [page](https://verifymcp.io/servers/julio-patron-lex-api-mx/lex-api-mx-mcp)

## Channel facts

- Registry: `pypi`
- Package: `lex-api-mx-mcp`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-10-20.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the Lex API MX MCP server?

Lex API MX runs locally as a PyPI package, launched with uvx lex-api-mx-mcp. 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 julio-patron-lex-api-mx -- uvx lex-api-mx-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "julio-patron-lex-api-mx": {
      "command": "uvx",
      "args": [
        "lex-api-mx-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "julio-patron-lex-api-mx": {
      "command": "uvx",
      "args": [
        "lex-api-mx-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add julio-patron-lex-api-mx -- uvx lex-api-mx-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "julio-patron-lex-api-mx": {
      "type": "local",
      "command": [
        "uvx",
        "lex-api-mx-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add julio-patron-lex-api-mx --command uvx --arg lex-api-mx-mcp
```

### Hermes

```yaml
mcp_servers:
  julio-patron-lex-api-mx:
    command: "uvx"
    args: ["lex-api-mx-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "julio-patron-lex-api-mx": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "lex-api-mx-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add julio-patron-lex-api-mx -t stdio -c uvx -a lex-api-mx-mcp
```

### Other

```json
{
  "mcpServers": {
    "julio-patron-lex-api-mx": {
      "command": "uvx",
      "args": [
        "lex-api-mx-mcp"
      ]
    }
  }
}
```

## 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-10-15 (score 24, 0)

- [security] Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- [functional] Package version: 0.3.0 → 0.3.1

### 2026-10-14 (score 24, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-13 (score 39, 0)

- [functional] Package version: 0.2.1 → 0.3.0

### 2026-10-12 (score 39)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/julio-patron-lex-api-mx/lex-api-mx-mcp#diagnostics

## Score history

- 2026-10-20: 24
- 2026-10-19: 24
- 2026-10-18: 24
- 2026-10-17: 24
- 2026-10-16: 24
- 2026-10-15: 24
- 2026-10-14: 24
- 2026-10-13: 39
- 2026-10-12: 39

## Common questions

### What is the Lex API MX MCP server?

Lex API MX is an MCP server listed in the public MCP registry as io.github.Julio-Patron/lex-api-mx. Legislación federal mexicana vigente con fuente, checksum y vigencia para agentes de IA. This page covers its PyPI package (lex-api-mx-mcp).

### Is the Lex API MX MCP server safe to use?

Lex API MX scores 24 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 October 2026. 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.

### Is the Lex API MX MCP server still maintained?

Lex API MX is still listed as active in the MCP registry. We last reached this channel on 20 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Lex API MX MCP server under?

Lex API MX declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/lex-api-mx-mcp/
- Socket report: https://socket.dev/pypi/package/lex-api-mx-mcp
- Repository: https://github.com/Julio-Patron/lexapi-mx
- Website: https://lexapi.mx/
- Changelog RSS feed: https://verifymcp.io/servers/julio-patron-lex-api-mx/lex-api-mx-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/julio-patron-lex-api-mx/lex-api-mx-mcp.json
- HTML version of this page: https://verifymcp.io/servers/julio-patron-lex-api-mx/lex-api-mx-mcp