Skills/Glama/setlog-mcp

setlog-mcp@0.2.0

VERIFIED· not started

Publisher claims: "Enables authenticated preparation and posting of encrypted MP4 videos to a user's setlog account, including comments, batch and scheduled posting, and date-based post search through a local stdio interface." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher shirafukayayoi · publishing for 5 daysInstalls 0Last detonated 3d ago
$npx skills add setlog-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
SETLOG_API_KEYConfiguration, not credentials: SETLOG_MCP_COUNTRY, SETLOG_MCP_FFPROBE, SETLOG_MCP_MAX_VIDEO_BYTES, SETLOG_MCP_REGION, SETLOG_MCP_STATE_DIR
Where it talks to
no vendor host named in the codeAlso newchatapi.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names newchatapi.com as well as its own vendor. The guard injects SETLOG_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- <the server's command>

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-11 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedtests/test_posting.py:241 · Python subprocess execution detectedprocess = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedsrc/setlog_mcp/upload.py:68 · Python subprocess execution detectedprocess = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedtests/test_posting.py:211 · Python subprocess execution detectedprocess = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

Cost to the agent

Instructions loaded
≈37 tok
1 file · 27 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

setlog-mcp@0.2.0 safety verdict: Verified (not started) — KillerSkills