Connect-MCP

com.submitmap/directory

com.submitmap/directory · v1.0.0

A directory of product launch platforms: where your product qualifies and how each form is filled.

MCPremoteno credentialsE-commerceMaps & location

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 11 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 70/100

What it does: 11 tools · 5 read, 2 write · E-commerce, Maps & location, Email

Test call list_projects: failed — tool error: { "error": "Automating submissions needs a SubmitMap account, and this request has no token. Tell the maker to (1) sig (951 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +5
  • Read/write annotations: 0
  • Safe test call: 0
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://submitmap.com/api/mcp

Tools

11 tools listed at last check
  • search_platforms Search the SubmitMap directory of startup launch platforms and directories. Filter by free-text query, category, pricing, link type, backlink requirement, approval speed or domain rating, and with a token leave out the ones this project has already been sent to. This is the tool behind "find me a sm
  • get_platform Full record for one platform: eligibility, disqualifiers, step-by-step submission instructions, requirements, gotchas and expected outcome. All of that is free, and it is what decides whether this product should be submitted here at all. Pass brief: true to also get agentPrompt, the brief for that p
  • qualify_project Given a product, work out which platforms it qualifies for right now, which it could qualify for after supplying something (with the exact list of what is missing), and which are structurally out of reach. It also hands back `recommended`: the run in the order it should be worked, so the plan comes
  • whoami Which SubmitMap account this token belongs to, named by its email address, which plan it is on, and what it already holds. Call it first if you are unsure whether the maker is connected, and tell them the address it reports: it is the only way either of you can tell one of their accounts from anothe
  • list_projects The projects on this account, each with its facts (eligibility answers) and its pack (what a submission form asks for), plus what is still missing from the pack. Call it whenever the maker says "my product" or "my project" without naming one: it is how you find out which project they mean, and every
  • create_project Store a product on the account. Before asking the maker anything, use what you can already see: a README, package metadata, the site's own copy and title, an assets or public folder. A maker working in their product's repository should be able to say 'add my product to SubmitMap' and get a filled-in
  • update_project Fill in or correct a stored project. Facts and pack are merged into what is there, so you can add one field at a time as the maker answers.
  • submission_playbook Everything needed to submit a stored project to one platform, yourself, in the maker's browser: a preflight of what is still missing, the sign-in plan (on the first submission it carries a question for the maker: hand every login back to them, or use the Google address they write out, which you then
  • record_submission Log what happened to the dashboard: the listing URL, when it was sent, when it goes live. Call it as soon as a submission lands, before you ask for the next brief, including when it is only queued for review, and including when you are not sure it landed: that is what `attempted` is for. The next br
  • plan_submissions Write the run order for a project: which platforms, in what sequence, and why each one is where it is. Anything already submitted to is dropped from the plan and named back to you in `alreadySubmitted`, because a plan is what is still ahead. Pass the platforms in the order they should be worked, wit
  • list_submissions Where every submission for a project stands: what went out, when, what came back, and what is still waiting. This is the tool behind "check my submissions", "what did I submit", "did I ever submit to that one" and "how is my launch going", so answer those from here instead of asking the maker to rem

Badge

Connect-MCP badge for com.submitmap/directory

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/com.submitmap/directory.svg)](https://clawy.uk/mcp/s/com.submitmap/directory)