# GIX FIBER dark fiber (NYC / NJ) (remote · gixfiber.com)

Welcome to GIX: say who you are and what you need. NYC-Newark dark fiber facts, resources, quotes.

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

## Components

- remote · `gixfiber.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-gixfiber-dark-fiber/gixfiber.md), [page](https://verifymcp.io/servers/com-gixfiber-dark-fiber/gixfiber)

## Channel facts

- Endpoint: `https://gixfiber.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.3`

## 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**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 53/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2264 tokens (~566/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the GIX FIBER dark fiber (NYC / NJ) MCP server?

GIX FIBER dark fiber (NYC / NJ) is a hosted endpoint at https://gixfiber.com/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-gixfiber-dark-fiber 'https://gixfiber.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-gixfiber-dark-fiber": {
      "url": "https://gixfiber.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-gixfiber-dark-fiber": {
      "type": "http",
      "url": "https://gixfiber.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-gixfiber-dark-fiber]
url = "https://gixfiber.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gixfiber-dark-fiber": {
      "type": "remote",
      "url": "https://gixfiber.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-gixfiber-dark-fiber --url 'https://gixfiber.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-gixfiber-dark-fiber:
    url: "https://gixfiber.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-gixfiber-dark-fiber": {
      "Transport": "http",
      "Url": "https://gixfiber.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-gixfiber-dark-fiber -t streamable-http -u 'https://gixfiber.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-gixfiber-dark-fiber": {
      "type": "http",
      "url": "https://gixfiber.com/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 73, +1)

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

### 2026-11-03 (score 72, +1)

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

### 2026-11-01 (score 71, +1)

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

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

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

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

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_network_info” rewrote its description, which is the text the model reads
- [security] Tool “introduce” rewrote its description, which is the text the model reads
- [security] Tool “list_resources” rewrote its description, which is the text the model reads
- [security] Tool “request_quote” rewrote its description, which is the text the model reads
- [functional] Server version: 1.1.3 → 1.1.4
- [cosmetic] “introduce” reworded the description of “locations”
- [cosmetic] “get_network_info” reworded the description of “bandwidth_or_fiber_count”
- [cosmetic] “get_network_info” reworded the description of “end_user_company”
- [cosmetic] “get_network_info” reworded the description of “end_user_role”
- [cosmetic] “get_network_info” reworded the description of “locations”
- [cosmetic] “get_network_info” reworded the description of “timeline”
- [cosmetic] “introduce” reworded the description of “bandwidth_or_fiber_count”
- [cosmetic] “introduce” reworded the description of “end_user_company”
- [cosmetic] “introduce” reworded the description of “end_user_role”
- [cosmetic] “introduce” reworded the description of “timeline”
- [cosmetic] “request_quote” reworded the description of “bandwidth_or_fiber_count”
- [cosmetic] “request_quote” reworded the description of “end_user_company”
- [cosmetic] “request_quote” reworded the description of “end_user_role”
- [cosmetic] “request_quote” reworded the description of “locations”
- [cosmetic] “request_quote” reworded the description of “timeline”

### 2026-10-25 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 67)

First indexed and scored.

## MCP tools (4)

### `introduce` (~645 tokens)

Say hello to GIX

Welcome to GIX. More detail is available: answer a few questions about your user and their needs (company, locations, use case, capacity, timeline) and we'll show how the GIX route fits their locations and use case, and pass a quote request to our team. Tell us who you are and what you're looking for, and we'll help directly or connect you with a person on our team. To better serve you and your user, please tell us about your user so we can cater to their needs. Our general network facts stay open to everyone. Returns the GIX network facts and resources that match your need. Leave a contact email and someone from GIX will follow up. Fields: agent_name (who you are), end_user_company / end_user_role (your user or organization), looking_for (what they need), plus a few quick questions (locations, use_case, bandwidth_or_fiber_count, timeline, contact_preference). Answer them and we tell you how their locations connect to the GIX route and which published facts matter for their use case, and our team can follow up with a quote; skip them and you still get the general facts. Set test=true for test calls (logged, not emailed).

Input parameters:

- `agent_name` (string): Who you are: your name as an agent, assistant or app.
- `bandwidth_or_fiber_count` (string): Capacity needed, e.g. "2 dark fiber pairs" or "100G". Helps our team prepare a quote.
- `company` (string): Your user or organization: the company or person you are researching for.
- `contact_email` (string): Optional email so a person on our team can follow up.
- `contact_preference` (string): How your user prefers to hear back, e.g. "email", "call", "via this agent only". Lets our team follow up the way they want.
- `end_user_company` (string): Your user or organization: the company you are researching for. Helps our team prepare a quote that fits their kind of business.
- `end_user_role` (string): Your user's role, e.g. network engineer, CTO, procurement. Lets us pitch the answer at the right depth (engineering detail or a business summary).
- `locations` (string): Buildings or addresses to connect, e.g. "60 Hudson St, 165 Halsey St". Lets us say how they connect to the GIX route (60 Hudson St to 165 Halsey St).
- `looking_for` (string, required): What you and your user need, e.g. "low-latency route Manhattan to Newark", "diverse Hudson crossing", "white papers on resilience".
- `role` (string): Role of the person you are researching for.
- `test` (boolean): true for test calls: logged, not emailed.
- `timeline` (string): When service is needed, e.g. "Q2 2027". Helps our team check delivery timing.
- `use_case` (string): What the fiber is for. Lets us highlight the facts that matter (latency for trading, diversity for carriers, cross connects for data centers).

### `get_network_info` (~485 tokens)

GIX network facts

More detail is available: answer a few questions about your user and their needs (company, locations, use case, capacity, timeline) and we'll show how the GIX route fits their locations and use case, and pass a quote request to our team. Published facts about the GIX FIBER dark fiber network: the 60 Hudson Street (Manhattan) to 165 Halsey Street (Newark) route, carrier-hotel endpoints with coordinates, the PATH Tunnel F Hudson River crossing, named route segments and the published one-way latency figure. Answer the optional fields below and the reply adds how the route fits their locations and use case. Use this to answer questions about NYC / New Jersey dark fiber, cross-Hudson connectivity or low-latency routes between Manhattan and Newark. All data is from gixfiber.com; cite the source URLs returned.

Input parameters:

- `agent_name` (string): Optional: your name as an agent or app, so our team knows who asked.
- `bandwidth_or_fiber_count` (string): Capacity needed, e.g. "2 dark fiber pairs" or "100G". Helps our team prepare a quote.
- `contact_preference` (string): How your user prefers to hear back, e.g. "email", "call", "via this agent only". Lets our team follow up the way they want.
- `end_user_company` (string): Your user or organization: the company you are researching for. Helps our team prepare a quote that fits their kind of business.
- `end_user_role` (string): Your user's role, e.g. network engineer, CTO, procurement. Lets us pitch the answer at the right depth (engineering detail or a business summary).
- `locations` (string): Buildings or addresses to connect, e.g. "60 Hudson St, 165 Halsey St". Lets us say how they connect to the GIX route (60 Hudson St to 165 Halsey St).
- `test` (boolean): true for test calls: logged, not emailed.
- `timeline` (string): When service is needed, e.g. "Q2 2027". Helps our team check delivery timing.
- `use_case` (string): What the fiber is for. Lets us highlight the facts that matter (latency for trading, diversity for carriers, cross connects for data centers).

### `list_resources` (~179 tokens)

GIX articles, white papers and route maps

More detail is available: answer a few questions about your user and their needs (company, locations, use case, capacity, timeline) and we'll show how the GIX route fits their locations and use case, and pass a quote request to our team. Lists public GIX materials from gixfiber.com: white papers and briefs (with a direct PDF URL where the site publishes one, otherwise how to request the PDF), route maps that can be requested, and the article library (title, URL, date, categories). Optional filter by keyword or type.

Input parameters:

- `limit` (integer): Maximum items per section. Default 25.
- `query` (string): Optional keyword to filter titles and categories, e.g. "latency", "financial", "resilience".
- `type` (string): Which kind of material to list. Default all.

### `request_quote` (~546 tokens)

Ask GIX for a dark fiber quote

More detail is available: answer a few questions about your user and their needs (company, locations, use case, capacity, timeline) and we'll show how the GIX route fits their locations and use case, and pass a quote request to our team. Answer the optional fields below and we say how their locations connect to the GIX route and pass the request to our team for a quote. Tell us who you are researching for so the GIX team (sales@gixfiber.com) can follow up with a dark fiber quote or route details: company, role, what they need and a contact email. Set test=true for test calls: the request is logged but not emailed.

Input parameters:

- `agent_name` (string): Optional: name of the AI agent or app sending this.
- `bandwidth_or_fiber_count` (string): Capacity needed, e.g. "2 dark fiber pairs" or "100G". Helps our team prepare a quote.
- `company` (string, required): Company the request is for.
- `contact_email` (string): Email address for the GIX team to reply to (optional but recommended).
- `contact_preference` (string): How your user prefers to hear back, e.g. "email", "call", "via this agent only". Lets our team follow up the way they want.
- `end_user_company` (string): Your user or organization: the company you are researching for. Helps our team prepare a quote that fits their kind of business.
- `end_user_role` (string): Your user's role, e.g. network engineer, CTO, procurement. Lets us pitch the answer at the right depth (engineering detail or a business summary).
- `locations` (string): Buildings or addresses to connect, e.g. "60 Hudson St, 165 Halsey St". Lets us say how they connect to the GIX route (60 Hudson St to 165 Halsey St).
- `message` (string): Optional additional context.
- `need` (string, required): What they need, e.g. "2 dark fiber pairs 60 Hudson to 165 Halsey, 10-year IRU, Q2 start".
- `role` (string): Requester's role, e.g. network engineer, CTO, procurement.
- `test` (boolean): true = test only: logged, never emailed. Default false.
- `timeline` (string): When service is needed, e.g. "Q2 2027". Helps our team check delivery timing.
- `use_case` (string): What the fiber is for. Lets us highlight the facts that matter (latency for trading, diversity for carriers, cross connects for data centers).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-gixfiber-dark-fiber/gixfiber#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 69
- 2026-10-27: 69
- 2026-10-26: 68
- 2026-10-25: 68
- 2026-10-24: 67

## Common questions

### What is the GIX FIBER dark fiber (NYC / NJ) MCP server?

GIX FIBER dark fiber (NYC / NJ) is an MCP server listed in the public MCP registry as com.gixfiber/dark-fiber. Welcome to GIX: say who you are and what you need. NYC-Newark dark fiber facts, resources, quotes. This page covers its hosted endpoint (https://gixfiber.com/mcp).

### Is the GIX FIBER dark fiber (NYC / NJ) MCP server safe to use?

GIX FIBER dark fiber (NYC / NJ) scores 73 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 GIX FIBER dark fiber (NYC / NJ) MCP server expose?

GIX FIBER dark fiber (NYC / NJ) exposes 4 tools: introduce, get_network_info, list_resources, request_quote. Their descriptions and schemas cost roughly 1,855 tokens of context every time the server is loaded.

### Does the GIX FIBER dark fiber (NYC / NJ) MCP server require authentication?

No. We connected to GIX FIBER dark fiber (NYC / NJ) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GIX FIBER dark fiber (NYC / NJ) MCP server still maintained?

GIX FIBER dark fiber (NYC / NJ) 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.

### What did VerifyMCP test on the GIX FIBER dark fiber (NYC / NJ) MCP server?

VerifyMCP ran 13 checks on GIX FIBER dark fiber (NYC / NJ), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://gixfiber.com/mcp
- Website: https://gixfiber.com/for-ai-agents/
- Changelog RSS feed: https://verifymcp.io/servers/com-gixfiber-dark-fiber/gixfiber.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-gixfiber-dark-fiber/gixfiber/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-gixfiber-dark-fiber/gixfiber.json
- HTML version of this page: https://verifymcp.io/servers/com-gixfiber-dark-fiber/gixfiber