Noonlaunch

Launch a product on Noonlaunch, search its directory and weekly winners, and find 333 launch sites.

使うべきか

品質と安全性

A
説明の品質
94%
スキーマの完全性
84%
命名の品質
68%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

検出事項(10)

  • LOWTool 'search-directory' doesn't follow camelCase/snake_casesearch-directory 内
  • LOWTool 'get-product' doesn't follow camelCase/snake_caseget-product 内
  • LOWTool 'get-weekly-winners' doesn't follow camelCase/snake_caseget-weekly-winners 内
  • LOWTool 'list-launch-directories' doesn't follow camelCase/snake_caselist-launch-directories 内
  • LOWTool 'get-plans' doesn't follow camelCase/snake_caseget-plans 内
  • LOWTool 'check-product' doesn't follow camelCase/snake_casecheck-product 内
  • LOWTool 'submit-product' doesn't follow camelCase/snake_casesubmit-product 内
  • LOWTool 'verify-badge' doesn't follow camelCase/snake_caseverify-badge 内
  • LOWTool 'check-status' doesn't follow camelCase/snake_casecheck-status 内
  • LOWTool 'report-badge-problem' doesn't follow camelCase/snake_casereport-badge-problem 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,447トークン数(ツール定義)
~851 B一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 1.13%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "mcp": {
      "url": "https://noonlaunch.com/mcp"
    }
  }
}

リモートエンドポイント

https://noonlaunch.com/mcpstreamable-http

できること

ツール一覧

ツール(10)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢search-directory(query, category, limit)

Search the Noonlaunch product directory. Returns approved products matching the query, ordered by community votes, with links to their Noonlaunch product pages.

入力スキーマ

{
  "type": "object",
  "properties": {
    "query": {
      "description": "Search term matched against product names, taglines and descriptions.",
      "type": "string"
    },
    "category": {
      "description": "Optional category slug or name to narrow results.",
      "type": "string"
    },
    "limit": {
      "description": "Max results to return (1-25, default 10).",
      "type": "integer"
    }
  }
}
🟢get-product(slug)

Get full public details of one Noonlaunch product by its slug (the last part of its noonlaunch.com/product/... URL).

入力スキーマ

{
  "type": "object",
  "properties": {
    "slug": {
      "description": "The product slug, e.g. \"my-product\" for noonlaunch.com/product/my-product.",
      "type": "string"
    }
  }
}
🟢get-weekly-winners(weeks_ago)

Get the Noonlaunch launch board for a week: the top-voted free launches, with the top 3 marked as winners. weeks_ago 0 is the current (still running) week, 1 is the last completed week.

入力スキーマ

{
  "type": "object",
  "properties": {
    "weeks_ago": {
      "description": "How many weeks back (0 = current running week, 1 = last completed week, default 1, max 52).",
      "type": "integer"
    }
  }
}
🟢list-launch-directories(category, free_only, min_da, limit)

Browse Noonlaunch's curated list of 333 startup launch directories and communities where founders can submit a product. Filterable by category, cost and minimum domain authority.

入力スキーマ

{
  "type": "object",
  "properties": {
    "category": {
      "description": "Filter by directory category, e.g. \"AI\", \"SaaS\", \"General\".",
      "type": "string"
    },
    "free_only": {
      "description": "Only directories that are free to submit to.",
      "type": "boolean"
    },
    "min_da": {
      "description": "Minimum domain authority (0-100).",
      "type": "integer"
    },
    "limit": {
      "description": "Max results (1-100, default 50).",
      "type": "integer"
    }
  }
}
🟢get-plans

What it costs to launch on Noonlaunch, and what each plan includes. Use this to answer a pricing question on its own. To actually submit a product, call check_product instead: which plans apply depends on the site, because relaunching one that is already listed needs a paid plan.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
🟢check-product(website_url)

Check whether a product can be submitted to Noonlaunch, and get the plans, categories and launch weeks available for it. Always call this first, and always ask the person for their live public website URL rather than guessing it from their code.

入力スキーマ

{
  "type": "object",
  "properties": {
    "website_url": {
      "description": "The live public URL of the product, as given by the person. Never a localhost or development address.",
      "type": "string"
    }
  }
}
🟡submit-product(website_url, name, tagline, description, category, ...)

Submit a product to Noonlaunch. Nothing is published by this call. It returns a claim link to give the person straight away, and for free launches the badge snippet to install. Call check_product first.

入力スキーマ

{
  "type": "object",
  "properties": {
    "website_url": {
      "description": "The live public URL the person confirmed. Never guess this from the codebase.",
      "type": "string"
    },
    "name": {
      "description": "Product name, 2-100 characters.",
      "type": "string"
    },
    "tagline": {
      "description": "One line shown on the board, 10-70 characters.",
      "type": "string"
    },
    "description": {
      "description": "What the product does, 30-600 characters. Longer text is rejected, not trimmed.",
      "type": "string"
    },
    "category": {
      "description": "Category id or slug from check_product.",
      "type": "string"
    },
    "plan": {
      "description": "One of: free, bundle_featured, bundle_spotlight. Ask the person which they want.",
      "type": "string"
    },
    "launch_week": {
      "description": "Optional launch week as a Monday date (YYYY-MM-DD) from check_product. Defaults to the next open week.",
      "type": "string"
    },
    "logo_url": {
      "description": "Optional public URL of the product logo image, which we download.",
      "type": "string"
    },
    "twitter_handle": {
      "description": "Optional X handle, with or without the @.",
      "type": "string"
    }
  }
}
🟡verify-badge(submission_token)

Check that the Noonlaunch badge is installed on the product site and publish the listing if it is. Only for free launches, and only after the person has deployed the change. Paid listings are published by payment instead, so use check_status for those.

入力スキーマ

{
  "type": "object",
  "properties": {
    "submission_token": {
      "description": "The submission_token returned by submit_product.",
      "type": "string"
    }
  }
}
🟢check-status(submission_token)

Where a submission stands: whether it has been claimed, paid for, verified and published. This is the only way to find out whether a payment has landed. Poll it rather than assuming.

入力スキーマ

{
  "type": "object",
  "properties": {
    "submission_token": {
      "description": "The submission_token returned by submit_product.",
      "type": "string"
    }
  }
}
🟢report-badge-problem(submission_token, message)

Report that the badge check is wrong: the badge is installed and visible but we cannot find it. Only use this after verify_badge has failed twice and you have confirmed the badge really is live on the page. A person reviews it within 24 hours.

入力スキーマ

{
  "type": "object",
  "properties": {
    "submission_token": {
      "description": "The submission_token returned by submit_product.",
      "type": "string"
    },
    "message": {
      "description": "Where the badge is on the page and what you have already checked, so a human can resolve it without asking. 20-1500 characters.",
      "type": "string"
    }
  }
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 10 件