# catalejo (pypi · catalejo)

Filings from Spain's securities regulator (CNMV): price-sensitive and regulatory announcements.

- Trust score: 49/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `catalejo`: 49/100 (this document), [markdown](https://verifymcp.io/servers/polfananas-catalejo/catalejo.md), [page](https://verifymcp.io/servers/polfananas-catalejo/catalejo)

## Channel facts

- Registry: `pypi`
- Package: `catalejo`
- Version: `0.1.3`
- 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-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - 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.
  - 0 of 10 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to polfananas/catalejo).
  - 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 package installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, 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 catalejo MCP server?

catalejo runs locally as a PyPI package, launched with uvx catalejo mcp. The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs. 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 polfananas-catalejo -- uvx catalejo mcp
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Cursor

```json
{
  "mcpServers": {
    "polfananas-catalejo": {
      "command": "uvx",
      "args": [
        "catalejo",
        "mcp"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### VS Code

```json
{
  "servers": {
    "polfananas-catalejo": {
      "command": "uvx",
      "args": [
        "catalejo",
        "mcp"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Codex

```bash
codex mcp add polfananas-catalejo -- uvx catalejo mcp
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "polfananas-catalejo": {
      "type": "local",
      "command": [
        "uvx",
        "catalejo",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### OpenClaw

```bash
openclaw mcp add polfananas-catalejo --command uvx --arg catalejo --arg mcp
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Hermes

```yaml
mcp_servers:
  polfananas-catalejo:
    command: "uvx"
    args: ["catalejo", "mcp"]
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Netclaw

```json
{
  "McpServers": {
    "polfananas-catalejo": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "catalejo",
        "mcp"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Vellum

```bash
assistant mcp add polfananas-catalejo -t stdio -c uvx -a catalejo mcp
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Other

```json
{
  "mcpServers": {
    "polfananas-catalejo": {
      "command": "uvx",
      "args": [
        "catalejo",
        "mcp"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

## 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-21 (score 49, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-20 (score 34, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-18 (score 49, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 34, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-15 (score 49, 0)

- [functional] Package version: 0.1.1 → 0.1.3

### 2026-11-12 (score 49)

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/polfananas-catalejo/catalejo#diagnostics

## Score history

- 2026-11-21: 49
- 2026-11-20: 34
- 2026-11-19: 49
- 2026-11-18: 49
- 2026-11-17: 34
- 2026-11-16: 49
- 2026-11-15: 49
- 2026-11-14: 49
- 2026-11-13: 49
- 2026-11-12: 49

## Common questions

### What is the catalejo MCP server?

catalejo is an MCP server listed in the public MCP registry as io.github.polfananas/catalejo. Filings from Spain's securities regulator (CNMV): price-sensitive and regulatory announcements. This page covers its PyPI package (catalejo).

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

catalejo scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 catalejo MCP server still maintained?

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

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

### What did VerifyMCP test on the catalejo MCP server?

VerifyMCP ran 9 checks on catalejo, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about catalejo: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/catalejo/
- Socket report: https://socket.dev/pypi/package/catalejo
- Repository: https://github.com/polfananas/catalejo
- Changelog RSS feed: https://verifymcp.io/servers/polfananas-catalejo/catalejo.xml
- Changelog JSON feed: https://verifymcp.io/servers/polfananas-catalejo/catalejo/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/polfananas-catalejo/catalejo.json
- HTML version of this page: https://verifymcp.io/servers/polfananas-catalejo/catalejo
