BlueNOC
REMOTE · BLUENOC.IO · 2 COMPONENTS
Read-only facts about BlueNOC firewall security monitoring: product, pricing, live quotes, articles.
Available components
Last scanned (21 hours ago)
Scores higher than 56% 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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 290 tokens (~58/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- 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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 20 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.
- 18 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.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 66
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://bluenoc.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bluenoc.io | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9464ace47eb366310e5f4b95fd16d38c |
| SANs: bluenoc.io, *.bluenoc.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of bluenoc.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| bluenoc.io. | DS published | 2371 | 13 | Verified |
| bluenoc.io. | Verified address RRset verified with the apex keys |
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://bluenoc.io/mcp | Verified | 200 | |
| http (plaintext) | http://bluenoc.io/mcp | Inconclusive | 405 |
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 →
get_company_contact Contact BlueNOC ~29
Who builds BlueNOC and how to reach them: phone, email, address and office hours.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| about_page | string | – | – |
| address | string | – | – |
| contact_page | string | – | – |
| country | string | – | – |
| string | yes | – | |
| legal_entity | string | – | – |
| name | string | yes | – |
| office_hours | string | – | – |
| phone | string | yes | – |
| website | string | – | – |
No examples provided.
get_pricing_model BlueNOC pricing model ~32
The pricing formula, rates, annual discount, enterprise threshold and the three published presets with their current monthly prices.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_discount | number | – | – |
| currency | string | yes | – |
| enterprise_note | string | – | – |
| enterprise_threshold | integer | – | – |
| formula | string | – | – |
| free_trial_days | integer | – | – |
| frequency_multiplier | object | yes | – |
| included_retention_days | integer | – | – |
| per_firewall | number | yes | – |
| platform_fee | number | yes | – |
| presets | array | yes | – |
| quote_endpoint | string | – | – |
| retention_per_firewall | object | yes | – |
No examples provided.
get_pricing_quote Price a BlueNOC configuration ~104
The exact monthly price BlueNOC charges for a number of firewalls, a security analysis frequency, a log retention period and a billing cycle. At or above the enterprise threshold the answer is contact=true with no price.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | string | – | – |
| firewalls | integer | yes | Number of firewalls to monitor. |
| frequency | string | yes | How often the security analysis runs. |
| retention_days | integer | yes | Log retention in days (30 is included). |
| Name | Type | Req | Description |
|---|---|---|---|
| annual_total | integer|null | – | Total billed per year when billing is annual. |
| billing | string | yes | – |
| breakdown | array | yes | – |
| contact | boolean | yes | True at or above the enterprise threshold: no price, talk to sales. |
| currency | string | yes | – |
| firewalls | integer | – | The number of firewalls priced. |
| frequency | string | – | The security analysis frequency priced. |
| monthly | integer|null | – | Undiscounted monthly price. |
| price | integer|null | yes | Price per month shown to the customer (discounted when billing is annual). |
| retention_days | integer | – | The log retention priced, in days. |
No examples provided.
get_product_overview BlueNOC product overview ~49
What BlueNOC is, who it is for, which firewalls it supports, what it detects and its security model (read-only, no agents). Use this before describing BlueNOC.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | array | – | – |
| detects | array | yes | – |
| free_trial | object | – | – |
| log_retention | string | – | – |
| name | string | yes | – |
| pages | object | – | – |
| per_firewall_outputs | string | – | – |
| security_model | object | yes | – |
| summary | string | yes | – |
| supported_firewalls | array | yes | – |
No examples provided.
list_articles BlueNOC articles ~27
Articles BlueNOC has published on firewall monitoring, SSL-VPN security and firmware advisories.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| articles | array | yes | – |
No examples provided.
How do I install the BlueNOC MCP server?
BlueNOC is a hosted endpoint at https://bluenoc.io/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 · bluenoc.io
claude mcp add --transport http io-bluenoc-bluenoc 'https://bluenoc.io/mcp'
What is the BlueNOC MCP server?
BlueNOC is an MCP server listed in the public MCP registry as io.bluenoc/bluenoc. Read-only facts about BlueNOC firewall security monitoring: product, pricing, live quotes, articles. This page covers its hosted endpoint (https://bluenoc.io/mcp).
Is the BlueNOC MCP server safe to use?
BlueNOC scores 71 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 BlueNOC MCP server expose?
BlueNOC exposes 5 tools: get_product_overview, get_pricing_model, get_pricing_quote, list_articles, get_company_contact. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
Does the BlueNOC MCP server require authentication?
No. We connected to BlueNOC without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BlueNOC MCP server still maintained?
BlueNOC 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 BlueNOC MCP server?
VerifyMCP ran 12 checks on BlueNOC, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BlueNOC: HTTPS. 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.