# vu1nz (remote · vu1nz.com)

Vulnerability intel (vu1nz.com)

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `vu1nz.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-profullstack-vu1nz/api-mcp.md), [page](https://verifymcp.io/servers/com-profullstack-vu1nz/api-mcp)

## Channel facts

- Endpoint: `https://vu1nz.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: this server exposes a tool marked destructive (delete_webhook) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
  - 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**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 742 tokens (~61/item across 12 items; 12 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**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the vu1nz MCP server?

vu1nz is a hosted endpoint at https://vu1nz.com/api/mcp, so there is nothing to install locally. 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 --transport http com-profullstack-vu1nz 'https://vu1nz.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-profullstack-vu1nz": {
      "url": "https://vu1nz.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-profullstack-vu1nz": {
      "type": "http",
      "url": "https://vu1nz.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-profullstack-vu1nz]
url = "https://vu1nz.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-profullstack-vu1nz": {
      "type": "remote",
      "url": "https://vu1nz.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-profullstack-vu1nz --url 'https://vu1nz.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-profullstack-vu1nz:
    url: "https://vu1nz.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-profullstack-vu1nz": {
      "Transport": "http",
      "Url": "https://vu1nz.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-profullstack-vu1nz -t streamable-http -u 'https://vu1nz.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-profullstack-vu1nz": {
      "type": "http",
      "url": "https://vu1nz.com/api/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-11-21 (score 67, +1)

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

### 2026-11-19 (score 66, +1)

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

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

- [security regression] HSTS header: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (delete_webhook) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Schema quality: unverified → 100

### 2026-11-17 (score 50, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

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

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-13 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 62, +58)

- [security regression] HSTS header: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (delete_webhook) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 58
- [functional] First check of Destructive annotations: 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-11-11 (score 4)

First indexed and scored.

## MCP tools (12)

### `scan_repo` (~68 tokens)

Scan Repo CI/CD Security

Run vu1nz's 6 deterministic CI/CD security checks against any public GitHub repository's workflow files. Returns findings with severity, file, line, CWE, and recommendation.

Input parameters:

- `repo` (string, required): GitHub repo in 'owner/repo' format (or a full github.com URL).

### `threat_feed` (~75 tokens)

Malicious Package Feed

Recent malicious packages caught in the wild across npm, pip, cargo, rubygems. Sourced from OSV.dev with a curated fallback list (Shai-Hulud, Polyfill.io, ctx, ua-parser-js, etc.).

Input parameters:

- `limit` (number): Max entries to return (1-50, default 25).

### `list_checks` (~43 tokens)

List Security Checks

The catalog of CI/CD security checks vu1nz runs, each mapped to a CWE. Use to explain to a user what vu1nz would catch on their PRs.

### `list_advisories` (~26 tokens)

List Advisories

vu1nz-published security advisories with date, severity, and summary.

### `list_blog_posts` (~40 tokens)

List Blog Posts

All vu1nz blog posts: supply-chain analysis, release notes, security research. Returns slug, title, date, tags, summary, and URL.

### `get_blog_post` (~42 tokens)

Get Blog Post

Full content of a vu1nz blog post by slug.

Input parameters:

- `slug` (string, required): Blog post slug (e.g. 'what-dependabot-misses').

### `check_license` (~99 tokens)

Check License Status

Look up the vu1nz subscription status for a GitHub org. Bootstraps a 14-day free trial on first call. Returns ok, status (trialing/active/past_due/cancelled/exempt), days remaining, license_key, and upgrade URL.

Input parameters:

- `github_org` (string, required): GitHub org login (e.g. 'acme-corp').
- `license_key` (string): Optional existing license_key for sanity check.

### `list_webhooks` (~36 tokens)

List Webhooks

List your vu1nz webhook endpoints and the event types vu1nz emits (scan.completed, scan.failed). Needs an API key.

### `create_webhook` (~80 tokens)

Create Webhook

Add a webhook endpoint (public https URL). Returns the endpoint and its signing secret (shown once). Needs an API key.

Input parameters:

- `description` (string)
- `events` (array): Patterns: '*', 'scan.completed', 'scan.failed', 'scan.*'. Default all.
- `url` (string, required): https URL that receives signed CloudEvents.

### `delete_webhook` (~30 tokens)

Delete Webhook

Remove one of your webhook endpoints by id. Needs an API key.

Input parameters:

- `id` (string, required)

### `test_webhook` (~37 tokens)

Send Test Webhook

Send a webhook.test event to one of your endpoints now and report the result. Needs an API key.

Input parameters:

- `id` (string, required)

### `webhook_deliveries` (~47 tokens)

Webhook Deliveries

Recent webhook deliveries (status, attempts, last HTTP status), optionally for one endpoint. Needs an API key.

Input parameters:

- `endpoint_id` (string)
- `limit` (number)

## Diagnostics

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

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 50
- 2026-11-16: 63
- 2026-11-15: 63
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 62
- 2026-11-11: 4

## Common questions

### What is the vu1nz MCP server?

vu1nz is an MCP server listed in the public MCP registry as com.profullstack/vu1nz. Vulnerability intel (vu1nz.com). This page covers its hosted endpoint (https://vu1nz.com/api/mcp).

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

vu1nz scores 67 out of 100 on VerifyMCP. 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.

### What tools does the vu1nz MCP server expose?

vu1nz exposes 12 tools: scan_repo, threat_feed, list_checks, list_advisories, list_blog_posts, and 7 more. Their descriptions and schemas cost roughly 623 tokens of context every time the server is loaded.

### Does the vu1nz MCP server require authentication?

No. We connected to vu1nz without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the vu1nz MCP server still maintained?

vu1nz 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 did VerifyMCP test on the vu1nz MCP server?

VerifyMCP ran 12 checks on vu1nz, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about vu1nz: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://vu1nz.com/api/mcp
- Website: https://vu1nz.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-profullstack-vu1nz/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-profullstack-vu1nz/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-profullstack-vu1nz/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-profullstack-vu1nz/api-mcp
