Responded16 / 22 checks passed
Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.
- Handshake
- Tools listed
- Updated recently
Median latency 699 ms · Last checked
com.submitmap/directory
com.submitmap/directory
A directory of product launch platforms: where your product qualifies and how each form is filled.
OtherIs com.submitmap/directory down?Alternatives
11 of 22 checks passed
- Handshake
- Tools listed
- Updated recently
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Median latency
362 ms
Uptime, 30 days
Not measured
Last checked
Measurement details
Core
- Pass
- Pass
- Pass
- Pass
- Pass
Performance
- Not measured
- Not measured
- Not measured
- Not measured
Access
- Pass
- Not measured
- Not measured
Tools
- Pass
- Pass
- Fail
- Fail
Publisher
- Pass
- Fail
- Pass
- Not measured
- Pass
- Not measured
Tools
- 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, leave the rest, and come back with update_project. Facts drive what it qualifies for; the pack is what you will paste into forms later. Ask about images early: most platforms want a square logo and many want a cover, and every asset in the pack is two fields, the public address (logoUrl) and the file on the maker's machine (logoFile), because a form uploads the file and only the address can be shown back to them.
Measured
- 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 contradicts its label, a second email input belonging to a newsletter, a honeypot). The brief spends one of the account's tracked platforms, so ask for it once the maker has decided to fill this form, not while you are still choosing between platforms. For a stored project, submission_playbook returns the same brief with the maker's values already in it.
Measured
- 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.
Measured
- 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.
Measured
- 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 as a checklist that ticks itself off as submissions land. Anything already tracked is reordered rather than reset. Call it after qualify_project, using the `recommended` list it hands back, and if that response carried `questions`, put them to the maker before you plan: the order depends on the answers, and a plan written on an assumption is one they have to undo by hand. A plan costs nothing on any plan, so plan the whole run the product deserves rather than a short one sized to a guess about what the account can track.
Measured
- 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` and `budget`, and when they have not been answered the response says what it assumed and carries the questions to put to the maker: ask them, call again with the answers, and store them with update_project so nobody asks twice. Needs no account: describe the product inline. Every field is optional and an unanswered field becomes a gap to fill rather than a rejection.
Measured
- 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, a login, a payment, a file, an address to confirm) is recorded as `planned` with a note saying what you need from them: that hands it back without claiming an outcome, and frees the run to carry on. If the live platform did not match what the brief said, put the difference in `differsFromRecord`. This costs nothing on any plan and no status costs more than another, so record what actually happened: the brief was what spent the tracked platform, and leaving the row wrong now only makes the run harder to follow.
Measured
- 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 from what you remember of the web. Returns summaries; call get_platform for the full record including the submission steps.
Measured
- 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 gotchas, the agentGotchas (traps in the form itself), and the call to make afterwards. Read the preflight before opening a tab. One brief is out at a time per project: ask for the next platform only after record_submission has answered this one, because until then this tool refuses the next brief and names the one still open. Do not fetch briefs ahead or in parallel. This is the tool the free plan meters: it covers the same submissions the dashboard tracks, plus any platform the account has already sent to, and past that it says so and points at the upgrade rather than answering.
Measured
- 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.
Measured
- 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 a limit says so at the write it stops.
Measured
Probe history
- ok362 ms11 tools
Add badge to your README
The image links back to this page. It shows checks passed, or uptime, and the colour follows the latest status. Responses are cached for 5 to 15 minutes.
Markdown
[](https://mcpheartbeat.com/s/com.submitmap/directory)HTML
<a href="https://mcpheartbeat.com/s/com.submitmap/directory"><img alt="MCP Heartbeat" src="https://mcpheartbeat.com/badge/com.submitmap/directory.svg"></a>Uptime markdown
[](https://mcpheartbeat.com/s/com.submitmap/directory)Served from https://mcpheartbeat.com.
Related servers
All alternativesSame function and industry, ranked by checks passed then median latency.
- Responded15 / 22 checks passed
Find the nearest public toilet worldwide. Read-only tools, no account, no API key.
- Handshake
- Tools listed
- Updated recently
Median latency 49 ms · Last checked
- Responded15 / 22 checks passed
Perícia e ciência forense pelo mundo, em português: busca, artigos completos e glossário técnico.
- Handshake
- Tools listed
- Updated recently
Median latency 56 ms · Last checked
- Responded15 / 22 checks passedPick My Costume
pickmycostume.comVerified
Recommends Halloween costumes you can actually build, with step-by-step DIY build guides.
- Handshake
- Tools listed
- Updated recently
Median latency 57 ms · Last checked
- Responded15 / 22 checks passed
Write a step-by-step routine and get a link that opens it in Routine Run on iPhone. No sign-in.
- Handshake
- Tools listed
- Updated recently
Median latency 62 ms · Last checked
- Responded15 / 22 checks passed
Runs a Secret Santa name draw in chat and gives each person a private reveal link.
- Handshake
- Tools listed
- Updated recently
Median latency 62 ms · Last checked
Connect to this server
Claude Code
claude mcp add --transport http com-submitmap-directory https://submitmap.com/api/mcpCursor .cursor/mcp.json
{
"mcpServers": {
"com-submitmap-directory": {
"url": "https://submitmap.com/api/mcp"
}
}
}VS Code .vscode/mcp.json
{
"servers": {
"com-submitmap-directory": {
"type": "http",
"url": "https://submitmap.com/api/mcp"
}
}
}