# PacketFabric (remote · mcp.packetfabric.com)

Query and manage PacketFabric NaaS: ports, virtual circuits, cloud routers, pricing, metrics.

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

## Components

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

## Channel facts

- Endpoint: `https://mcp.packetfabric.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.4`

## 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**: 77/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1791 tokens (~111/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 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 PacketFabric MCP server?

PacketFabric is a hosted endpoint at https://mcp.packetfabric.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 packetfabric-packetfabric-mcp 'https://mcp.packetfabric.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "packetfabric-packetfabric-mcp": {
      "url": "https://mcp.packetfabric.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.packetfabric-packetfabric-mcp]
url = "https://mcp.packetfabric.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  packetfabric-packetfabric-mcp:
    url: "https://mcp.packetfabric.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "packetfabric-packetfabric-mcp": {
      "type": "http",
      "url": "https://mcp.packetfabric.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-03 (score 77, +1)

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

### 2026-11-01 (score 76, +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-10-30 (score 75, +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-10-28 (score 74, +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-26 (score 73, +1)

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

### 2026-10-24 (score 72, +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-22 (score 71, +1)

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

### 2026-10-21 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (16)

### `pf_list_api_areas` (~42 tokens)

List the areas (tags) of the PacketFabric API with counts of read and write operations.

    Use this to orient yourself before pf_search_endpoints.

Output parameters:

- `result` (string)

### `pf_search_endpoints` (~101 tokens)

Search all PacketFabric API endpoints by keyword. Returns operation_ids to pass to
    pf_describe_endpoint / pf_call_endpoint.

Input parameters:

- `limit` (integer)
- `query` (string): Keywords, e.g. 'cloud router bgp', 'port metrics', 'aws hosted'.
- `read_only`: True = only safe reads, False = only writes.
- `tag`: Restrict to one API area from pf_list_api_areas.

Output parameters:

- `result` (string)

### `pf_describe_endpoint` (~45 tokens)

Show parameters, request body schema and response shape for one endpoint.
    Call this before pf_call_endpoint for anything you haven't used yet.

Input parameters:

- `operation_id` (string, required)

Output parameters:

- `result` (string)

### `pf_call_endpoint` (~223 tokens)

Call any PacketFabric API endpoint by operation_id.

    Reads run immediately. Writes (create/modify/delete — may create billable services)
    are only possible when the server was started with PF_ALLOW_WRITES=true, and return a
    dry-run preview unless confirm=true. Always show the user the preview and get explicit
    approval before re-calling with confirm=true.

Input parameters:

- `body`: JSON request body for POST/PUT/PATCH.
- `confirm` (boolean): Required true to actually execute a write. Without it, writes return a preview only.
- `fields`: Only return these keys from each item (dot paths allowed, e.g. 'interfaces'). Omit for all.
- `max_items` (integer): Cap on list items returned.
- `operation_id` (string, required): From pf_search_endpoints.
- `params`: Path and query parameters by name, e.g. {'port_circuit_id': 'PF-AP-LAX1-1234', 'since': '1 day ago'}. Lists are sent as repeated query params.

Output parameters:

- `result` (string)

### `pf_get_account` (~35 tokens)

Get the current PacketFabric customer account (name, account number, UUID, type).
    Good first call to confirm credentials work.

Output parameters:

- `result` (string)

### `pf_list_ports` (~139 tokens)

List the account's ports (physical access ports, LAGs, cloud ports) with speed, status, POP.

Input parameters:

- `fields`: Only return these keys from each item (dot paths allowed, e.g. 'interfaces'). Omit for all.
- `is_cloud`
- `is_lag`
- `is_ptp`
- `market`: Market code, e.g. LAX, NYC.
- `max_items` (integer): Cap on list items returned.
- `pop`: POP code, e.g. LAX1.
- `q`: Free-text filter: description, circuit id, POP, region.

Output parameters:

- `result` (string)

### `pf_get_port` (~42 tokens)

Get full details for one port by circuit id (e.g. PF-AP-LAX1-1234).

Input parameters:

- `port_circuit_id` (string, required)

Output parameters:

- `result` (string)

### `pf_list_services` (~116 tokens)

List the account's virtual circuits / services (backbone VCs, cloud connections, IX, marketplace).

Input parameters:

- `fields`: Only return these keys from each item (dot paths allowed, e.g. 'interfaces'). Omit for all.
- `max_items` (integer): Cap on list items returned.
- `port_circuit_id`: Only VCs on this port.
- `q`: Free-text filter: description, VC circuit id, interface POP/port.
- `service_type`: Filter by one or more service types.

Output parameters:

- `result` (string)

### `pf_list_point_to_point` (~67 tokens)

List point-to-point (wavelength-style) services.

Input parameters:

- `fields`: Only return these keys from each item (dot paths allowed, e.g. 'interfaces'). Omit for all.
- `max_items` (integer): Cap on list items returned.
- `q`

