Skills/npm/submitator-mcp

submitator-mcp@0.1.3

VERIFIED

Publisher claims: "Launch your clients' products on up to 110 directories each from Claude, ChatGPT, Cursor or VS Code." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher submitator · publishing for 16 daysInstalls 0Last detonated 1 h ago
$claude mcp add submitator-mcp -- npx -y submitator-mcp
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
SUBMITATOR_API_KEYConfiguration, not credentials: SUBMITATOR_API_URL, SUBMITATOR_FILES_DIR
Where it talks to
submitator.com (its own)Also x.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
what the tools do when called with real credentials

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

$vet-skills run --secrets SUBMITATOR_API_KEY=submitator.com -- npx -y submitator-mcp

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) on 2026-11-15 and scored it 90/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 32 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
12sprocessdependency install exit 0
32sclaimed24 tools: whoami, list_projects, get_project, create_project, update_project, delete_draft, set_logo, add_screenshot, remove_image, preview_launch, find_directories, project_directories, launch_project, add_directories, list_listings, list_events, get_badge, verify_badge, create_report, get_report, save_report_file, get_share_link, create_share_link, delete_share_link
32stools926bae7d5067ca6c
32stools54cf9ea8700609fd
32stools7136e761eae954f9
32stools48a9926bc3597d04
32stools8531b0087cc6aff1
32stools483971f6c388fde9
32stools99229352ae5d4bc0
32stools27317ff8d47d73d2
32stools009ae35f73741f8a
32stoolsfe15e821bc75b255
32stools10100f1ed1541573
32stools1494bf173394d9b1
32stoolsed3d04b0f1513376
32stools53694528ad37ded4
32stoolsac5c81357b1d3f3f
32stoolsb7413984f8a9190c
32stools7047bf7bd6a8081b
32stools8926987efa0113c8
32stools0d9ed25141b3e02a
32stools6b18a322a016c68b
32stools06261f38880b26fc
32stoolsda3b7add844044da
32stools0d24395e903052cd
32stools2dccee106e682250
32sprocessscript backend runs setup only
32sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagedist/server.js:1 · npx invocation of non-well-known package — may execute untrusted code// One factory for both entries: stdio (the npx package) and remote HTTP.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/tools/images.js:69 · npx invocation of non-well-known package — may execute untrusted code? 'Adds one screenshot to a project (5 at most), from a public URL or, with the npx package, a local file. Each call adds another one: a repeated call adds the same image twice.'Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/tools/images.js:50 · npx invocation of non-well-known package — may execute untrusted code… URL is fetched right away (a failed fetch answers image_unreachable); with the npx package a local file inside SUBMITATOR_FILES_DIR (or the folder the server started in) …Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/result.js:50 · npx invocation of non-well-known package — may execute untrusted code… key. Put an agency key in this MCP server's config (SUBMITATOR_API_KEY for the npx package, the Authorization header for the remote server). Keys are created in the agency…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/stdio.js:2 · npx invocation of non-well-known package — may execute untrusted code// The npx entry: `npx -y submitator-mcp` with SUBMITATOR_API_KEY in the env.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈62 tok
1 file · 31 in bundle
Tool list per prompt
≈6,267 tok
24 tools · 261 per tool
Handshake
1649 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 186

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

No advisories in OSV for submitator-mcp@0.1.3 as of 49 min ago. This is the package itself, not its dependencies.