Stealth Communications
REMOTE · STEALTH.NET
NYC fiber availability, pricing, customer-approved orders and manual availability inquiries.
Available components
Last scanned (12 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1723 tokens (~287/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 3 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.
- 2 Nov 26 0
- “place_order” reworded the description of “preferred_installation_date” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 1 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.
- 30 Oct 26 +4
- Schema quality: 236 → 286 ▼ functional
- Tool coverage: 4% → 100% ▲ functional
- Schema quality: good → excellent functional
- “check_building_availability” reworded the description of “address” cosmetic
- “check_building_availability” reworded the description of “borough” cosmetic
- “place_order” reworded the description of “accept_terms” cosmetic
- “place_order” reworded the description of “authorized_to_order” cosmetic
- “place_order” reworded the description of “company” cosmetic
- “place_order” reworded the description of “details” cosmetic
- “place_order” reworded the description of “email” cosmetic
- “place_order” reworded the description of “name” cosmetic
- “place_order” reworded the description of “order_token” cosmetic
- “place_order” reworded the description of “phone” cosmetic
- “place_order” reworded the description of “suite” cosmetic
- “prepare_availability_inquiry” reworded the description of “address” cosmetic
- “prepare_availability_inquiry” reworded the description of “address_token” cosmetic
- “prepare_availability_inquiry” reworded the description of “borough” cosmetic
- “prepare_availability_inquiry” reworded the description of “speed” cosmetic
- “prepare_order” reworded the description of “address_token” cosmetic
- “prepare_order” reworded the description of “speed” cosmetic
- “submit_availability_inquiry” reworded the description of “approve_submission” cosmetic
- “submit_availability_inquiry” reworded the description of “company” cosmetic
- “submit_availability_inquiry” reworded the description of “details” cosmetic
- “submit_availability_inquiry” reworded the description of “email” cosmetic
- “submit_availability_inquiry” reworded the description of “inquiry_token” cosmetic
- “submit_availability_inquiry” reworded the description of “name” cosmetic
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_building_availability” rewrote its description, which is the text the model reads security
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- Tool “place_order” rewrote its description, which is the text the model reads security
- Tool “prepare_order” rewrote its description, which is the text the model reads security
- Schema quality: 172 → 236 ▼ functional
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://stealth.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stealth.net | CN=YE1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5fd27c2500ba6e0210af90b01ca7a22f1a8 |
| SANs: stealth.net | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 stealth.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| stealth.net. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; script-src 'self' 'sha256-SPtDYhOl1J3VkS18AJ1hq07eTnYVRkjPqbyN0+enJcE='; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self'; font-src 'self'; connect-src 'self'; media-src 'none'; manifest-src 'none'; object-src 'none'; frame-src 'none'; worker-src 'none'; child-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; report-uri /api/csp-reports; report-to csp |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), geolocation=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stealth.net/mcp | Verified | 200 | |
| http (plaintext) | http://stealth.net/mcp | HTTPS enforced | 308 | https://stealth.net/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_building_availability Check Stealth building availability ~228
Search a New York City business address. Returns up to five verified address candidates with signed address tokens and current eligibility. Ask the customer to select the correct building when there is more than one candidate. An unverified address requires manual review and cannot be ordered. Before placing an order, show the actual customer the exact building, bandwidth, monthly price, installation fee, survey requirement where applicable, term and linked service terms. Nearby orders use the standard installation fee for the selected bandwidth from the published Dedicated Internet schedule. Explain that feasibility, installation scope and timing require a site survey; special construction or changes to the displayed price or terms require separate approval before work begins. Never promise the connected-building online installation offer or timing for a Nearby order. Obtain that customer’s explicit acceptance and confirmation that they are authorized to order for the company. Never infer consent or authority from an availability or pricing inquiry.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | New York City street address, including the building number and street name. |
| borough | string | yes | New York City borough containing the address; select one of the listed values. |
No output schema declared.
No examples provided.
get_pricing Get current Dedicated Internet pricing ~178
Read current published Dedicated Internet bandwidth prices, installation fees, initial term, billing and service terms. The result distinguishes the connected-building online installation offer from standard Nearby installation fees by bandwidth. Check the building before preparing an order. Before placing an order, show the actual customer the exact building, bandwidth, monthly price, installation fee, survey requirement where applicable, term and linked service terms. Nearby orders use the standard installation fee for the selected bandwidth from the published Dedicated Internet schedule. Explain that feasibility, installation scope and timing require a site survey; special construction or changes to the displayed price or terms require separate approval before work begins. Never promise the connected-building online installation offer or timing for a Nearby order. Obtain that customer’s explicit acceptance and confirmation that they are authorized to order for the company. Never infer consent or authority from an availability or pricing inquiry.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
place_order Place an explicitly approved Stealth service order ~412
Records the reviewed service order and queues staff and customer confirmations after validation. Connected-building orders are accepted; eligible nearby commercial buildings receive conditional orders with status pending_survey. Before placing an order, show the actual customer the exact building, bandwidth, monthly price, installation fee, survey requirement where applicable, term and linked service terms. Nearby orders use the standard installation fee for the selected bandwidth from the published Dedicated Internet schedule. Explain that feasibility, installation scope and timing require a site survey; special construction or changes to the displayed price or terms require separate approval before work begins. Never promise the connected-building online installation offer or timing for a Nearby order. Obtain that customer’s explicit acceptance and confirmation that they are authorized to order for the company. Never infer consent or authority from an availability or pricing inquiry. Pass accept_terms=true and authorized_to_order=true only after that explicit customer confirmation. Retry the same order_token after a network failure; never prepare a new order just to retry. No payment is collected at checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_terms | boolean | yes | Set to true only after the actual customer explicitly accepts the reviewed service terms and charges. |
| authorized_to_order | boolean | yes | Set to true only after the actual customer explicitly confirms authorization to place this order. |
| company | string | yes | Legal or business name of the customer placing the order. |
| details | string | – | Optional customer-provided notes relevant to the order. |
| string | yes | Customer contact email address for the order confirmation. | |
| name | string | yes | Name of the customer contact authorized to place the order. |
| order_token | string | yes | Signed, time-limited order_token from prepare_order for the offer the customer reviewed. |
| phone | string | yes | Customer contact telephone number for the order. |
| preferred_installation_date | string | – | Optional YYYY-MM-DD date, 4 to 90 calendar days from today in America/New_York. Stealth confirms scheduling. |
| suite | string | yes | Floor, suite, or other location within the selected building. |
No output schema declared.
No examples provided.
prepare_availability_inquiry Prepare a manual availability inquiry ~218
Prepare a request for manual availability review, including unverified or off-network addresses. Supply an address token from a building check, or the entered address and NYC borough. This step sends nothing. Before sending an availability inquiry, show the actual customer the address, requested bandwidth, contact details, message and returned customer data notice. Obtain explicit approval to share them with Stealth. This requests a manual review; it does not place an order, confirm availability or promise installation timing. Never infer consent from an address search or pricing inquiry.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | New York City street address, including building number and street name; provide with borough instead of address_token. |
| address_token | string | – | Signed address_token or inquiry_address_token returned by check_building_availability; use this instead of address and borough. |
| borough | string | – | Borough containing the entered address; provide with address instead of address_token. |
| speed | integer | – | Requested bandwidth in Gbps; use 0 or omit when the customer is not sure yet. |
No output schema declared.
No examples provided.
prepare_order Prepare a Stealth service order for review ~218
Recheck the explicitly selected building and create a signed, time-limited quote for a published bandwidth. This does not place an order. Show the returned review and linked terms to the actual customer before requesting acceptance. Before placing an order, show the actual customer the exact building, bandwidth, monthly price, installation fee, survey requirement where applicable, term and linked service terms. Nearby orders use the standard installation fee for the selected bandwidth from the published Dedicated Internet schedule. Explain that feasibility, installation scope and timing require a site survey; special construction or changes to the displayed price or terms require separate approval before work begins. Never promise the connected-building online installation offer or timing for a Nearby order. Obtain that customer’s explicit acceptance and confirmation that they are authorized to order for the company. Never infer consent or authority from an availability or pricing inquiry.
| Name | Type | Req | Description |
|---|---|---|---|
| address_token | string | yes | Signed address_token for the building explicitly selected from check_building_availability. |
| speed | integer | yes | Requested Dedicated Internet bandwidth in Gbps; choose one of the listed values. |
No output schema declared.
No examples provided.
submit_availability_inquiry Send an approved availability inquiry ~231
Save the customer-approved availability inquiry and queue staff and customer confirmations. Before sending an availability inquiry, show the actual customer the address, requested bandwidth, contact details, message and returned customer data notice. Obtain explicit approval to share them with Stealth. This requests a manual review; it does not place an order, confirm availability or promise installation timing. Never infer consent from an address search or pricing inquiry. Pass approve_submission=true only after that explicit approval. Retry the same inquiry_token after a network failure; never prepare another inquiry merely to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| approve_submission | boolean | yes | Set to true only after the actual customer explicitly approves sharing the reviewed inquiry and contact details with Stealth. |
| company | string | – | Optional customer business or organization name. |
| details | string | – | Optional customer-provided message or details for the availability review. |
| string | yes | Customer contact email address for the availability inquiry. | |
| inquiry_token | string | yes | Signed, time-limited inquiry_token returned by prepare_availability_inquiry. |
| name | string | yes | Name of the customer contact requesting the availability review. |
No output schema declared.
No examples provided.
How do I install the Stealth Communications MCP server?
Stealth Communications is a hosted endpoint at https://stealth.net/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 · stealth.net
claude mcp add --transport http net-stealth-mcp 'https://stealth.net/mcp'
What is the Stealth Communications MCP server?
Stealth Communications is an MCP server listed in the public MCP registry as net.stealth/mcp. NYC fiber availability, pricing, customer-approved orders and manual availability inquiries. This page covers its hosted endpoint (https://stealth.net/mcp).
Is the Stealth Communications MCP server safe to use?
Stealth Communications scores 77 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 Stealth Communications MCP server expose?
Stealth Communications exposes 6 tools: check_building_availability, get_pricing, prepare_order, place_order, prepare_availability_inquiry, submit_availability_inquiry. Their descriptions and schemas cost roughly 1,485 tokens of context every time the server is loaded.
Does the Stealth Communications MCP server require authentication?
No. We connected to Stealth Communications without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Stealth Communications MCP server still maintained?
Stealth Communications is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.