Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Flyto Core

PYPI · FLYTO-CORE

Execution engine for AI agents. 412 modules: browser, file, Docker, data, crypto.

Available components

pypi · flyto-core 0
0 this week 0 Trust /100

Last scanned (2 hours ago)

Scores higher than 0% of PyPI servers

Recent critical change

CVE-2026-67429 affects this package (2 Aug 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security69
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
  • Declares code that runs automatically (setup.py) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 0 of 21 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Licence could not be checked: the licence is declared in free text we could not match to a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 35 days ago).Pass
  • 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 package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, 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 →

Changelog

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 0
    • Provenance: unverified → fail ▼ security
  • 3 Nov 26 0
    • Provenance: fail → unverified ▼ security
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 29 Oct 26 0
    • Malware scan: unverified → pass ▲ security
  • 22 Oct 26 0
    • Security disclosure: pass → fail ▼ functional
  • 18 Oct 26 0
    • Malware scan: pass → unverified ▼ security
  • 17 Oct 26 0
    • Malware scan: unverified → pass ▲ security
Diagnostics

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/flyto-core@2.12.6

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 2 scripts
Hook Tier Command
build_backend allowlisted setuptools.build_meta
setup_py unreviewed <setup.py, unreviewed>

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 13 findings
ID CVE Severity Vector Fix available
GHSA-2956-977x-2w3r CVE-2026-67429 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H yes
GHSA-794r-5rp2-fpg8 CVE-2026-55787 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N yes
GHSA-c9hr-64h3-gxpc CVE-2026-67424 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N yes
GHSA-hr7p-wg7r-hg9m CVE-2026-67427 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-pgwh-4jj4-qm8v CVE-2026-67428 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N yes
GHSA-qq9q-xgm3-xv9g CVE-2026-67425 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N yes
PYSEC-2026-2481 CVE-2026-55787 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N yes
PYSEC-2026-3568 CVE-2026-67429 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H yes
PYSEC-2026-3569 CVE-2026-67424 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N yes
PYSEC-2026-3570 CVE-2026-67427 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N yes
PYSEC-2026-3571 CVE-2026-67426 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N yes
PYSEC-2026-3572 CVE-2026-67428 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N yes
PYSEC-2026-3573 CVE-2026-67425 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 21 packages
Packages resolved 21
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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.

Install

How do I install the Flyto Core MCP server?

Flyto Core runs locally as a PyPI package, launched with uvx flyto-core. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · flyto-core

# add to Claude Code
claude mcp add flytohub-flyto-core -- uvx flyto-core