Submitator MCP server

• Registry namecom.submitator/mcpverified in the MCP registry

The registry name sits under submitator.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-30
• Tools23
• Server calls itselfsubmitator
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 147 ms.

• Its tools do submit a startup to many directories without manual form filling, but not check domain rating changes against competitors each day.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• What an agent can do with it1 of 2 use cases
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer134 ms
• Space in an agent's context≈ 6,069 tokensthe definitions of all its tools (23), which an agent carries on every turn
• Tool definitionsA · 96 of 100
• Typed results0 of 23 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 6 of 23

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• whoami

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

• list_projects

  Lists the agency projects, newest first. Find one by name or URL with q, or by your own external_id.

• get_project

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

• create_project

  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.

• update_project

  Changes project fields. Send only what changes; 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 not yet sent to their directory.

• delete_draft

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

• set_logo

  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.

• add_screenshot

  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, so do not repeat a call that succeeded.

• remove_image

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

• preview_launch

  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, top and median DR, what is missing, what would unlock more, and what it costs. Show the numbers…

• find_directories

  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.

• project_directories

  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.

• launch_project

  Starts submissions and spends one launch of the agency (a test launch with a sbm_test_ key). Call preview_launch with the same arguments first and get the user to agree; confirm_selected is the count they agreed to. With a live key…

• add_directories

  Submits a launched project to more directories from its free allowance (no launch is spent). Call preview_launch with the same arguments first and get the user to agree. An include longer than the free allowance answers…

• list_listings

  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.

• list_events

  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). Keep next_cursor…

• get_badge

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

• verify_badge

  Checks the client's site for the badge now. Up to 10 checks an hour per project, so check once after the client says it is installed.

• create_report

  Builds a PDF or XLSX report of a project, branded for the agency. Building takes a moment: then call get_report.

• get_report

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

• get_share_link

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

• create_share_link

  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.

• delete_share_link

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