ToolRepute
← Back to MCP database
MCPv0.1.2Registry: active

SaC — Software as Content

Give your AI agent the ability to respond with live, interactive apps that evolve.

ai.dynsoft/sac

Publication

Published

Publisher

Software-As-Content

Publisher identity: Not verified

Primary source

Official MCP Registry record

https://github.com/Software-As-Content/software-as-content-sdk

Static analysis · human review · publication

Security evidence

Scanner signals, coverage and review decisions describe different parts of this report.

How ToolRepute evaluates MCP integrations
Scan status
completed
Coverage
Sufficient source coverage
Static risk signals
8/100 · low
Finding count
3
Highest finding severity
medium
Human review
Approved review
Review freshness
Stale review
Publication
Published

Scan coverage and reliability

The scan completed with enough source coverage for ToolRepute's current review workflow. This does not verify runtime behavior.

Reliability: Meets current requirements

Scanner version
V5
Scan run
279
Last scan date
2026-09-09
Files scanned
50
Bytes scanned
412,963
Manifest
Found
Source commit
Pinned
Truncation
No

Analyzed source

https://github.com/Software-As-Content/software-as-content-sdk

Analyzed commit: 5bee0862d9ee2d29388d8a04d454d798e034eb56

Human review and publication

This historical decision does not establish current approval for the current review workflow. It may concern an older run, changed evidence or an older scanner.

Review decision
Approved review
Review date
2026-09-09
Reviewed scan run
279
Reviewed commit
5bee0862d9ee2d29388d8a04d454d798e034eb56

Publication is a decision to display evidence under ToolRepute's current rules, not a security certification, endorsement or guarantee.

Internal reviewer identity, review notes and private metadata are not displayed.

Published findings

MediumShell command execution detectedINSTALL_SHELL_EXECsrc/sac/cli.py:434Finding details and evidence

Shell command execution detected

Category: code execution

What was found

Static analysis detected an API or option capable of launching shell commands.

Why it matters

Shell execution can interact with the host system and expands the impact of unsafe input.

Evidence snippet

