PacketFabric
REMOTE · MCP.PACKETFABRIC.COM · 2 COMPONENTS
Query and manage PacketFabric NaaS: ports, virtual circuits, cloud routers, pricing, metrics.
Available components
Last scanned (23 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 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 Security77
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 3 Nov 26 +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.
- 1 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.
- 30 Oct 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.
- 28 Oct 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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 4 Nov 2026 · Probed https://mcp.packetfabric.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=packetfabric.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 652207b8736c36780e437d2c3420df9b |
| SANs: packetfabric.com, portal.packetfabric.com, *.portal-beta.packetfabric.com, *.partners.packetfabric.com, *.packetfabric.com, *.portal.packetfabric.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 secure
Validation of mcp.packetfabric.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| packetfabric.com. | present | 2371 | 13 | Verified |
| mcp.packetfabric.com. | Verified address RRset verified with the apex keys |
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://mcp.packetfabric.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.packetfabric.com/mcp | HTTPS enforced | 301 | https://mcp.packetfabric.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 →
pf_call_endpoint ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_describe_endpoint ~45
Show parameters, request body schema and response shape for one endpoint. Call this before pf_call_endpoint for anything you haven't used yet.
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_find_locations ~154
Find PacketFabric locations / POPs (data center, address, market, status, port types).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_get_account ~35
Get the current PacketFabric customer account (name, account number, UUID, type). Good first call to confirm credentials work.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_get_maintenances ~65
Current and upcoming maintenance windows, optionally for a POP or market.
| Name | Type | Req | Description |
|---|---|---|---|
| market | – | – | Market code, e.g. LAX. |
| max_items | integer | – | Cap on list items returned. |
| pop | – | – | POP name, e.g. LAX1. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_get_port ~42
Get full details for one port by circuit id (e.g. PF-AP-LAX1-1234).
| Name | Type | Req | Description |
|---|---|---|---|
| port_circuit_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_get_pricing ~174
Look up list pricing (MRC/NRC) for a PacketFabric product between locations. Read-only, no order is created. vcbwc = backbone virtual circuit bandwidth.
| Name | Type | Req | Description |
|---|---|---|---|
| location_type | string | – | – |
| max_items | integer | – | Cap on list items returned. |
| media | – | – | Optic media, e.g. LR, LR4. |
| product_type | string | yes | – |
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_get_traffic ~129
Traffic rate time series for a port (or one VC on a port).
| Name | Type | Req | Description |
|---|---|---|---|
| interval | – | – | Bucket size in seconds, e.g. 300, 3600. |
| port_circuit_id | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_list_api_areas ~42
List the areas (tags) of the PacketFabric API with counts of read and write operations. Use this to orient yourself before pf_search_endpoints.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_list_cloud_connections ~85
List Layer-2 cloud connections (hosted or dedicated) to AWS, Azure, Google, Oracle, IBM.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_list_cloud_router_connections ~106
List Cloud Router connections (AWS/Azure/GCP/Oracle/IBM, ports, IPsec) across the account or for one router.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_list_cloud_routers ~73
List Cloud Routers (L3 NaaS routers) on the account with ASN, capacity, regions.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_list_point_to_point ~67
List point-to-point (wavelength-style) services.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_list_ports ~139
List the account's ports (physical access ports, LAGs, cloud ports) with speed, status, POP.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_list_services ~116
List the account's virtual circuits / services (backbone VCs, cloud connections, IX, marketplace).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pf_search_endpoints ~101
Search all PacketFabric API endpoints by keyword. Returns operation_ids to pass to pf_describe_endpoint / pf_call_endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.
remote · mcp.packetfabric.com
claude mcp add --transport http packetfabric-packetfabric-mcp 'https://mcp.packetfabric.com/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.