PacketFabric
PYPI · PACKETFABRIC-MCP · 2 COMPONENTS
Query and manage PacketFabric NaaS: ports, virtual circuits, cloud routers, pricing, metrics.
Available components
Last scanned (3 hours ago)
Scores higher than 85% of PyPI servers
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to PacketFabric/public-mcp). View diagnostics → Pass
- Clear OSI-approved license (MPL-2.0).Pass
- Actively maintained (last published 15 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1782 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 Management70
- Stability observed for 21 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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 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.
- 27 Oct 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.
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 · Analysed pypi/packetfabric-mcp@0.2.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | PacketFabric/public-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/PacketFabric/public-mcp/.github/workflows/publish.yml@refs/tags/v0.2.4 |
| Rekor log index | 3344370014 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:b9b0939246b9c7eb2a37c904b5161d0690610a1ca8095fe7468872412831e749 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~219
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 ~44
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 ~34
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 ~173
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 ~41
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 ~100
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 runs locally as a PyPI package, launched with uvx packetfabric-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · packetfabric-mcp
claude mcp add packetfabric-packetfabric-mcp -- uvx packetfabric-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 PyPI package (packetfabric-mcp).
Is the PacketFabric MCP server safe to use?
PacketFabric scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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,587 tokens of context every time the server is loaded.
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.
What licence is the PacketFabric MCP server under?
PacketFabric declares the MPL-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.