Last scanned (16 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 742 tokens (~61/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 18 Nov 26 +15
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 17 Nov 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 13 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 +58
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 11 Nov 26 4
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://vu1nz.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vu1nz.com | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 647198813e4c4f4c74cf53ad4a81ef5c4e6 |
| SANs: vu1nz.com, www.vu1nz.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vu1nz.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| vu1nz.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vu1nz.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://vu1nz.com/api/mcp | HTTPS enforced | 301 | https://vu1nz.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_license Check License Status ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| github_org | string | yes | GitHub org login (e.g. 'acme-corp'). |
| license_key | string | – | Optional existing license_key for sanity check. |
No output schema declared.
No examples provided.
create_webhook Create Webhook ~80
Add a webhook endpoint (public https URL). Returns the endpoint and its signing secret (shown once). Needs an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| events | array | – | Patterns: '*', 'scan.completed', 'scan.failed', 'scan.*'. Default all. |
| url | string | yes | https URL that receives signed CloudEvents. |
No output schema declared.
No examples provided.
delete_webhook Delete Webhook ~30
Remove one of your webhook endpoints by id. Needs an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_blog_post Get Blog Post ~42
Full content of a vu1nz blog post by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Blog post slug (e.g. 'what-dependabot-misses'). |
No output schema declared.
No examples provided.
list_advisories List Advisories ~26
vu1nz-published security advisories with date, severity, and summary.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_blog_posts List Blog Posts ~40
All vu1nz blog posts: supply-chain analysis, release notes, security research. Returns slug, title, date, tags, summary, and URL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_checks List Security Checks ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~36
List your vu1nz webhook endpoints and the event types vu1nz emits (scan.completed, scan.failed). Needs an API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_repo Scan Repo CI/CD Security ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | GitHub repo in 'owner/repo' format (or a full github.com URL). |
No output schema declared.
No examples provided.
test_webhook Send Test Webhook ~37
Send a webhook.test event to one of your endpoints now and report the result. Needs an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
threat_feed Malicious Package Feed ~75
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.).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max entries to return (1-50, default 25). |
No output schema declared.
No examples provided.
webhook_deliveries Webhook Deliveries ~47
Recent webhook deliveries (status, attempts, last HTTP status), optionally for one endpoint. Needs an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
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.
remote · vu1nz.com
claude mcp add --transport http com-profullstack-vu1nz 'https://vu1nz.com/api/mcp'
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.