← submitmap.com

INDIVIDUAL MCP TOOL

whoami

Which SubmitMap account this token belongs to, named by its email address, which plan it is on, and what it already holds.

submitmap.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://submitmap.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for whoami and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name, description or schema mentions credentials.
  • A tool name or description suggests sending messages.

Parent server

submitmap.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.submitmap]
url = "https://submitmap.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "submitmap": {
      "type": "http",
      "url": "https://submitmap.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

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

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "submitmap": {
      "url": "https://submitmap.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "submitmap": {
      "type": "http",
      "url": "https://submitmap.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "submitmap",
  "transport": "streamable-http",
  "url": "https://submitmap.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • search_platforms — Search the SubmitMap directory of startup launch platforms and directories.
  • get_platform — Full record for one platform: eligibility, disqualifiers, step-by-step submission instructions, requirements, gotchas and expected outcome.
  • 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.
  • 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.
  • create_project — Store a product on the account.
  • update_project — Fill in or correct a stored project.
  • 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.
  • record_submission — Log what happened to the dashboard: the listing URL, when it was sent, when it goes live.