Skip to main content
Glama

Server Details

Plan startup directory submissions and verify the links went live, with your own AI agent.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
LaunchDistro/launchdistro-mcp
GitHub Stars
1
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 13 tools

Disambiguation4/5

Most tools target a distinct resource plus action: profile read/write, directory matching, planning, recording, verifying. The one genuinely close pair is verify_badge vs verify_link, since both check dofollow link-backs, but the descriptions clearly separate the product's own page from a public listing page. record_submission vs verify_link also touch submission state, though the descriptions explicitly divide manual recording from live verification.

Naming Consistency4/5

The set is overwhelmingly verb_noun: get_product_profile, save_product_profile, list_products, match_directories, plan_submissions, record_submission, verify_badge, verify_link, and so on. Two outliers (license_status, submission_playbook) are noun phrases, and one is a bare verb-noun pair without object clarity (suggest_directory), but the pattern stays predictable.

Tool Count5/5

13 tools fit comfortably in the well-scoped band, and each maps to a step in the submission lifecycle: read/write the profile, match directories, plan, fetch the playbook, record, verify, and feed facts back. No tool looks redundant or like filler.

Completeness4/5

The surface covers the lifecycle well: product profiles (get/save/list), directory discovery (match, suggest, playbook, report fact), planning, submission recording with multiple states, and both verification paths, plus license/status. Minor gaps: there is no way to inspect a single submission or plan entry in detail beyond list_submissions, and no explicit tool to clear or amend an existing plan other than re-planning or marking skipped.

Publisher details

Operator
LaunchDistro · Publisher source
Vendor relationship
Unknown
Privacy policy
Not provided
Restrictions
https://launchdistro.com/terms · Publisher source

Available Tools

13 tools
get_product_profileProduct profileC
Read-only
Inspect

The product's facts in product.json form: every submission is filled from these, and nothing else. Also lists the fields directories ask for that are still empty.

Inputs: product.

license_statusPlan and usageB
Read-only
Inspect

The user's plan, free submissions used, Launch passes and connected devices.

Inputs: no named parameters.

list_productsList productsB
Read-only
Inspect

The user's products: name, website, whether a profile exists and how many submissions it has.

Inputs: no named parameters.

list_submissionsWhat has gone outB
Read-only
Inspect

Every directory on this product's plan and what happened there, with the next one to submit.

Inputs: product.

match_directoriesWhere the product qualifiesB
Read-only
Inspect

Every catalogued directory for this product: ready, locked (a Launch or Pro opens it), no tested playbook yet, or not a fit, each with the reason (product type, region, badge answer).

Inputs: product.

plan_submissionsPlan the runA
Destructive
Inspect

Orders the directories that are ready for this product and saves the plan to the dashboard: long review queues first, then verified dofollow, then badge listings (at most a quarter of the plan), then authority, at a pace for the domain's DR, each with why it is where it is. Submits nothing. Replaces the previous plan's unsent directories.

Inputs: days, pace, count, product, +2 more.

record_submissionRecord a submissionA
Idempotent
Inspect

Records what happened at a directory, on the dashboard. submitted: sent (with the confirmation URL, and the listing URL once the directory shows one). draft: saved there but not sent yet (say what is left in note). needs_human: waiting on the user. rejected, skipped (take it off the plan). Never records live: verify_link does that after reading the public page.

Inputs: status (required), directory (required), note, route, +3 more.

report_directory_factReport what a directory saidAInspect

When a directory shows something its playbook did not say, report it in the page's own words: how long approval takes, whether the free link is dofollow, whether a free route still exists, a badge or link-back rule, a price, a changed form. One fact per report: when a directory has become paid only, send free_route no as well as the price. It goes straight to LaunchDistro for review (the user does not need to email anyone) and improves the catalog for everyone. Stored with the user's account in case we need to ask; only the directory fact is used.

Inputs: kind (required), value (required), directory (required), quote, +1 more.

save_product_profileSave product profileA
Idempotent
Inspect

Saves product facts (product.json keys) to the dashboard. Merged onto the stored profile for the same website, so send only what changed. Only facts the user confirmed: never invent pricing, metrics or features.

Inputs: profile (required).

submission_playbookPlaybook for one directoryA
Idempotent
Inspect

How to submit to one directory: what its form asks, which profile field goes where, the fields the profile lacks, the free plan's conditions, and where to stop. Call it before every submission. Counts as one submission attempt (a same-day re-read is free). Refused, and not counted, for a directory that is not a fit for the product.

Inputs: directory (required), product.

suggest_directorySuggest a directoryA
Idempotent
Inspect

When the user recommends a directory LaunchDistro does not give for this product, send it for review. A suggestion only: do not open its form or submit there. It gets a playbook, and reaches plans, only after LaunchDistro checks it.

Inputs: url (required), name, note, product.

verify_badgeCheck a badge on the product's siteA
Idempotent
Inspect

Opens the product's own page and checks that it links to the directory (the badge or link back its free plan asks for), and whether that link is dofollow. Call it after the user deploys, before pressing the directory's verify button.

Inputs: directory (required), product, page_url.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to audit a website for launch readiness, find suitable startup/SaaS/AI directories using filters like DR and link type, and submit product listings to SaaSCity as drafts.
      428 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching a hand-curated directory of product launch platforms and startup directories, checking which ones a project qualifies for, and planning, executing, and tracking submissions through an agent's browser with optional authenticated account access.
      208
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables submitting products for launch, browsing the product directory and weekly winners, and finding 333 curated startup launch directories from an AI agent.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to discover Substack newsletter and sponsor leads, mine Shopify competitor churn reviews, extract emails from Linktree/bio hubs and company websites, and find Show HN/Product Hunt startup launches.
      5
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.