mcp-semclone (SemClone/mcp-semclone) is an MCP server listed on the M8ven Trust Index. It scores 35 out of 100, grade F. It declares 14 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
F
Warning
35/100

mcp-semclone

Enables LLMs to perform software composition analysis including license detection, vulnerability assessment, SBOM generation, and policy validation using the SEMCL.ONE toolchain.

→ SemClone/mcp-semclone· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

SemClone

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — generate_legal_notices_from_purls (line 1654: Path(purl_file_path).unlink(missing_ok=True))
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes14 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

scan_directory

FIRST STEP: Scan a directory for compliance issues using purl2notices.

check_package

Check a specific package using intelligent tool selection.

validate_policy

Validate if licenses are approved or rejected for a specific project/distribution type.

get_license_obligations

Get detailed obligations for specified licenses.

check_license_compatibility

Check if two licenses are compatible for use together.

get_license_details

Get comprehensive details about a specific license.

analyze_commercial_risk

Analyze commercial licensing risk for a project.

validate_license_list

QUICK answer to: "Can I ship this with these licenses?"

generate_legal_notices

PRIMARY TOOL: Generate legal notices by scanning source code directly (DEFAULT - FAST).

generate_legal_notices_from_purls

ALTERNATIVE TOOL: Generate legal notices from PURL list (downloads from registries - SLOWER).

download_and_scan_package

Download package source from registry and perform comprehensive analysis.

generate_sbom

Generate a Software Bill of Materials (SBOM) in CycloneDX format using purl2notices.

scan_binary

Scan binary files for OSS components and licenses using BinarySniffer.

run_compliance_check

UNIVERSAL COMPLIANCE WORKFLOW: One-shot compliance check for ANY project type.

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configMCP_LOG_LEVEL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

14/14 tools missing one or more hints — scan_directory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_package (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); validate_policy (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +11 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

3 tools perform destructive updates without destructiveHint — scan_directory deletes at line 519 (os.unlink(temp_json_path)); generate_legal_notices_from_purls deletes at line 1654 (Path(purl_file_path).unlink(missing_ok=True)); download_and_scan_package deletes at line 1846 (Path(temp_cache).unlink(missing_ok=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — generate_legal_notices_from_purls (line 1654: Path(purl_file_path).unlink(missing_ok=True))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

generate_legal_notices_from_purls: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/semclone/mcp-semclone?variant=verified)](https://m8ven.ai/mcp/semclone/mcp-semclone)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 8845cc83065eedfb210e1cb726aa998a143f310d
code hash: afe68e6a81894e691c35d9ee9e83c6a0488ee400d011535d95518b17a982c677
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client