_ registry / mcp streamable-http · checked 1h ago

mantlekit-launch-planner

https://mcp.mantlekit.dev

Registry code: e989daf341d1eb46

api record

Generate MantleKit setup plans and launch-ready SaaS blueprints from a product idea.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.mantlekit.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mantlekit-launch-planner live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is mantlekit-launch-planner free to use?
Yes — the hub reached it with no key and no payment.
What tools does mantlekit-launch-planner have?
4 tools: generate_project_blueprint, recommend_setup, match_theme, compare_build_vs_custom.
Is mantlekit-launch-planner safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
407ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 295 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
developer tools
used for
  • generate a saas project blueprint
  • recommend a starter kit setup
  • match a theme to a product
takes → gives
text, data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • generate_project_blueprint reads unknown 12h ago

    Turn an app idea into a launch-ready MantleKit project blueprint with pages, dashboard sections, entities, and MVP scope.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appName",
    "oneLineIdea"
  ],
  "properties": {
    "appName": {
      "type": "string",
      "minLength": 2,
      "description": "Name of the planned product."
    },
    "adminNeeds": {
      "type": "boolean",
      "description": "Whether the product needs dashboard/admin workflows."
    },
    "oneLineIdea": {
      "type": "string",
      "minLength": 8,
      "description": "Short description of the product."
    },
    "authRequired": {
      "type": "boolean",
      "description": "Whether users need accounts, login, or protected areas."
    },
    "contentNeeds": {
      "type": "boolean",
      "description": "Whether the product needs CMS, blog, docs, or SEO content."
    },
    "coreFeatures": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": [],
      "description": "Core user-facing features to include in the MVP."
    },
    "supportNeeds": {
      "type": "boolean",
      "description": "Whether the product needs tickets, chat, or support workflows."
    },
    "commercialUse": {
      "type": "boolean",
      "description": "Whether this is for client delivery or commercial agency use."
    },
    "ecommerceNeeds": {
      "type": "boolean",
      "description": "Whether the product needs products, orders, carts, or fulfilment."
    },
    "targetAudience": {
      "type": "string",
      "description": "Primary audience or buyer segment for the product."
    },
    "themePreference": {
      "type": "string",
      "description": "Desired MantleKit theme style or brand direction."
    },
    "paymentsRequired": {
      "type": "boolean",
      "description": "Whether the app needs checkout, subscriptions, or paid plans."
    }
  }
}
    arguments 64 lines
  • recommend_setup reads unknown never probed

    Recommend the best MantleKit tier, theme, and built-in feature set for a new app idea.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appIdea"
  ],
  "properties": {
    "appIdea": {
      "type": "string",
      "minLength": 8,
      "description": "Plain-English description of the app idea."
    },
    "needsCms": {
      "type": "boolean",
      "description": "Whether structured content management is needed."
    },
    "needsAuth": {
      "type": "boolean",
      "description": "Whether authentication is needed."
    },
    "needsAdmin": {
      "type": "boolean",
      "description": "Whether a serious admin/dashboard surface is needed."
    },
    "businessType": {
      "type": "string",
      "description": "Business model or category, for example B2B SaaS or agency."
    },
    "commercialUse": {
      "type": "boolean",
      "description": "Whether client delivery or commercial usage matters."
    },
    "needsPayments": {
      "type": "boolean",
      "description": "Whether hosted payments or checkout are needed."
    },
    "needsEcommerce": {
      "type": "boolean",
      "description": "Whether products, orders, and customers are needed."
    },
    "targetAudience": {
      "type": "string",
      "description": "Primary audience for the product."
    },
    "needsSupportTickets": {
      "type": "boolean",
      "description": "Whether support ticketing is needed."
    },
    "preferredThemeStyle": {
      "type": "string",
      "description": "Desired visual direction or brand adjectives."
    }
  }
}
    arguments 54 lines
  • match_theme reads unknown 12h ago

    Recommend the best MantleKit theme for a product type, audience, and brand direction.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appType"
  ],
  "properties": {
    "appType": {
      "type": "string",
      "minLength": 2,
      "description": "Type of product being built."
    },
    "audience": {
      "type": "string",
      "description": "Intended audience or buyer segment."
    },
    "brandAdjectives": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": [],
      "description": "Brand adjectives or vibe words."
    },
    "stylePreference": {
      "type": "string",
      "description": "Optional style direction or visual preference."
    }
  }
}
    arguments 30 lines
  • compare_build_vs_custom reads unknown 12h ago

    Estimate where MantleKit saves time versus building from scratch for a SaaS project.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appIdea"
  ],
  "properties": {
    "appIdea": {
      "type": "string",
      "minLength": 8,
      "description": "Plain-English description of the app idea."
    },
    "needsCms": {
      "type": "boolean",
      "description": "Whether structured content management is needed."
    },
    "teamSize": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "Approximate team size working on the product.",
      "exclusiveMinimum": 0
    },
    "needsAuth": {
      "type": "boolean",
      "description": "Whether authentication is needed."
    },
    "needsAdmin": {
      "type": "boolean",
      "description": "Whether a serious admin/dashboard surface is needed."
    },
    "commercialUse": {
      "type": "boolean",
      "description": "Whether client delivery or commercial usage matters."
    },
    "needsPayments": {
      "type": "boolean",
      "description": "Whether hosted payments or checkout are needed."
    },
    "timelineWeeks": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "Target launch timeline in weeks.",
      "exclusiveMinimum": 0
    },
    "needsEcommerce": {
      "type": "boolean",
      "description": "Whether products, orders, and customers are needed."
    },
    "experienceLevel": {
      "enum": [
        "solo_indie",
        "small_team",
        "experienced_team"
      ],
      "type": "string",
      "description": "Builder profile used to estimate fit and time saved."
    },
    "estimatedFeatures": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": [],
      "description": "Major product features expected in the first release."
    },
    "needsSupportTickets": {
      "type": "boolean",
      "description": "Whether support ticketing is needed."
    }
  }
}
    arguments 71 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e989daf341d1eb46.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e989daf341d1eb46/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e989daf341d1eb46/badge.svg)](https://brick.blue/agent/e989daf341d1eb46?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.