io.github.arpe-io/fastbcp-mcp
PYPI · FASTBCP-MCP
MCP server for FastBCP — high-performance parallel database export to files and cloud
Available components
Last scanned (6 days ago)
Scores higher than 0% of PyPI servers
Category Databases
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: we could not find this package in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency0
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: the registry has no such package, so there's no artefact to verify. See how to fix → View diagnostics → Fail
- License check failed: the registry has no such package, so no license can be read. See how to fix → Fail
- Maintenance check failed: the registry has no such package, so there's no release history to read. See how to fix → Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Checks we ran (6)
- Malware scan
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
Checks we could not complete (8)
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.
- Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: we could not find this package in its registry.
- Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
- Dependency health in Supply Chain SecurityDependency health could not be checked: we could not find this package in its registry.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.
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.
- 31 Oct 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Oct 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 29 Oct 26 −5
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 27 Oct 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Oct 26 0
- Known CVEs: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Provenance: Provenance check failed: the registry has no such package, so there's no artefact to verify. security
- The code this package runs automatically changed: its declared build backend security
- Dependency health: 0.99 → unverified ▼ functional
- License: pass → fail ▼ functional
- Maintenance: pass → fail ▼ functional
- Licence: MIT functional
- 25 Oct 26 0
- Provenance: pass → fail ▼ security
- The attested source repository moved: arpe-io/fastbcp-mcp security
- 22 Oct 26 −5
- Source repository: pass → fail ▼ security
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 31 Oct 2026 · Analysed pypi/fastbcp-mcp@0.1.5
Provenance Package not found
The registry answered that no such package exists, so no provenance could be looked up.
| Result | Package not found |
|---|---|
| Ecosystem | pypi |
| Reason | Package details unavailable |
Background: How many MCP packages publish verified provenance →
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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the io.github.arpe-io/fastbcp-mcp server?
io.github.arpe-io/fastbcp-mcp runs locally as a PyPI package, launched with uvx fastbcp-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 · fastbcp-mcp
claude mcp add arpe-io-fastbcp-mcp -- uvx fastbcp-mcp
What is the io.github.arpe-io/fastbcp-mcp server?
io.github.arpe-io/fastbcp-mcp is listed in the public MCP registry as io.github.arpe-io/fastbcp-mcp. MCP server for FastBCP, high-performance parallel database export to files and cloud. This page covers its PyPI package (fastbcp-mcp).
Is the io.github.arpe-io/fastbcp-mcp server safe to use?
io.github.arpe-io/fastbcp-mcp scores 0 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.
Is the io.github.arpe-io/fastbcp-mcp server still maintained?
io.github.arpe-io/fastbcp-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.arpe-io/fastbcp-mcp server?
VerifyMCP ran 6 checks on io.github.arpe-io/fastbcp-mcp, covering Malware scan, Source repository, Provenance, License and 2 more. 8 items could not be completed, a gap on our side rather than a finding about io.github.arpe-io/fastbcp-mcp: Known CVEs, Install scripts, Dependency health, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.