# Fetter MCP (remote · mcp.fetter.io)

Real-time Python package and vulnerability data for AI coding agents.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp.fetter.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/fetter-io-fetter-mcp/mcp.md), [page](https://verifymcp.io/servers/fetter-io-fetter-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.fetter.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-08-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 341 tokens (~113/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http fetter-io-fetter-mcp https://mcp.fetter.io/mcp
```

### Codex

```toml
[mcp_servers.fetter-io-fetter-mcp]
url = "https://mcp.fetter.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fetter-io-fetter-mcp": {
      "type": "remote",
      "url": "https://mcp.fetter.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fetter-io-fetter-mcp --url https://mcp.fetter.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fetter-io-fetter-mcp:
    url: "https://mcp.fetter.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "fetter-io-fetter-mcp": {
      "type": "http",
      "url": "https://mcp.fetter.io/mcp"
    }
  }
}
```

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-08-03 (score 64, +3)

No change was recorded against any check on this day. Schema Quality & AI Usability went from 66 to 75. Other categories moved too: Stability & Change Management rose 4.

### 2026-08-02 (score 61, −1)

No change was recorded against any check on this day. Schema Quality & AI Usability went from 70 to 66. Other categories moved too: Stability & Change Management rose 3.

### 2026-07-31 (score 62, 0)

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

### 2026-07-30 (score 62, +1)

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

### 2026-07-28 (score 61, +1)

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

### 2026-07-27 (score 60, +1)

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

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (3)

### `lookup` (~208 tokens)

Look up a package by name and (optionally) version number to find which versions are available and/or have vulnerabilities.

Input parameters:

- `cvss_filter` (string): CVSS score filter: "all" to show all vulnerabilities, "max" to show only the maximum observed score, or a number (0.0-10.0) to filter by threshold
- `limit` (integer): When the name is not an exact version, limit the number of recent versions to check.
- `name` (string, required): The package name to look up (e.g., "requests", "numpy>=2.0", "flask==3.0.0"). Note that when an exact "==" version is specified, the `limit` and `retain_passing` parameters have no effect.
- `retain_passing` (boolean): 'When the name is not an exact version, setting this to True will return refernces for all packages, include those with no vulnerabilities (default: false)

### `most_recent_not_vulnerable` (~52 tokens)

Find the most recent version of a package that has no known vulnerabilities.

Input parameters:

- `name` (string, required): The package name to look up (e.g., "requests", "numpy", "flask").

### `is_vulnerable` (~73 tokens)

Check if a specific package version has known vulnerabilities. Requires an exact version specifier (e.g., 'requests==2.31.0').

Input parameters:

- `name` (string, required): The exact package name and version (e.g., "requests==2.31.0", "numpy==1.24.0").

## Diagnostics

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

## Score history

- 2026-08-04: 64
- 2026-08-03: 64
- 2026-08-02: 61
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 62
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://mcp.fetter.io/mcp
- Repository: https://github.com/fetter-io/fetter-mcp
- Website: https://fetter.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/fetter-io-fetter-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/fetter-io-fetter-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/fetter-io-fetter-mcp/mcp