result = subprocess.run(

Scanner interpretation

A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.

Recommended check

Inspect the command, its inputs and call path. Check input validation and whether execution is expected and explicitly authorized.

Limitations and legitimate-use context

The presence of an execution mechanism does not show that it is unsafe or that it runs without user intent.

MediumShell command execution detectedINSTALL_SHELL_EXECsrc/sac/cli.py:539Finding details and evidence

Shell command execution detected

Category: code execution

What was found

Static analysis detected an API or option capable of launching shell commands.

Why it matters

Shell execution can interact with the host system and expands the impact of unsafe input.

Evidence snippet

result = subprocess.run(

Scanner interpretation

A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.

Recommended check

Inspect the command, its inputs and call path. Check input validation and whether execution is expected and explicitly authorized.

Limitations and legitimate-use context

The presence of an execution mechanism does not show that it is unsafe or that it runs without user intent.

MediumShell command execution detectedINSTALL_SHELL_EXECsrc/sac/server/http/http.py:1122Finding details and evidence

Shell command execution detected

Category: code execution

What was found

Static analysis detected an API or option capable of launching shell commands.

Why it matters

Shell execution can interact with the host system and expands the impact of unsafe input.

Evidence snippet

out = subprocess.run(

Scanner interpretation

A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.

Recommended check

Inspect the command, its inputs and call path. Check input validation and whether execution is expected and explicitly authorized.

Limitations and legitimate-use context

The presence of an execution mechanism does not show that it is unsafe or that it runs without user intent.

Reputation evidence

Insufficient evidence · low confidence · model v1

Evidence support score: 5/100. This is separate from risk, review and publication.

Assessment as of 2026-11-06. Live repository HEAD is not checked when this page loads.

Security evidence · 0/25LIMITED · low confidence

Reliable mapped v6 scope is not established; evidence age: aging.

Static support is capped at 18/25 before a risk deduction of ceil(riskScore/4); zero findings does not establish safety.

Last observed: 2026-09-09

  • scan record 279: Scanner v5; completed; manifest found; sufficient scope true; 50 files / 412963 bytes; 3 findings; not truncated; scanner risk score 8.Commit 5bee0862d9ee2d29388d8a04d454d798e034eb56Source evidence

Static analysis covers a bounded source scope, not runtime, dependencies in full, or hosted behavior.

Source transparency · 5/25STALE · low confidence

Completed matching public GitHub acquisition: not established (+0).

Unique primary mapping: observed (+5).

Completed matching pinned commit: not established (+0).

Completed matching source mapping: not established (+0).

Matching manifest and sufficient untruncated scope: not established (+0).

Last observed: 2026-10-04

  • source record 327: Primary mapping is incomplete or changed. Live repository HEAD is not checked by page requests.Source evidence
  • scan record 279: Scanner v5; completed; manifest found; sufficient scope true; 50 files / 412963 bytes; not truncated.Commit 5bee0862d9ee2d29388d8a04d454d798e034eb56Source evidence

A source mapping does not prove ownership. Repository availability and live HEAD are not rechecked here.

Review freshness · 0/25STALE · low confidence

Current artifact-bound approval earns 25; matching approval with unchecked live HEAD earns 8; stale, missing or rejected evidence earns 0.

Last observed: 2026-09-09

  • review record 35: Decision: approved; reviewed run 279; NEXT-11 freshness: stale.

Page requests make no upstream probe. An old approval is not approval of changed evidence.

Registry consistency · 0/10UNKNOWN · low confidence

Unique primary, normalized active/latest official registry observation earns 10 within 30 days, 5 within 90, otherwise 0.

Last observed: 2026-10-04

  • registry record 327: Normalized official record: false; active: true; latest: true; observation age: aging.

Registry consistency is a source-record observation, not identity verification or a security endorsement.

Publisher identity confidence · 0/15UNKNOWN · low confidence

No verified legal, domain or repository-ownership binding is available; free text and the registry verification flag earn no credit.

Last observed: Not available

    Publisher name and registry namespace cannot establish legal identity or ownership.

    Recorded assessment history (1)

    History starts with explicit captures in model v1. Past source and review state cannot be fully reconstructed. Page reads do not save snapshots; changes in the live assessment appear in history only after an explicit capture.

    1. 2026-10-11 · model v1 · 5/100 · low confidence · scan 2795bee0862d9ee2d29388d8a04d454d798e034eb56
      Recorded signal breakdown
      • Security evidence: 0/25 · LIMITED
      • Source transparency: 5/25 · STALE
      • Review freshness: 0/25 · STALE
      • Registry consistency: 0/10 · UNKNOWN
      • Publisher identity confidence: 0/15 · UNKNOWN

    Reputation reflects ToolRepute-observed evidence only; it is not a guarantee of security.

    Signals may be incomplete or stale. Runtime and hosted behavior may differ from scanned source.

    Publisher identity has no verified binding. Repository ownership and legal identity are not established.

    This score measures support in the available evidence, not the probability that a tool is safe.

    Registry data

    Version

    0.1.2

    Packages

    1

    Remote endpoints

    0

    Enrichment

    complete

    Last fetched

    2026-10-04

    Registry inclusion identifies the source record. It is not a ToolRepute security endorsement.

    Normalized sources

    Structured from the Official MCP Registry record.

    Enriched 2026-10-04

    github

    https://github.com/Software-As-Content/software-as-content-sdk

    Packages

    pypi· stdio· v0.1.2

    sac-sdk

    More reviewed MCP servers

    Continue exploring integrations with published ToolRepute reviews.

    Snyk API & Web MCP Server

    MCP server for Snyk API & Web — DAST scanning, findings management, and vulnerability triage

    Synapse RMCP

    Host, Docker, Compose, SSH, logs, ZFS, and file operations over MCP and CLI.

    Terraform

    Generate more accurate Terraform and automate workflows for HCP Terraform and Terraform Enterprise