Case file No.480 · pypi · stdio

CyberSPF

com.cyberspf/mcp · v0.2.2

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

Package ↗Website ↗

Security score

73/100

Good

Normalized over 80 points of available evidence.

Unknown: Maintenance

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Source transparency0/15

no public GitHub repository linked

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

280 weekly downloads

Maintenanceunknown

Excluded from the score — no data available.

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v0.2.2)Oct 24, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is CyberSPF safe?

MCPWatch gives CyberSPF a heuristic security score of 73/100 (good), based on 80 points of available evidence; unknown: Maintenance. This is an automated heuristic, not an audit.

Does CyberSPF have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package cyberspf-mcp. That is not proof of safety.

When was CyberSPF last updated?

The latest registry version is 0.2.2, published Oct 18, 2026. The last repository push is unknown. MCPWatch last checked it on Oct 24, 2026.

What license does CyberSPF use?

Unknown — no public GitHub repository is linked in the registry.

Related servers

same publisher / similar score