Output parameters:

- `result` (string)

### `pf_list_cloud_routers` (~73 tokens)

List Cloud Routers (L3 NaaS routers) on the account with ASN, capacity, regions.

Input parameters:

- `fields`: Only return these keys from each item (dot paths allowed, e.g. 'interfaces'). Omit for all.
- `max_items` (integer): Cap on list items returned.

Output parameters:

- `result` (string)

### `pf_list_cloud_router_connections` (~106 tokens)

List Cloud Router connections (AWS/Azure/GCP/Oracle/IBM, ports, IPsec) across the account or for one router.

Input parameters:

- `cloud_router_circuit_id`: Only connections on this Cloud Router (PF-L3-CUST-…). Omit for all.
- `fields`: Only return these keys from each item (dot paths allowed, e.g. 'interfaces'). Omit for all.
- `max_items` (integer): Cap on list items returned.

Output parameters:

- `result` (string)

### `pf_list_cloud_connections` (~85 tokens)

List Layer-2 cloud connections (hosted or dedicated) to AWS, Azure, Google, Oracle, IBM.

Input parameters:

- `fields`: Only return these keys from each item (dot paths allowed, e.g. 'interfaces'). Omit for all.
- `kind` (string)
- `max_items` (integer): Cap on list items returned.
- `q`

Output parameters:

- `result` (string)

### `pf_find_locations` (~154 tokens)

Find PacketFabric locations / POPs (data center, address, market, status, port types).

Input parameters:

- `any_type`: Include non-primary location types.
- `city`
- `fields`: Only return these keys from each item (dot paths allowed, e.g. 'interfaces'). Omit for all.
- `ipsec_capable`
- `market`: Market code, e.g. LAX.
- `max_items` (integer): Cap on list items returned.
- `nat_capable`
- `near_cloud_router`
- `pop`: POP code, e.g. LAX1.
- `region`: Region short name, e.g. US, UK.
- `state`

Output parameters:

- `result` (string)

### `pf_get_pricing` (~174 tokens)

Look up list pricing (MRC/NRC) for a PacketFabric product between locations. Read-only, no order is created.
    vcbwc = backbone virtual circuit bandwidth.

Input parameters:

- `location_type` (string)
- `max_items` (integer): Cap on list items returned.
- `media`: Optic media, e.g. LR, LR4.
- `product_type` (string, required)
- `service_class`: 'metro' or 'longhaul'.
- `side_a`: A-side location code, e.g. LAX1 (or market/region per location_type).
- `side_z`: Z-side location code, e.g. NYC5.
- `speed`: e.g. 1Gbps, 10Gbps, 100Gbps.
- `subscription_term`: Months.

Output parameters:

- `result` (string)

### `pf_get_traffic` (~129 tokens)

Traffic rate time series for a port (or one VC on a port).

Input parameters:

- `interval`: Bucket size in seconds, e.g. 300, 3600.
- `port_circuit_id` (string, required): Port circuit id, e.g. PF-AP-LAX1-1234.
- `since` (string): Relative start, e.g. '24 hours ago', '7 days ago'.
- `type` (string)
- `until` (string)
- `vc_circuit_id`: If given, traffic for this VC on that port instead of the whole port.

Output parameters:

- `result` (string)

### `pf_get_maintenances` (~65 tokens)

Current and upcoming maintenance windows, optionally for a POP or market.

Input parameters:

- `market`: Market code, e.g. LAX.
- `max_items` (integer): Cap on list items returned.
- `pop`: POP name, e.g. LAX1.

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 73
- 2026-10-26: 73
- 2026-10-25: 72
- 2026-10-24: 72
- 2026-10-23: 71
- 2026-10-22: 71
- 2026-10-21: 70
- 2026-10-20: 70

## Common questions

### What is the PacketFabric MCP server?

PacketFabric is an MCP server listed in the public MCP registry as io.github.PacketFabric/packetfabric-mcp. Query and manage PacketFabric NaaS: ports, virtual circuits, cloud routers, pricing, metrics. This page covers its hosted endpoint (https://mcp.packetfabric.com/mcp).

### Is the PacketFabric MCP server safe to use?

PacketFabric 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 PacketFabric MCP server expose?

PacketFabric exposes 16 tools: pf_list_api_areas, pf_search_endpoints, pf_describe_endpoint, pf_call_endpoint, pf_get_account, and 11 more. Their descriptions and schemas cost roughly 1,596 tokens of context every time the server is loaded.

### Does the PacketFabric MCP server require authentication?

No. We connected to PacketFabric without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PacketFabric MCP server still maintained?

PacketFabric 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://mcp.packetfabric.com/mcp
- Authorisation metadata: https://mcp.packetfabric.com/.well-known/oauth-protected-resource/mcp
- Changelog RSS feed: https://verifymcp.io/servers/packetfabric-packetfabric-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/packetfabric-packetfabric-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/packetfabric-packetfabric-mcp/mcp