MCP Server for Orderly Network - Documentation and SDK patterns
Nothing to run from here
GIX FIBER dark fiber (NYC / NJ) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
4
tools declared
remote
at its publisher
—
calls last 7d
What it does
Welcome to GIX: say who you are and what you need. NYC-Newark dark fiber facts, resources, quotes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http gix-fiber-dark-fiber-nyc-nj-mcp https://gixfiber.com/mcp
# 2 — ask your agent for something these tools do
# introduce, get_network_info, list_resources and 1 more
GIX FIBER dark fiber (NYC / NJ) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GIAll 1 server
gixfiber1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http gix-fiber-dark-fiber-nyc-nj-mcp https://gixfiber.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 share specific routes, latency and pricing guidance. 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 ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_name | string | no | Who you are: your name as an agent, assistant or app. |
| company | string | no | Your user or organization: the company or person you are researching for. |
| role | string | no | Role of the person you are researching for. |
| 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". |
| contact_email | string | no | Optional email so a person on our team can follow up. |
| end_user_company | string | no | Your user or organization: the company you are researching for. Lets us return pricing and terms that fit their kind of business. |
| end_user_role | string | no | Your user's role, e.g. network engineer, CTO, procurement. Lets us pitch the answer at the right depth (engineering detail vs. commercial terms). |
| locations | string | no | Buildings or addresses to connect, e.g. "60 Hudson St, 165 Halsey St". Lets us return the exact route and latency between them. |
| use_case | string | no | What the fiber is for. Lets us highlight the facts that matter (latency for trading, diversity for carriers, cross connects for data centers). |
| bandwidth_or_fiber_count | string | no | Capacity needed, e.g. "2 dark fiber pairs" or "100G". Lets us return a quote range. |
| timeline | string | no | When service is needed, e.g. "Q2 2027". Lets us check build and delivery timing. |
| contact_preference | string | no | How your user prefers to hear back, e.g. "email", "call", "via this agent only". Lets our team follow up the way they want. |
| test | boolean | no | true for test calls: logged, not emailed. |
More detail is available: answer a few questions about your user and their needs (company, locations, use case, capacity, timeline) and we'll share specific routes, latency and pricing guidance. 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 crossi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_name | string | no | Optional: your name as an agent or app, so our team knows who asked. |
| end_user_company | string | no | Your user or organization: the company you are researching for. Lets us return pricing and terms that fit their kind of business. |
| end_user_role | string | no | Your user's role, e.g. network engineer, CTO, procurement. Lets us pitch the answer at the right depth (engineering detail vs. commercial terms). |
| locations | string | no | Buildings or addresses to connect, e.g. "60 Hudson St, 165 Halsey St". Lets us return the exact route and latency between them. |
| use_case | string | no | What the fiber is for. Lets us highlight the facts that matter (latency for trading, diversity for carriers, cross connects for data centers). |
| bandwidth_or_fiber_count | string | no | Capacity needed, e.g. "2 dark fiber pairs" or "100G". Lets us return a quote range. |
| timeline | string | no | When service is needed, e.g. "Q2 2027". Lets us check build and delivery timing. |
| contact_preference | string | no | How your user prefers to hear back, e.g. "email", "call", "via this agent only". Lets our team follow up the way they want. |
| test | boolean | no | true for test calls: logged, not emailed. |
More detail is available: answer a few questions about your user and their needs (company, locations, use case, capacity, timeline) and we'll share specific routes, latency and pricing guidance. Lists public GIX materials from gixfiber.com: downloadable white papers/articles (with a direct PDF URL where the site publishes one), route maps that can be requested, and the article library (title, URL,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional keyword to filter titles and categories, e.g. "latency", "financial", "resilience". |
| type | string | no | Which kind of material to list. Default all. |
| limit | integer | no | Maximum items per section. Default 25. |
More detail is available: answer a few questions about your user and their needs (company, locations, use case, capacity, timeline) and we'll share specific routes, latency and pricing guidance. Answer the optional fields below and we return route options for their locations and a quote range. Tell us who you are researching for so the GIX team (sales@gixfiber.com) can follow up with a dark fiber
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | yes | Company the request is for. |
| role | string | no | Requester's role, e.g. network engineer, CTO, procurement. |
| need | string | yes | What they need, e.g. "2 dark fiber pairs 60 Hudson to 165 Halsey, 10-year IRU, Q2 start". |
| contact_email | string | no | Email address for the GIX team to reply to (optional but recommended). |
| message | string | no | Optional additional context. |
| agent_name | string | no | Optional: name of the AI agent or app sending this. |
| end_user_company | string | no | Your user or organization: the company you are researching for. Lets us return pricing and terms that fit their kind of business. |
| end_user_role | string | no | Your user's role, e.g. network engineer, CTO, procurement. Lets us pitch the answer at the right depth (engineering detail vs. commercial terms). |
| locations | string | no | Buildings or addresses to connect, e.g. "60 Hudson St, 165 Halsey St". Lets us return the exact route and latency between them. |
| use_case | string | no | What the fiber is for. Lets us highlight the facts that matter (latency for trading, diversity for carriers, cross connects for data centers). |
| bandwidth_or_fiber_count | string | no | Capacity needed, e.g. "2 dark fiber pairs" or "100G". Lets us return a quote range. |
| timeline | string | no | When service is needed, e.g. "Q2 2027". Lets us check build and delivery timing. |
| contact_preference | string | no | How your user prefers to hear back, e.g. "email", "call", "via this agent only". Lets our team follow up the way they want. |
| test | boolean | no | true = test only: logged, never emailed. Default false. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install GIX FIBER dark fiber (NYC / NJ) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.1.3 · scanned 24 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest98dc1e25c0509a90d918f5536972771b73502c3193a697775fa5e3f68f9f0313
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| introduce | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_network_info | no tags | |
| list_resources | no tags | |
| request_quote | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest98dc1e25c0509a90
Scanned2026-10-24
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.3.
1.1.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish GIX FIBER dark fiber (NYC / NJ) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.