Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Submitator

NPM · SUBMITATOR-MCP · 2 COMPONENTS

Launch your clients' products on up to 100 directories each from Claude, ChatGPT, Cursor or VS Code.

74 Trust /100

Last scanned (5 hours ago)

Scores higher than 48% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3260 tokens (~135/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: fail → pass ▲ functional
  • 31 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.0 → 0.1.1 functional
  • 30 Oct 26 56

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/submitator-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 24 exposed · ~2,923 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_directories ~202

Submits a launched project to more directories from its free allowance (no launch is spent). Refuses unless confirm_selected equals the directory count preview_launch returns for the same arguments. With a live key, clients that can ask their user (MCP elicitation) also get a question to confirm, and the answer does not pass through the model. An include longer than the free allowance answers allowance_exhausted; a directory already listed answers invalid_directories.

NameTypeReqDescription
confirm_selectedintegeryesThe directory count from preview_launch that the user agreed to
directories–yes"auto" (best matches, highest DR first), {include: [ids]} exactly these, or {exclude: [ids]} auto without these
excluded_directoriesarray–Replaces the project's whole exclusion list for this request; [] clears it. directories: {exclude} leaves some out once instead
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

add_screenshot ~116

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.

NameTypeReqDescription
file_pathstring–A local image inside SUBMITATOR_FILES_DIR (or the starting folder), instead of url
project_idstringyesProject id (prj_...)
urlstring–Public image URL: PNG, JPEG, GIF or WebP, 5 MB at most

No output schema declared.

No examples provided.

create_project ~378

Creates a project for a client's product from its URL. Name, tagline and description are filled from the site in the background when left out. Costs nothing: a launch is spent only by launch_project.

NameTypeReqDescription
audienceobject–Which audience-restricted directories fit the product
category–––
competitorsarray–Up to 20, some directories need them. Replaces the whole list, so an entry left out is removed
contact_email––Email the directories write to; required before launch
excluded_directoriesarray–Directories never to use for this project. Replaces the whole list, which get_project shows; [] clears it
external_id––The agency's own id for this client
launch_date––YYYY-MM-DD
logo_urlstring–Public image URL for the logo (PNG, JPEG, GIF or WebP, 5 MB at most)
long_description––Long description
maker_name––Founder or maker name
metadataobject–Up to 20 string pairs for the agency. Replaces all of it; {} clears it
namestring–Product name; filled from the site when left out
price_amount_cents––Price in cents
price_period–––
pricing_model–––
promo_code––Discount code some directories ask for
promo_description––What the promo code gives
screenshot_urlsarray–1 to 5 public image URLs
short_description––Short description
tagline––One-line pitch
tagsarray–Up to 10. Replaces the whole list
twitter_url––https://x.com/... profile
urlstringyesThe client product's public URL

No output schema declared.

No examples provided.

create_report ~58

Builds a PDF or XLSX report of a project, branded for the agency. Building takes a moment; get_report says when it is ready.

NameTypeReqDescription
formatstringyes–
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

create_share_link ~88

Gives the project's client page link. Returns the current link when there is one; replace: true issues a new link and turns the old one off.

NameTypeReqDescription
expires_atstring–When the new link stops working
project_idstringyesProject id (prj_...)
replaceboolean–Issue a new link even if one exists; the old one stops working

No output schema declared.

No examples provided.

delete_draft ~38

Deletes a project that was never launched. A launched project cannot be deleted.

NameTypeReqDescription
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

delete_share_link ~38

Turns the project's client page link off. Anyone holding it sees nothing afterwards.

NameTypeReqDescription
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

find_directories ~157

Searches the directories Submitator submits to, highest Domain Rating first, or reads one by id. Before the agency first buys launches, only the top 20 are shown.

NameTypeReqDescription
audiencestring––
cursorstring–next_cursor from the previous page
directory_idstring–Read this one directory; other filters are ignored
kindstring–article = article platforms, open only through include
limitinteger–Rows to return, 25 by default, 50 at most
min_drinteger–Lowest Domain Rating
qstring–Part of the name
requiresstring–What the directory asks for
topicstring––

No output schema declared.

No examples provided.

get_badge ~82

The agency-branded badge some directories require on the client's site: its status, a message to forward to the client, the platforms it has install code for, and the code for the one named in platform.

NameTypeReqDescription
platformstring–Platform name from the list, for its install code
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

get_project ~53

One project in full: status, what it waits for, progress counts, allowance, readiness, texts, images and the image candidates found on its site.

NameTypeReqDescription
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

get_report ~34

Whether a report is ready, and how to get the file.

NameTypeReqDescription
report_idstringyesReport id (rep_...)

No output schema declared.

No examples provided.

get_share_link ~44

The project's client page link (a read-only progress page in the agency's brand), with its views.

NameTypeReqDescription
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

launch_project ~227

Starts submissions and spends one of the agency's paid launches; with a sbm_test_ key it spends a test launch and submits nothing. Refuses unless confirm_selected equals the directory count preview_launch returns for the same arguments. With a live key, clients that can ask their user (MCP elicitation) also get a question to confirm, and the answer does not pass through the model.

NameTypeReqDescription
auto_replaceboolean–true: within a day the free allowance fills up to 100 with fitting directories, replacing declined ones too. include turns it off unless you send true
confirm_selectedintegeryesThe directory count from preview_launch that the user agreed to
directories––"auto" (best matches, highest DR first), {include: [ids]} exactly these, or {exclude: [ids]} auto without these
excluded_directoriesarray–Replaces the project's whole exclusion list for this request; [] clears it. directories: {exclude} leaves some out once instead
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

list_events ~188

