Flieber
PYPI · FLIEBER
Your Flieber account in your AI assistant: sales, forecast, inventory, replenishment and more.
Available components
Last scanned (10 hours ago)
Scores higher than 67% of PyPI servers
Category E-commerce
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
- 3 of 36 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Proprietary) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 44668 tokens (~279/item across 160 items; 155 tools + 5 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 Management47
- Stability observed for 14 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
- All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 157 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
- Supports UI / widget rendering.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +15
- Tool safety: pass → unverified ▼ security
- Stability: 0.30 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.1.13 → 0.1.14 functional
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.12 → 0.1.13 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.10 → 0.1.12 functional
- Package version: 0.1.10 → 0.1.11 functional
- 28 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.8 → 0.1.10 functional
- Package version: 0.1.8 → 0.1.9 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 5 Nov 2026 · Analysed pypi/flieber@0.1.14
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 36 packages
| Packages resolved | 36 |
|---|---|
| Stale | 3 |
| 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 →
sign_in_finish ~185
Finish the sign-in `sign_in_start` began, with the one-time code the person pasted from the Flieber sign-in page. Paste the code only into the terminal or agent you started this sign-in from: it signs that one in as you. It replaces this machine's stored flieber sign-in for this environment, as `flieber login` does. Local MCP only.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The whole one-time code the Flieber sign-in page showed the person, exactly as they pasted it to you (it has a `.` near the end). |
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
sign_in_start ~109
Start signing in to Flieber when this MCP server runs where the person's browser is not (a remote sandbox): returns a link for the person to open on their own device. Local MCP only.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
signup_link ~101
The Flieber portal's sign-up page for this environment, for a person who would rather create their account and organisation in the browser. Needs no sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
status ~109
What this key can see: its organisation, and which of the resources the other capabilities need it is granted and which it lacks. Call it first; a capability whose grant is missing fails with grant_missing.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
subscription_page ~119
The Flieber app's subscription page for the organisation, to add a payment method, pick a plan or reactivate it. The CLI opens it in the browser; on the MCP, give the person the link. Needs a Flieber sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
subscription_status ~117
The organisation's current plan as Flieber bills it: plan name, status (trialing, active, paused, …), trial end and whether a payment method is on file, with the next step. Needs a Flieber sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
supply_chain_product_locations ~171
Where each product sold in a store is fulfilled from and stored, as the Flieber app's advanced mapping of products to locations shows it: the location, whether it is the product's own choice or the store's default, and the store's defaults. Needs a Flieber sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | The page, from 1; meta.next_page names the next one. |
| product_id | – | – | Only this product. |
| store_id | – | – | Only this store (selling account). |
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
supply_chain_product_locations_set ~300
Map products to locations per store: the fulfillment and storage location of a product sold in a store, or the store's default, as the Flieber app's advanced mapping does. A commit replaces the mapping (the preview shows the previous one; map again to undo), and Flieber then deletes the per-product replenishment parameters and shipment lead times that no longer apply, across the organisation (the preview warns); they are not restored by mapping back. Preview first (commit=false), then commit with the preview_id. A commit makes Flieber recalculate the inventory forecast in the background (meta.warnings says so): inventory forecast reads may show old numbers for a few minutes. Needs a Flieber sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | boolean | yes | false: preview only; true: apply, with the preview_id from the preview of the same arguments. |
| items | array | yes | One item per product and store, for at most 4 products per call (one read each). |
| preview_id | – | – | From a preview of these arguments. Required when commit is true. It does not expire; after a credential change, run the preview again. |
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
tenants ~127
List the Flieber organisations your sign-in belongs to, with the ids to pass as `tenant`. Needs a Flieber sign-in (OAuth); an API key reads only its own organisation.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | The page, from 1; meta.next_page names the next one. |
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
trends ~255
Trends per product × store: units over the previous 30, 90 and 365 days (adjusted sales), forecast units over the next 30 and 90 days, revenue over the previous and next 30 days, and the 30-day relative change, as Flieber last computed them. Rows carry names, not ids. For actual sales over a period you choose, compared with a year earlier, use `sales_trends`.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency of the revenue columns. |
| limit | integer | – | Rows per page. |
| offset | integer | – | Zero-based row offset: `meta.next_offset` of the previous page. |
| product_ids | – | – | Only these product ids (from `listings`). |
| search | – | – | Substring of the product code or name. |
| store_ids | – | – | Only these store ids (from `listings`). |
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
| tier | – | – | Only products of this tier. |
No output schema declared.
No examples provided.
webhooks_page ~136
The Flieber app's Developers page, whose Webhooks section is where the organisation's webhook endpoints are added, tested and watched. The CLI opens it in the browser; on the MCP, give the person the link. It gives the app's page, not a webhooks-console login link. Needs a Flieber sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant | – | – | The Flieber organisation for this call: its id (`org_…`) or its UUID, as `tenants` lists them. Needed when your sign-in belongs to several organisations; omit it to use the default. An API key reads… |
No output schema declared.
No examples provided.
How do I install the Flieber MCP server?
Flieber runs locally as a PyPI package, launched with uvx flieber 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 · flieber
claude mcp add com-flieber-flieber -- uvx flieber mcp
What is the Flieber MCP server?
Flieber is an MCP server listed in the public MCP registry as com.flieber/flieber. Your Flieber account in your AI assistant: sales, forecast, inventory, replenishment and more. This page covers its PyPI package (flieber).
Is the Flieber MCP server safe to use?
Flieber scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Flieber MCP server expose?
Flieber exposes 155 tools: ping, status, tenants, account_status, list_terms, and 150 more. Their descriptions and schemas cost roughly 44,301 tokens of context every time the server is loaded.
Is the Flieber MCP server still maintained?
Flieber 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 Flieber MCP server under?
Flieber declares the Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the Flieber MCP server?
VerifyMCP ran 16 checks on Flieber, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. One item could not be completed, a gap on our side rather than a finding about Flieber: Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.