# Stealth Communications (remote · stealth.net)

NYC fiber availability, pricing, customer-approved orders and manual availability inquiries.

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

## Components

- remote · `stealth.net`: 77/100 (this document), [markdown](https://verifymcp.io/servers/net-stealth-mcp/stealth.md), [page](https://verifymcp.io/servers/net-stealth-mcp/stealth)

## Channel facts

- Endpoint: `https://stealth.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http net-stealth-mcp 'https://stealth.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "net-stealth-mcp": {
      "url": "https://stealth.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-stealth-mcp": {
      "type": "http",
      "url": "https://stealth.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.net-stealth-mcp]
url = "https://stealth.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-stealth-mcp": {
      "type": "remote",
      "url": "https://stealth.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-stealth-mcp --url 'https://stealth.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-stealth-mcp:
    url: "https://stealth.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-stealth-mcp": {
      "Transport": "http",
      "Url": "https://stealth.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-stealth-mcp -t streamable-http -u 'https://stealth.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-stealth-mcp": {
      "type": "http",
      "url": "https://stealth.net/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-05 (score 77, +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.

### 2026-11-03 (score 76, +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-02 (score 75, 0)

- [cosmetic] “place_order” reworded the description of “preferred_installation_date”

### 2026-11-01 (score 75, +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-10-30 (score 74, +4)

- [functional regression] Schema quality: 236 → 286
- [functional improvement] Tool coverage: 4% → 100%
- [functional] Schema quality: good → excellent
- [cosmetic] “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”

### 2026-10-29 (score 70, +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.

### 2026-10-27 (score 69, 0)

- [security] 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
- [functional regression] Schema quality: 172 → 236

### 2026-10-26 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `check_building_availability` (~228 tokens)

Check Stealth building availability

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.

Input parameters:

- `address` (string, required): New York City street address, including the building number and street name.
- `borough` (string, required): New York City borough containing the address; select one of the listed values.

### `get_pricing` (~178 tokens)

Get current Dedicated Internet pricing

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.

### `prepare_order` (~218 tokens)

Prepare a Stealth service order for review

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.

Input parameters:

- `address_token` (string, required): Signed address_token for the building explicitly selected from check_building_availability.
- `speed` (integer, required): Requested Dedicated Internet bandwidth in Gbps; choose one of the listed values.

### `place_order` (~412 tokens)

Place an explicitly approved Stealth service order

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.

Input parameters:

- `accept_terms` (boolean, required): Set to true only after the actual customer explicitly accepts the reviewed service terms and charges.
- `authorized_to_order` (boolean, required): Set to true only after the actual customer explicitly confirms authorization to place this order.
- `company` (string, required): Legal or business name of the customer placing the order.
- `details` (string): Optional customer-provided notes relevant to the order.
- `email` (string, required): Customer contact email address for the order confirmation.
- `name` (string, required): Name of the customer contact authorized to place the order.
- `order_token` (string, required): Signed, time-limited order_token from prepare_order for the offer the customer reviewed.
- `phone` (string, required): 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, required): Floor, suite, or other location within the selected building.

### `prepare_availability_inquiry` (~218 tokens)

Prepare a manual availability inquiry

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.

Input parameters:

- `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.

### `submit_availability_inquiry` (~231 tokens)

Send an approved availability inquiry

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.

Input parameters:

- `approve_submission` (boolean, required): 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.
- `email` (string, required): Customer contact email address for the availability inquiry.
- `inquiry_token` (string, required): Signed, time-limited inquiry_token returned by prepare_availability_inquiry.
- `name` (string, required): Name of the customer contact requesting the availability review.

## Diagnostics

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

## Score history

- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 70
- 2026-10-28: 69
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 69

## Common questions

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

## Links

- Remote endpoint: https://stealth.net/mcp
- Website: https://stealth.net/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/net-stealth-mcp/stealth.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-stealth-mcp/stealth.json
- HTML version of this page: https://verifymcp.io/servers/net-stealth-mcp/stealth