loopctl-mcp-server
npm
v2.89.0
Source verified
Published by mkreyman — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for loopctl — structural trust for AI development loops
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 − 6 = 94. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
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.
In the server's implementation (`lib/client-context.js:45`): 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: ecFileSync } from "node:child_process"; import os from "node:os"; function env(name) { const v = process.env[name];
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 lib/client-context.js
Tool "channel_handoffs" takes a URL/host parameter "host" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool channel_handoffs · inputSchema.properties.host
Each tool and what it can reach — statically extracted from the published source.
channel_getingests untrusted inputchannel_handoffsingests untrusted inputchannel_recentingests untrusted inputget_story_token_usagereads sensitive dataknowledge_heat_indexingests untrusted inputknowledge_indexingests untrusted inputarchive_kb_scopeno sensitive capabilitybackfill_storyno sensitive capabilitybulk_mark_completeno sensitive capabilitychannel_claimno sensitive capabilitychannel_claimsno sensitive capabilitychannel_deleteno sensitive capabilitychannel_doneno sensitive capabilitychannel_graduateno sensitive capabilitychannel_lockno sensitive capabilitychannel_locksno sensitive capabilitychannel_postno sensitive capabilitychannel_releaseno sensitive capabilitychannel_unlockno sensitive capabilityclaim_storyno sensitive capabilityclear_local_onlyno sensitive capabilitycontract_storyno sensitive capabilitycorpus_createno sensitive capabilitycorpus_deleteno sensitive capabilitycorpus_indexno sensitive capabilitycorpus_listno sensitive capabilitycorpus_searchno sensitive capabilitycorpus_statusno sensitive capabilitycreate_kb_scopeno sensitive capabilitycreate_projectno sensitive capabilitycreate_storyno sensitive capabilitycustody_claimno sensitive capabilitycustody_failuresno sensitive capabilitycustody_generate_keypairno sensitive capabilitycustody_sign_attestationno sensitive capabilitycustody_sign_claimno sensitive capabilitycustody_sign_owner_rotationno sensitive capabilitydeclare_trusted_endpointno sensitive capabilitydelete_projectno sensitive capabilitydispatchno sensitive capabilityegress_postureno sensitive capabilityegress_repinno sensitive capabilityembedding_materialize_system_corpusno sensitive capabilityembedding_reembedno sensitive capabilityembedding_statusno sensitive capabilityenroll_authenticatorno sensitive capabilityget_acceptance_criteriano sensitive capabilityget_cost_anomaliesno sensitive capabilityget_cost_summaryno sensitive capabilityget_ingestion_anomaliesno sensitive capabilityget_progressno sensitive capabilityget_sthno sensitive capabilityget_storyno sensitive capabilityget_system_articlesno sensitive capabilityget_tenantno sensitive capabilityhandoffno sensitive capabilityimport_storiesno sensitive capabilityknowledge_agent_usageno sensitive capabilityknowledge_analytics_topno sensitive capabilityknowledge_archiveno sensitive capabilityknowledge_article_statsno sensitive capabilityknowledge_assert_conflictno sensitive capabilityknowledge_bulk_deleteno sensitive capabilityknowledge_bulk_publishno sensitive capabilityknowledge_bulk_unpublishno sensitive capabilityknowledge_conflictsno sensitive capabilityknowledge_consolidationno sensitive capabilityknowledge_contextno sensitive capabilityknowledge_countno sensitive capabilityknowledge_createno sensitive capabilityknowledge_curation_logno sensitive capabilityknowledge_deleteno sensitive capabilityknowledge_distant_pairsno sensitive capabilityknowledge_draftsno sensitive capabilityknowledge_exportno sensitive capabilityknowledge_facetsno sensitive capabilityknowledge_getno sensitive capabilityknowledge_graphno sensitive capabilityknowledge_hybrid_searchno sensitive capabilityknowledge_ingestno sensitive capabilityknowledge_ingest_batchno sensitive capabilityknowledge_ingestion_jobsno sensitive capabilityknowledge_lintno sensitive capabilityknowledge_listno sensitive capabilityknowledge_llm_usageno sensitive capabilityknowledge_noveltyno sensitive capabilityknowledge_okf_exportno sensitive capabilityknowledge_okf_importno sensitive capabilityknowledge_progressive_drillno sensitive capabilityknowledge_progressive_indexno sensitive capabilityknowledge_publishno sensitive capabilityknowledge_random_walkno sensitive capabilityknowledge_resolve_conflictno sensitive capabilityknowledge_retrieval_metricsno sensitive capabilityknowledge_searchno sensitive capabilityknowledge_search_coverageno sensitive capabilityknowledge_statsno sensitive capabilityknowledge_suggest_linksno sensitive capabilityknowledge_suppressno sensitive capabilityknowledge_unpublishno sensitive capabilityknowledge_unsuppressno sensitive capabilityknowledge_unused_articlesno sensitive capabilityknowledge_updateno sensitive capabilitylist_enrolled_agent_keysno sensitive capabilitylist_projectsno sensitive capabilitylist_ready_storiesno sensitive capabilitylist_routesno sensitive capabilitylist_storiesno sensitive capabilityllm_configno sensitive capabilitymemory_forgetno sensitive capabilitymemory_graduateno sensitive capabilitymemory_listno sensitive capabilitymemory_promoteno sensitive capabilitymemory_recallno sensitive capabilitymemory_rememberno sensitive capabilityrecall_contextno sensitive capabilityrecall_referencedno sensitive capabilityrecover_capno sensitive capabilityregister_custody_owner_keyno sensitive capabilityreject_storyno sensitive capabilityreport_storyno sensitive capabilityreport_token_usageno sensitive capabilityrequest_authenticator_challengeno sensitive capabilityrequest_authenticator_revoke_challengeno sensitive capabilityrequest_reviewno sensitive capabilityresolve_projectno sensitive capabilityrestore_kb_scopeno sensitive capabilityreview_completeno sensitive capabilityrevoke_authenticatorno sensitive capabilityrevoke_trusted_endpointno sensitive capabilityset_llm_configno sensitive capabilityset_local_onlyno sensitive capabilityset_token_budgetno sensitive capabilitysignupno sensitive capabilitystart_storyno sensitive capabilityverify_all_in_epicno sensitive capabilityverify_storyno sensitive capabilityScan 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.89.0 latest |
A 94/100 | 2 | 1.13.0 | 2026-09-07 |
v2.78.2 |
A 94/100 | 2 | 1.13.0 | 2026-09-06 |
v2.78.0 |
A 94/100 | 2 | 1.13.0 | 2026-08-31 |
v2.77.0 |
A 94/100 | 2 | 1.13.0 | 2026-08-28 |
v2.76.0 |
A 94/100 | 2 | 1.12.1 | 2026-08-22 |
v2.75.0 |
A 94/100 | 2 | 1.12.1 | 2026-08-21 |
v2.74.0 |
A 94/100 | 2 | 1.12.1 | 2026-08-20 |
v2.72.0 |
A 97/100 | 1 | 1.12.1 | 2026-08-12 |
v2.71.0 |
A 97/100 | 1 | 1.12.1 | 2026-08-07 |
v2.67.0 |
A 97/100 | 1 | 1.12.1 | 2026-08-05 |
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.
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 loopctl-mcp-server --online
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.