Mmcp.market

Flyto Core MCP server

by flytohub·io.github.flytohub/flyto-core·v2.12.6·483 stars

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

B75/100grade B
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
Established

483 stars311 downloads/wk

Reviews

Write one

Nobody has reviewed Flyto Core yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Flyto Core tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

2 medium
  • Code scan809 source files scanned15/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10

Findings (2)

  • mediumeval / new Function usedexec.eval
    flyto_core-2.12.6/src/core/enterprise/state_machine/engine.py: …ression evaluation result = eval(expression, safe_context) re…
  • mediumsubprocess with shell=Trueexec.shell-true
    flyto_core-2.12.6/src/core/modules/atomic/shell/exec.py: …ll injection attacks. # Only enable shell=True when absolutely necessary (e.g., shell …
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Flyto Core in Claude Code, Cursor or VS Code

claude mcp add flyto-core -- uvx flyto-core
Add to Cursor

What the publisher says

From the Flyto Core repository's README, as published. We do not edit it. Read it on GitHub

Flyto2 Core

AI said it finished. Flyto2 shows the proof.

A Python execution engine for AI agents. It runs browser and API work as explicit steps, records what every step did, and replays from the step that failed — instead of re-running the whole job.

The current public inventory is 481 registry-backed modules across 89 catalog categories, including triggers, queue modules, workflow versioning, metering hooks, browser automation, API calls, data transforms, verification, files, and crypto.

<!-- mcp-name: io.github.flytohub/flyto-core -->

flyto2.com · Cloud Automation · Documentation · MCP Docs · YouTube

Try it in 30 seconds

pip install flyto-core[browser] && playwright install chromium
flyto recipe competitor-intel --url https://github.com/pricing
Step  1/12  browser.launch         ✓      420ms
  Step  2/12  browser.goto           ✓    1,203ms
  Step  3/12  browser.evaluate       ✓       89ms
  Step  4/12  browser.screenshot     ✓    1,847ms  → saved intel-desktop.png
  Step  5/12  browser.viewport       ✓       12ms  → 390×844
  Step  6/12  browser.screenshot     ✓    1,621ms  → saved intel-mobile.png
  Step  7/12  browser.viewport       ✓        8ms  → 1280×720
  Step  8/12  browser.performance    ✓    5,012ms  → Web Vitals captured
  Step  9/12  browser.evaluate       ✓       45ms
  Step 10/12  browser.evaluate       ✓       11ms
  Step 11/12  file.write             ✓        3ms  → saved intel-report.json
  Step 12/12  browser.close          ✓       67ms

  ✓ Done in 10.3s — 12/12 steps passed

Screenshots captured. Performance metrics extracted. JSON report saved. Every step traced.

What happens when step 8 fails?

With a shell script you re-run the whole thing. With flyto-core:

flyto replay --from-step 8

Steps 1–7 are instant. Only step 8 re-executes. Full context preserved.

How is this different?

3 recipes to try now

# Competitive pricing: screenshots + Web Vitals + JSON report
flyto recipe competitor-intel --url https://competitor.com/pricing

# Full site audit: SEO + accessibility + performance
flyto recipe full-audit --url https://your-site.com

# Web scraping → CSV export
flyto recipe scrape-to-csv --url https://news.ycombinator.com --selector ".titleline a"

Every recipe is traced. Every run is replayable. See all 41 recipes ->

Install

pip install flyto-core            # Core engine + CLI + MCP server
pip install flyto-core[browser]   # + browser automation (Playwright)
playwright install chromium        # one-time browser setup

Write Your Own Workflows

Recipes are just YAML files. Write your own:

name: price-monitor
steps:
  - id: open
    module: browser.launch
    params: { headless: true }

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Flyto Core: common questions

Is Flyto Core MCP server safe?
Mostly: it is graded B (75/100). Read the Flyto Core safety report
How do I install Flyto Core?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Flyto Core need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Flyto Core maintained?
The last commit was 14 days ago (2026-09-23). The latest release is v2.12.6.
What can I use instead of Flyto Core?
Servers from other publishers that do the same job: Behavior Runtime MCP server, Open Computer Use MCP server and BriefGate MCP server. Compare all Flyto Core alternatives.

Alternatives to Flyto Core

Same job from other publishers: the closest match first, then the best rated.

All Flyto Core alternatives →
  • Behavior Runtime MCP
    In-browser ~60Hz behavior tree execution engine with reactive triggers and blackboard projection.
    A
  • Open Computer Use
    Give any LLM its own computer — Docker sandboxes with bash, browser, docs, and sub-agents
    B
  • BriefGate
    Client intake: files, copy and logins from clients, from the browser or your AI agent.
    A
  • MCP Browser
    Browser automation using the user's Chromium session — JS execution, auth, and anti-bot support.
    B
  • SeleniumBase MCP
    Stealthy browser automation, testing, and web-scraping via CDP Mode.
    A

More from flytohub →