MCP.Market

Silex MCP server

by silex-tec·io.github.silex-tec/silex·v0.11.38

Local-first MCP server that reconstructs architecture, workflows and business rules from your code.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Silex yet.

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

Silex tools (100, 18 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • create_workspacewrite action
  • discover_entity_candidates

    Detect candidate domain entities from unknown names left by the LLM rule extractor.

  • discover_featureswrite action

    Run full feature discovery pipeline for a workspace. Uses Leiden communities if available, falls back to lexical grouping.

  • discover_workflows

    Discover functional workflows (event-handler → method chain → entity touched).

  • generate_domain_jsons

    Generate the 5 Silex V6.1 domain JSONs from the Neo4j archaeology graph.

  • generate_domain_report
  • get_bridges

    Get bridge nodes — classes that connect different communities. These are coupling points between bounded contexts.

  • get_class_references

    Get all references for a class — who calls it and who it calls. Shows relationship types (INHERITS, INSTANTIATES, CALLS, etc.).

  • get_code_communities

    Hierarchical code communities (Leiden) with members + labels — tier-aware.

  • get_communities

    List detected communities (Leiden clusters) for a workspace. Returns communities with members, cohesion scores, and bridge nodes.

  • get_domain_map

    Get DDD domain map — communities classified as core_domain, supporting, infrastructure, shared_kernel, or generic_subdomain.

  • get_field_graph_summary

    Resumo do grafo de fields no workspace: nodes + relationships.

  • get_field_operations

    Lista as operações que leem/escrevem o field ``declaring_class.field_name``.

  • get_operation_detail

    Retrieve all rules for a specific entity+method, reading from the materialized JSON at .silex/domain/{workspace_id}/business_logic.json.

  • get_operation_fields

    Lista os fields lidos/escritos/unresolved por uma operação.

  • get_operation_workflow_context

    Retorna contexto operation-first para uma operation específica.

  • get_published_domain

    Retrieve published V6.1 domain JSONs.

  • get_rules_by_ids

    Batch-fetch rules from the materialized ``business_logic.json``.

  • get_state_machines

    Retorna as state machines (FSMs) materializadas em ``.silex/domain/{workspace_id}/state_machines.json``.

  • get_structural_findings
  • get_workflows_for_operation

    Return workflows whose steps reference (entity, method).

  • get_workspace_stats
  • ingest_field_graph

    Persiste no Neo4j os eixos de fields da #284 (declared + usage).

  • label_communities

    Gera labels semânticos DDD para communities via LLM.

  • list_extractors

    List all registered extractors with metadata.

  • list_pending_reviews

    List extracted artifacts pending human review (status: draft or review).

  • list_unresolved_field_references

    Lista SilexFieldReference (usages unresolved).

  • publish_domainwrite action

    Publish accepted artifacts as the final V6.1 domain JSONs.

  • rescan_workspace

    Re-dispara o scan de um workspace EXISTENTE (J1-RESCAN-1 #1071).

  • review_artifact

    Record a human decision on an extracted artifact.

  • run_extractorwrite action

    Dispatch to a registered extractor and return its serialized output.

  • search_code_semantic

    Semantic code search using Qdrant vector embeddings. Find code by natural language description.

  • silex.business_logic.submitwrite action

    Persiste **rules extraídas pelo LLM do cliente** (com provenance) (#675).

  • silex.business_mermaid.runwrite action

    Materializa ``business_mermaids.json`` a partir de ``business_logic.json``.

  • silex.business_mermaid.status

    Status do ``business_mermaids.json`` materializado.

  • silex.code_decision.community_story

    Story da comunidade Contrato/SGPC (``story_kind=archaeology_process``).

  • silex.code_decision.context_pack

    Context pack arquitetural do runner: índice de decisão citável.

  • silex.code_decision.file_story

    História de um arquivo/god class: "como este arquivo nasceu?".

  • silex.code_decision.symbol_story

    História de um método/símbolo: "de onde saiu este método?".

  • silex.code_symbol.search

    Busca semântica de **símbolos de código** (parent-resumo).

  • silex.communities.status

    Status agregado de communities/packages do workspace.

  • silex.community.code_pack
  • silex.contract.fact.generate

    Gera o **contrato de fato** (``fact_contract/v1``) de um escopo coeso.

  • silex.contract.goal.get

    Busca um **goal de produto** por id (read-only).

  • silex.contract.goal.list

    Lista os **goals de produto** do contrato (read-only).

  • silex.contract.goal.upsert

    Cria/atualiza um **goal de produto** (``contract_goal/v2``).

  • silex.contract.ledger.correct

    Corrige campos de um requisito (curadoria do revisor — **não** geração).

  • silex.contract.ledger.generate_batch

    Gera o **ledger do domínio em batch** — uma entrada ``proposed`` por comunidade.

  • silex.contract.ledger.list_proposed

    Lista os requisitos **candidatos** (``status: proposed``) do ledger.

  • silex.contract.ledger.promote

    Promove um candidato ``proposed`` para **normativo** (``active``).

  • silex.contract.ledger.propose

    Propõe um **requisito candidato** (``proposed``) a partir do fato.

  • silex.contract.ledger.reject

    Rejeita (descarta) um candidato ``proposed`` — remove do ledger.

  • silex.contract.search

    Busca semântica no **contrato de produto** (goals + histórias).

  • silex.curation.budget

    Monta o **orçamento de curação** faseado do domínio (#634).

  • silex.curation.community_nature

    Monta o **pacote de review assistido** de natureza por comunidade (#632).

  • silex.entity.pack
  • silex.extractors.describe

    Detalha extractor + deps transitivas + ordem de execução recomendada.

  • silex.extractors.get_output

    Metadata do artifact por default. Conteúdo só com ``include_content=True`` E ``size_bytes <= max_bytes`` — caso contrário devolve erro estruturado ``artifact_too_large``.

  • silex.extractors.list

    Lista extractors registrados em ``create_default_registry``.

  • silex.extractors.runwrite action

    Roda 1 extractor isolado ou com deps. Output gravado como artifact em ``.silex/runs/{run_id}/outputs/{extractor_id}.json``.

  • silex.extractors.run_batchwrite action

    Roda N extractors em UM ``run_id``, 1 stage por extractor.

  • silex.extractors.validate_output

    Valida artifact: existe em disco, hash bate, JSON parseia, reporta top-level keys/counts. Sem payload bruto.

  • silex.feedback.investigate_rule

    Investiga uma rule suspeita comparando evidência com o código-fonte.

  • silex.feedback.list_extractor_gaps

    Lista gaps de extractor de um workspace, com agregados por gap_type.

  • silex.feedback.report_extractor_gap

    Registra um gap de extractor em JSONL local (com dedup enquanto open).

  • silex.fsm_evidence.build_transitions_offline

    Gera transitions.catalog.json deterministico (Camada 1, sem LLM) — #334.

  • silex.fsm_evidence.inspect

    Relata presenca/entries dos artifacts FSM evidence-first.

  • silex.fsm_evidence.runwrite action
  • silex.llm_provider.status

    Status de configuração de um provider LLM — sem chamada de rede.

  • silex.packages.get

    Resolve um pacote por ``package_id`` ou ``community_id``.

  • silex.packages.list

    Cataloga pacotes de comunidade executáveis.

  • silex.packages.merge

    Recompõe artifacts workspace-level a partir de package runs (#253).

  • silex.packages.runwrite action

    Wrapper fino sobre :func:`run_community_package` (#253).

  • silex.phase5_narrative.runwrite action
  • silex.phase5_narrative.status

    Status do enriquecimento phase5_narrative no workspace.

  • silex.pipeline_run.artifactswrite action

    Lista artifact refs do run. Filtros opcionais por ``kind``, ``stage_id`` ou ``metadata.target``. Sem conteúdo.

  • silex.pipeline_run.createwrite action

    Cria manifest ``pipeline_run.v1`` vazio/running.

  • silex.pipeline_run.getwrite action

    Carrega ``run_id`` e devolve summary do manifest.

  • silex.pipeline_run.listwrite action

    Lista summaries curtos de manifests em ``run_root``.

  • silex.pipeline_run.resumewrite action

    Gera plano de resume (``execute=False``) ou executa quando suportado (``execute=True`` + ``mode=community`` + ``package_id``).

  • silex.pipeline_run.statuswrite action

    Status operacional curto: status do run, contagens por status de stage, warnings/errors, timestamps, flags has_running/has_failed/ has_invalidated.

  • silex.product_surface.diagnose

    Diagnóstico canônico da superfície de produto SGPC.

  • silex.qdrant_gate.diagnose

    Diagnóstico da superfície Qdrant sem indexar.

  • silex.qdrant_gate.runwrite action

    Gate de busca semântica scoped sobre o staging/package.

  • silex.refactoring.crosscutting

    Mede o **espalhamento de transversais curados** pelos domínios do grafo.

  • silex.review.surface_status

    Status unificado da superfície de Review (state/transition/panel).

  • silex.roadmap.score

    Alignment score estratégico do roadmap (read-only, determinístico).

  • silex.runner.arch_findings

    Diagnóstico read-only do gate de arquitetura de uma issue.

  • silex.runner.claim

    Claima uma issue (Project status → ``In Progress``) sem rodar coder.

  • silex.runner.comment_gate

    Posta um comentário de gate (audit trail) sem mudar status.

  • silex.runner.enqueue

    Enfileira uma issue para o runner (label + Project status ``Todo``).

  • silex.runner.manifest

    Manifest read-only de uma execução do runner para a issue.

  • silex.runner.merge_ready

    Decisão read-only de prontidão de merge de uma issue (não mergeia).

  • silex.runner.plan

    Plano determinístico (prompt → branch → worktree → comandos) read-only.

  • silex.runner.queue

    Fila read-only de issues abertas elegíveis ao runner.

  • silex.runner.set_blocked

    Marca uma issue como ``Blocked`` com motivo, deixando comentário.

  • silex.runner.set_done

    Marca o Project status como ``Done`` — guardado pelo gate de arquitetura.

  • silex.runner.status

    Status canônico read-only de uma issue do runner.

  • silex_export_materialized

    Export canonical materialized JSONs of a workspace to ``target_dir``.

  • validate_domain_jsons

    Validate previously generated domain JSONs against V6.1 schemas.

Public scan report

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

no findings
  • Code scan529 source files scanned25/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
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Silex compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
100
the typical server has 7
Tools that change things
18%
typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 69 read · 3 create · 15 change · 1 send or post · 12 run or deploy

Install Silex in Claude Code, Cursor or VS Code

claude mcp add silex -- uvx silex-archaeology
Add to Cursor

What the publisher says

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

Silex — evidence-based code archaeology

Understand the codebase before changing the code.

Silex reconstructs architecture, dependencies, workflows and business rules from your source code — and serves that understanding to your AI coding agents via MCP. Every claim is anchored to file:line with a verified quote. What Silex can't prove, it tells you.

Local-first. Your code never leaves your machine. No account, no card, no telemetry.

→ Site & docs: https://silex.tec.br · Concepts · MCP tool reference · llms.txt

Install (free tier)

# Python 3.10+
pip install silex-archaeology

Until the PyPI release lands you can install the wheel from

Releases:

pip install https://github.com/silex-tec/silex/releases/latest/download/silex_archaeology-py3-none-any.whl

Connect it to your MCP client (Claude Code, Cursor, Claude Desktop, Windsurf, Cline, Continue, Zed) — stdio config:

{
  "mcpServers": {
    "silex": { "command": "silex-mcp-server", "args": ["serve", "--stdio"] }
  }
}

Full install guide (Windows/PowerShell notes included): https://silex.tec.br/docs/

Try it on a real codebase

Clone Microsoft's eShop (MIT) and point a scan at it — the Concepts page shows the community graph, the recovered order state machine and anchored findings from that exact scan, so you can compare your output against a published reference.

What you get (free)

out of the way by default

  • Local MCP server, full codebase scan (C#, JS/TS, Java, PHP, COBOL, VB…)
  • Community map — the real shape of the system, vendor/generated classified
  • Evidence anchored to file:line, confidence with provenance
  • Unknown-territory detection: what can't be proven is flagged, not guessed
  • Shareable evidence report
  • Works with the AI seat you already pay for

Pro tier (team workspaces, deep architecture visualization, refactoring trust contracts): coming soon — join the waitlist.

Issues & feedback

Bug reports and field feedback are welcome in Issues. The engine is proprietary; this repository hosts distribution, documentation and the public roadmap conversation.

© 2026 SILEX. All rights reserved.

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

Silex: common questions

Is Silex MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Silex safety report
How do I install Silex?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Silex need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Silex maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.11.38.
How does Silex compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 100 (the typical server has 7); tools that change things 18% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.