Facets Module MCP Server

facets-module-mcp PyPI v0.1.21

Published by facets-cloud — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Facets Module MCP

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Shell/command execution in server code (facets_mcp/utils/ftf_command_utils.py)MTC-SRC-002

In the server's implementation (`facets_mcp/utils/ftf_command_utils.py:56`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: config result = subprocess.run( ["git", "config", "--get", "remote.origin.url"], cwd=wor

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server facets_mcp/utils/ftf_command_utils.py

medium Tool "edit_file_block" can modify the filesystemMTC-CAP-002

Tool "edit_file_block" can write, overwrite or delete files (keyword "edit_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool edit_file_block

low Mutating tool "edit_file_block" declares no destructiveHintMTC-CAP-005

Tool "edit_file_block" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool edit_file_block

Tools 30

Each tool and what it can reach — statically extracted from the published source.

  • edit_file_blockwrites files
  • get_deployment_logsreads sensitive data
  • get_local_modulesingests untrusted input
  • list_filesreads sensitive data
  • read_filereads sensitive data
  • add_import_declarationno sensitive capability
  • check_deployment_statusno sensitive capability
  • create_or_update_intentno sensitive capability
  • discover_terraform_resourcesno sensitive capability
  • find_output_types_with_providerno sensitive capability
Show 20 more tools ↓
  • FIRST_STEP_get_instructionsno sensitive capability
  • fork_existing_moduleno sensitive capability
  • generate_module_with_user_confirmationno sensitive capability
  • get_intentno sensitive capability
  • get_output_type_detailsno sensitive capability
  • list_all_intentsno sensitive capability
  • list_all_output_typesno sensitive capability
  • list_modules_for_forkno sensitive capability
  • list_test_projectsno sensitive capability
  • mark_module_as_publishedno sensitive capability
  • push_preview_module_to_facets_cpno sensitive capability
  • register_output_typeno sensitive capability
  • search_modules_after_confirmationno sensitive capability
  • test_already_previewed_moduleno sensitive capability
  • validate_moduleno sensitive capability
  • write_config_filesno sensitive capability
  • write_generic_fileno sensitive capability
  • write_outputsno sensitive capability
  • write_readme_fileno sensitive capability
  • write_resource_fileno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.21 latest A 93/100 3 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/facets-module-mcp/badge.svg)](https://mcptrustchecker.com/registry/facets-module-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/facets-module-mcp"><img src="https://mcptrustchecker.com/registry/facets-module-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/facets-module-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan facets-module-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools