decompose-mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited decompose-mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Decompose any text or URL into classified semantic units. Each unit gets authority level, risk category, attention score, entity extraction, and irreducibility flags. No LLM required. Deterministic. Runs locally.
pip install decompose-mcpAdd to your OpenClaw MCP config:
{
"mcpServers": {
"decompose": {
"command": "python3",
"args": ["-m", "decompose", "--serve"]
}
}
}python3 -m decompose --text "The contractor shall provide all materials per ASTM C150-20."decompose_textDecompose any text into classified semantic units.
Parameters:
text (required) — The text to decomposecompact (optional, default: false) — Omit zero-value fields for smaller outputchunk_size (optional, default: 2000) — Max characters per unitExample prompt: "Decompose this spec and tell me which sections are mandatory"
Returns: JSON with units array. Each unit contains:
authority — mandatory, prohibitive, directive, permissive, conditional, informationalrisk — safety_critical, security, compliance, financial, contractual, advisory, informationalattention — 0.0 to 10.0 priority scoreactionable — whether someone needs to act on thisirreducible — whether content must be preserved verbatimentities — referenced standards and codes (ASTM, ASCE, IBC, OSHA, etc.)dates — extracted date referencesfinancial — extracted dollar amounts and percentagesheading_path — document structure hierarchydecompose_urlFetch a URL and decompose its content. Handles HTML, Markdown, and plain text.
Parameters:
url (required) — URL to fetch and decomposecompact (optional, default: false) — Omit zero-value fieldsExample prompt: "Decompose https://spec.example.com/transport and show me the security requirements"
filter_for_llm()When using Decompose as a Python library (not MCP), filter_for_llm() pre-filters decompose output for LLM context windows:
from decompose import decompose_text, filter_for_llm
result = decompose_text(document_text)
filtered = filter_for_llm(result, max_tokens=4000)
# filtered["text"] = high-value units only (mandatory, safety-critical, financial, compliance)
# filtered["meta"]["reduction_pct"] = typically 60-80% token reductionKeeps mandatory, prohibitive, directive, conditional authority + safety-critical, compliance, financial, contractual risk + requirement, constraint, data, definition types. Configurable via keyword arguments.
Text classification is fully local. The decompose_text tool performs all processing in-process with no network I/O. No data leaves your machine.
URL fetching performs outbound HTTP requests. The decompose_url tool fetches the target URL, which necessarily involves network I/O to the specified host. This is why the skill declares the network permission in claw.json. If you do not need URL fetching, you can use decompose_text exclusively with no network access required.
SSRF protection. URL fetching blocks private/internal IP ranges before connecting: 0.0.0.0/8, 10.0.0.0/8, 100.64.0.0/10, 127.0.0.0/8, 169.254.0.0/16, 172.16.0.0/12, 192.168.0.0/16, ::1/128, fc00::/7, fe80::/10. The implementation resolves the hostname via DNS before connecting and checks all returned addresses against the blocklist. See src/decompose/mcp_server.py lines 19-49.
No API keys or credentials required. No external services are contacted except when using decompose_url to fetch user-specified URLs.
Source code is fully auditable. The complete source is published at github.com/echology-io/decompose. The PyPI package is built from this repo via GitHub Actions (publish.yml) using PyPI Trusted Publishers (OIDC), so the published artifact is traceable to a specific commit.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.