# CyberSPF (pypi · cyberspf-mcp)

Assess a domain, IP or ASN: mail and DNS security, certificates, routing and a report card.

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

## Components

- pypi · `cyberspf-mcp`: 0/100 (this document), [markdown](https://verifymcp.io/servers/com-cyberspf-mcp/cyberspf-mcp.md), [page](https://verifymcp.io/servers/com-cyberspf-mcp/cyberspf-mcp)

## Channel facts

- Registry: `pypi`
- Package: `cyberspf-mcp`
- Version: `0.2.2`
- 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-06.

- **Supply Chain Security**: 75/100
  - No malware found by supply-chain analysis.
  - CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 23 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (LicenseRef-Proprietary) isn't a recognized OSI-approved license.
  - Actively maintained (last published 18 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect 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 CyberSPF MCP server?

CyberSPF runs locally as a PyPI package, launched with uvx cyberspf-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 com-cyberspf-mcp -- uvx cyberspf-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-cyberspf-mcp": {
      "command": "uvx",
      "args": [
        "cyberspf-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cyberspf-mcp": {
      "command": "uvx",
      "args": [
        "cyberspf-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-cyberspf-mcp -- uvx cyberspf-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-cyberspf-mcp --command uvx --arg cyberspf-mcp
```

### Hermes

```yaml
mcp_servers:
  com-cyberspf-mcp:
    command: "uvx"
    args: ["cyberspf-mcp"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add com-cyberspf-mcp -t stdio -c uvx -a cyberspf-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-cyberspf-mcp": {
      "command": "uvx",
      "args": [
        "cyberspf-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-19 (score 0, 0)

- [functional] Package version: 0.2.0 → 0.2.2

### 2026-10-06 (score 0, 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.

### 2026-10-04 (score 0, 0)

- [security improvement] Malware scan: unverified → pass
- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 0.1.0 → 0.2.0

### 2026-10-03 (score 0)

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, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-cyberspf-mcp/cyberspf-mcp#diagnostics

## Score history

- 2026-11-06: 0
- 2026-11-05: 0
- 2026-11-04: 0
- 2026-11-03: 0
- 2026-11-02: 0
- 2026-11-01: 0
- 2026-10-31: 0
- 2026-10-30: 0
- 2026-10-29: 0
- 2026-10-28: 0
- 2026-10-27: 0
- 2026-10-26: 0
- 2026-10-25: 0
- 2026-10-24: 0
- 2026-10-23: 0
- 2026-10-22: 0
- 2026-10-21: 0
- 2026-10-20: 0
- 2026-10-19: 0
- 2026-10-18: 0
- 2026-10-17: 0
- 2026-10-16: 0
- 2026-10-15: 0
- 2026-10-14: 0
- 2026-10-13: 0
- 2026-10-12: 0
- 2026-10-07: 0
- 2026-10-06: 0
- 2026-10-04: 0
- 2026-10-03: 0

## Common questions

### What is the CyberSPF MCP server?

CyberSPF is an MCP server listed in the public MCP registry as com.cyberspf/mcp. Assess a domain, IP or ASN: mail and DNS security, certificates, routing and a report card. This page covers its PyPI package (cyberspf-mcp).

### Is the CyberSPF MCP server still maintained?

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

CyberSPF declares the LicenseRef-Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

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