Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Directory is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
11
tools declared
remote
at its publisher
—
calls last 7d
What it does
A directory of product launch platforms: where your product qualifies and how each form is filled.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http submitmap-directory-mcp https://submitmap.com/api/mcp
# 2 — ask your agent for something these tools do
# search_platforms, get_platform, qualify_project and 8 more
Directory costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SUAll 1 server
submitmap1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http submitmap-directory-mcp https://submitmap.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free text matched against name, tagline, domain, slug and categories. A bare domain works: "startupfa.me" finds Startup Fame. |
| category | string | no | e.g. "AI tools", "Dev tools", "Web apps". |
| pricing | string | no | — |
| dofollow | boolean | no | Only platforms giving a dofollow backlink. |
| requiresBacklink | boolean | no | Filter on whether they demand a badge/link back. |
| maxApprovalDays | number | no | Only platforms approving within this many days. Leaves out every platform that publishes no approval time, the same way a rating bound leaves out the unrated. |
| minDomainRating | number | no | Only platforms with at least this domain rating. |
| maxDomainRating | number | no | Only platforms up to this domain rating. The small, quick, unglamorous end of the directory, which is where a first submission usually belongs. |
| sort | string | no | Fastest approval first (the default), or strongest domain first. Either way, a platform that publishes no approval time comes last rather than reading as instant. |
| limit | number | no | Return at most this many. The count is unaffected. |
| excludeTracked | boolean | no | Leave out every platform this project has already been submitted to or planned for. Needs a token, and is what makes "one I have not done yet" answerable. |
| projectId | string | no | Omit it when the account has one project, which is the free tier. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Platform slug, e.g. "product-hunt". |
| projectId | string | no | Which project the brief is for, when brief is true. Omit it when the account has one project. A brief is one form being worked on for one product, and the project it belongs to cannot be issued anothe |
| brief | boolean | no | Include agentPrompt and agentGotchas. This is the paid half and it spends a tracked platform, once, for good. Leave it out while you are deciding where to submit: eligibility, disqualifiers, gotchas, |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal | string | no | What this run is for, which decides the order of it. already-live means the product is out and wants listings, links and traffic now, so the run leads on fast approvals, dofollow links and strong do |
| budget | string | no | Whether platforms that charge to list may appear in the run. Absent means free-only, which is the assumption that cannot cost anybody anything. freemium platforms are in the run either way: their |
| launchAt | string | no | ISO 8601 date the maker is launching on, when they have named one. |
| name | string | no | — |
| url | string | no | — |
| stage | string | no | — |
| pricingModel | string | no | — |
| categories | array | no | Every audience and form factor this product belongs to, not just the main one. A product is often several at once, and one missing tag is one directory it never hears about: a repository holding a bro |
| domainRating | number | no | — |
| monthlyTraffic | number | no | — |
| livePublicUrl | boolean | no | — |
| openSignup | boolean | no | — |
| pricingPage | boolean | no | — |
| logoSquare | boolean | no | — |
| coverImage | boolean | no | — |
| demoVideo | boolean | no | — |
| publicRepo | boolean | no | — |
| privacyPolicy | boolean | no | — |
| docs | boolean | no | — |
| payingCustomers | boolean | no | — |
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
No parameter schema on file.
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.
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| url | string | no | — |
| pitch | string | no | One paragraph in the maker's own words. |
| facts | object | no | Same shape qualify_project takes: stage, pricingModel, categories, and the booleans. It is also where the two answers that decide a run order live once the maker has given them (goal, budget, and |
| pack | object | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Omit it when the account has one project, which is the free tier. |
| name | string | no | — |
| url | string | no | — |
| pitch | string | no | — |
| facts | object | no | — |
| pack | object | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Omit it when the account has one project, which is the free tier. |
| platformSlug | string | yes | — |
| signInAs | string | no | The Google address the maker wrote out when they agreed you could sign in, or sign up, for them on this project, whether they said it when asked or before you started. Pass it on every call after they |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Omit it when the account has one project, which is the free tier. |
| platformSlug | string | yes | — |
| status | string | yes | Use attempted when the form was sent and you cannot prove it arrived: the tab died, the connection dropped, the page never came back. It is not a lesser submitted, it is the honest one, and it car |
| listingUrl | string | no | The product's URL on that platform. |
| submittedAt | string | no | ISO 8601. |
| launchAt | string | no | ISO 8601, if it is scheduled. |
| note | string | no | Required with planned: what you need from the maker, in one line they can act on. |
| differsFromRecord | string | no | Only when the live platform did not match the brief or the platform record: say what differed, in one line, as fact. A price where the record said free, a sign-in or phone check it did not mention, a |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Omit it when the account has one project, which is the free tier. |
| summary | string | no | Why this order, in a sentence or two. The maker reads this. |
| checklist | array | no | What the maker has to prepare before any of this can be submitted: the gallery, the demo video, a privacy policy page, a launch date. Write it from what the platforms in this plan actually demand and |
| items | array | yes | In the order they should be submitted. First is next. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Omit it when the account has one project, which is the free tier. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Directory or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest59306664137424f2f94b8c319ddf6886c8880fd931f6f69fbdbfbc2845ea5674
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_platforms | no tags | |
| get_platform | no tags | |
| qualify_project | no tags | |
| whoami | no tags | |
| list_projects | no tags | |
| create_project | no tags | |
| update_project | no tags | |
| submission_playbook | no tags | |
| record_submission | no tags | |
| plan_submissions | no tags | |
| list_submissions | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest59306664137424f2
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Directory can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.