Changes to projects and listings. The feed keeps 90 days and reads oldest first, so one call scans up to 1,000 events from the cursor (or from the start) and returns the newest ones since `since` (7 days ago by default). Passed back in a later call, its next_cursor reads only what came after. For the current state of a project, get_project and list_listings are cheaper.

NameTypeReqDescription
cursorstring–next_cursor from an earlier call: continues from there
limitinteger–Rows to return, 25 by default, 100 at most
project_idstring–Only this project
sincestring–ISO time; 7 days ago by default, none when a cursor is given
typestring–A type such as listing.live, or a group: listing.*, project.*, report.*

No output schema declared.

No examples provided.

list_listings ~119

A project's listings, one per directory, highest DR first, with status and the live link once published. Or one listing in full by its id.

NameTypeReqDescription
cursorstring–next_cursor from the previous page
directorystring–Only the listing on this directory
limitinteger–Rows to return, 25 by default, 50 at most
listing_idstring–Read this one listing instead
project_idstring–Project id (prj_...)
statusstring––

No output schema declared.

No examples provided.

list_projects ~98

Lists the agency projects, newest first. q finds one by part of its name or URL, and external_id by the agency's own id.

NameTypeReqDescription
cursorstring–next_cursor from the previous page
external_idstring––
limitinteger–Rows to return, 20 by default, 50 at most
qstring–Part of the name or URL
statusstring––

No output schema declared.

No examples provided.

preview_launch ~204

Free dry run of launch_project (or of add_directories on a launched project) with the same arguments: how many directories it would submit to, what is missing, what would unlock more and what it costs, plus the top and median DR of the auto pick. Its would_submit count is the confirm_selected that launch_project or add_directories requires for the same arguments.

NameTypeReqDescription
auto_replaceboolean–true: within a day the free allowance fills up to 100 with fitting directories, replacing declined ones too. include turns it off unless you send true
directories––"auto" (best matches, highest DR first), {include: [ids]} exactly these, or {exclude: [ids]} auto without these
excluded_directoriesarray–Replaces the project's whole exclusion list for this request; [] clears it. directories: {exclude} leaves some out once instead
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

project_directories ~120

Every catalog directory as seen by one project: suggested (the auto pick), open, locked (with what unlocks it), excluded or listed. Shows suggested, open and locked by default; the counts cover all.

NameTypeReqDescription
limitinteger–Rows to return, 50 by default, 100 at most
offsetinteger–Rows to skip, for the next page
project_idstringyesProject id (prj_...)
statesarray–Which states to list; suggested, open and locked by default

No output schema declared.

No examples provided.

remove_image ~65

Removes the logo ("logo") or one screenshot (its img_ id). A launched project keeps at least its logo and one screenshot.

NameTypeReqDescription
image–yes"logo", or the img_ id of a screenshot
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

save_report_file ~63

Downloads a ready report and saves it to a local folder (Downloads by default). Never overwrites a file. Returns the path.

NameTypeReqDescription
directorystring–Folder to save into; Downloads by default
report_idstringyesReport id (rep_...)

No output schema declared.

No examples provided.

set_logo ~121

Sets or replaces a project's logo. A 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) works too.

NameTypeReqDescription
file_pathstring–A local image inside SUBMITATOR_FILES_DIR (or the starting folder), instead of url
project_idstringyesProject id (prj_...)
urlstring–Public image URL: PNG, JPEG, GIF or WebP, 5 MB at most

No output schema declared.

No examples provided.

update_project ~354

Changes the project fields it is sent and leaves the others as they are; null clears a field, and a list replaces the whole list. contact_email cannot change after launch, and after launch an edit reaches only the listings that have not been sent to their directory.

NameTypeReqDescription
audienceobject–Which audience-restricted directories fit the product
category–––
competitorsarray–Up to 20, some directories need them. Replaces the whole list, so an entry left out is removed
contact_email––Email the directories write to; required before launch
excluded_directoriesarray–Directories never to use for this project. Replaces the whole list, which get_project shows; [] clears it
external_id––The agency's own id for this client
launch_date––YYYY-MM-DD
long_description––Long description
maker_name––Founder or maker name
metadataobject–Up to 20 string pairs for the agency. Replaces all of it; {} clears it
namestring–Product name; filled from the site when left out
price_amount_cents––Price in cents
price_period–––
pricing_model–––
project_idstringyesProject id (prj_...)
promo_code––Discount code some directories ask for
promo_description––What the promo code gives
short_description––Short description
tagline––One-line pitch
tagsarray–Up to 10. Replaces the whole list
twitter_url––https://x.com/... profile
urlstring––

No output schema declared.

No examples provided.

verify_badge ~43

Checks the client's site for the badge now. Each project gets up to 10 checks an hour.

NameTypeReqDescription
project_idstringyesProject id (prj_...)

No output schema declared.

No examples provided.

whoami ~33

Shows the agency and mode (live or test) behind the key, its permissions, launches left and the hourly request budget.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Submitator MCP server?

Submitator runs locally as an npm package, launched with npx -y submitator-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · submitator-mcp

# add to Claude Code
claude mcp add com-submitator-mcp -- npx -y submitator-mcp
Common questions

What is the Submitator MCP server?

Submitator is an MCP server listed in the public MCP registry as com.submitator/mcp. Launch your clients' products on up to 100 directories each from Claude, ChatGPT, Cursor or VS Code. This page covers its npm package (submitator-mcp).

Is the Submitator MCP server safe to use?

Submitator scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Submitator MCP server expose?

Submitator exposes 24 tools: whoami, list_projects, get_project, create_project, update_project, and 19 more. Their descriptions and schemas cost roughly 2,923 tokens of context every time the server is loaded.

Is the Submitator MCP server still maintained?

Submitator is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Submitator MCP server under?

Submitator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.