A directory of product launch platforms: where your product qualifies and how each form is filled.
| Endpoint | https://submitmap.com/api/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 11 tools · grade C (65) · pin ts_147d58dc9061ab301880606c1d425f4c · protocol 2025-06-18 |
| First / last listed | 2026-11-12 00:19 UTC / 2026-11-12 00:19 UTC |
| Grade over time | 2026-11-12: C (65), 11 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: search_platforms get_platform qualify_project whoami list_projects create_project update_project submission_playbook record_submission plan_submissions list_submissions
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 small directory I can submit to right now": it is the whole directory, so answer from it rather than f params: query, category, pricing, dofollow, requiresBacklink, maxApprovalDays, minDomainRating, maxDomainRating, sort, limit, excludeTracked, projectId |
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 platform's form, and agentGotchas, the traps that only bite something filling it (a placeholder that params: slug*, projectId, brief |
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 out of the directory rather than out of what you remember of the web. That order is decided by `goal params: goal, budget, launchAt, name, url, stage, pricingModel, categories, domainRating, monthlyTraffic, livePublicUrl, openSignup, pricingPage, logoSquare, coverImage, demoVideo, publicRepo, privacyPolicy, docs, payingCustomers, acceptsBacklink |
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 another. It does not hand you the plan's limits and you do not need them to work: plan the whole run, and params: none |
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 other account tool takes the id it returns. params: none |
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 project back, with questions only about what is genuinely not there. Fill in as much as you can, le params: name*, url, pitch, facts, pack |
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. params: projectId, name, url, pitch, facts, pack |
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 pass back as signInAs), the pack values mapped onto the fields the form asks for, the steps, the go params: projectId, platformSlug*, signInAs |
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 brief on this project is refused until this call is made. A platform that needs the maker (a captcha, params: projectId, platformSlug*, status*, listingUrl, submittedAt, launchAt, note, differsFromRecord |
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, with a short reason on each, plus a summary of the strategy. The plan appears on the maker's dashboard params: projectId, summary, checklist, items* |
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 remember. Start with list_projects if they have not named a project. params: projectId |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.