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.
Available components
Last scanned (8 hours ago)
Scores higher than 60% 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 Security74
- 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
- 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 Usability53
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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 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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 29 Oct 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.
- 27 Oct 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.
- 26 Oct 26 0
- 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 security
- Server version: 1.1.3 → 1.1.4 functional
- “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” cosmetic
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 67
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 5 Nov 2026 · Probed https://gixfiber.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gixfiber.com | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a5499a753e590cad139f5e0bb9a6a156 |
| SANs: gixfiber.com | ||||||
| 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 insecure
Validation of gixfiber.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gixfiber.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gixfiber.com/mcp | Verified | 200 | |
| http (plaintext) | http://gixfiber.com/mcp | HTTPS enforced | 301 | https://gixfiber.com/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 →
get_network_info GIX network facts ~485
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
introduce Say hello to GIX ~645
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
list_resources GIX articles, white papers and route maps ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
request_quote Ask GIX for a dark fiber quote ~546
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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). |
No output schema declared.
No examples provided.
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.
remote · gixfiber.com
claude mcp add --transport http com-gixfiber-dark-fiber 'https://gixfiber.com/mcp'
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.