Flyto Indexer

io.github.flytohubPublished by GitHub account flytohubv2.10.2Updated Oct 24, 2026

Code intelligence MCP server — impact analysis, semantic search, dependency graphs

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local code-intelligence MCP server that gives coding agents a change map (callers, impact, structure) and a verification gate before they declare work done.

What you can do
Search code and concepts to locate relevant code and context for a task, with bounded, pageable results instead of whole-repository dumps. Analyze impact: show callers, dependents, likely tests, cross-project links and unresolved references before an edit. Manage tasks: keep decisions, repository rules, requirements and proof connected, run a gate before editing, validate after, and optionally grill vague requirements into a frozen plan. Audit quality and security risks, including secrets, unsafe data flow, dependencies, licenses and research-priority triage. Inspect project structure and connections, and verify whether the repository is ready to finish or merge. Record feedback on weak or m
When to use it
Useful when an AI agent edits an existing codebase where a change can cross packages, services or repositories, when several developers or agents must follow the same rules, or when private source must stay local. Best tried first on one risky refactor rather than as a replacement for your IDE, linters or CI.
Requirements
Runs locally over stdio as a Python package installed with pip; no API key, hosted account or source upload is required. Setup builds a local index and configures supported MCP clients. Built-in indexing covers Python, TypeScript, JavaScript, Vue, Go, Rust, Java, Dart and C/C++; optional language servers or SCIP data can improve precision.
Before you install
It reports evidence and does not auto-edit, auto-commit or take over the agent, but it reads the target repository, which it treats as untrusted input. Static analysis does not prove runtime behavior, and zero indexed callers is bounded evidence, not proof that dynamic callers do not exist. Generated data is kept under a local index directory and can be deleted; task state is stored in a local SQLite file with retention limits.

Installation

In SourceWeft

  1. Open Flyto Indexer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.10.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.