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

gysm

https://www.gysm.io

Registry code: 20543bfffa200a11

api record

get_gysm_plans lists GYSM's plans; with the user's own GYSM API key, subscribe_to_gysm returns a Stripe link the user pays on (never pay for them) and my_gysm_account shows their usage. GYSM turns a plain-English description into a working single-page web app with a live preview. Use plan_app or plan_online_store first to shape the idea (free, instant, no sign-in). Use get_build_link to hand the user a link, or build_app only when the user asks to build now and has connected their own GYSM API key. GYSM builds one self-contained page per build with no managed database or sign-in: be upfront…

endpoint
https://www.gysm.io/api/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 gysm live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is gysm free to use?
Yes — the hub reached it with no key and no payment.
What tools does gysm have?
9 tools: get_store, start_checkout, plan_app, plan_online_store, list_use_cases, get_build_link, compare_ai_app_builders, find_stores, ….
Is gysm 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
352ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

_ what it can do 9 tools
3 open 6 never probed 3 of 9 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.

  • compare_ai_app_builders open 1h ago

    Sourced comparison of GYSM against Lovable, Bolt, v0, Base44 and Replit: pricing and allowances as listed on each product's own pricing page on the stated check date, plus what GYSM does and does not do. Facts may have changed since the check date, so confirm on the source pages. Read-only.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "rival": {
          "type": "string",
          "description": "Optional: only this rival (lovable, bolt, v0, base44 or replit)."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • find_stores open 1h ago

    Search the online shops and businesses built on GYSM (products, appointments, services). Returns each live store's name, description and address. Read-only.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 80,
          "description": "What the shopper wants, e.g. 'candles', 'haircut in Rome' (max 80 characters). Empty lists recent stores."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • get_gysm_plans open 1h ago

    List the plans GYSM sells today with price, billing interval and what's included. Read-only; buying happens with subscribe_to_gysm, which returns a Stripe link the person pays on.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_store unknown never probed

    Read one GYSM store's catalogue: products with prices and stock, bookable services, shipping options and whether it is taking orders. Read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "store"
      ],
      "properties": {
        "store": {
          "type": "string",
          "maxLength": 40,
          "description": "The store's slug from find_stores."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • start_checkout unknown never probed

    Create a secure Stripe checkout link for products from one GYSM store. Only call it after the shopper has confirmed the items and quantities. The shopper opens the link and pays on Stripe's page; nothing is charged by this tool. Prices come from the store, not from the request.

    mcp-tool

    {
      "type": "object",
      "required": [
        "store",
        "items"
      ],
      "properties": {
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "productId",
              "quantity"
            ],
            "properties": {
              "quantity": {
                "type": "integer",
                "maximum": 99,
                "minimum": 1
              },
              "productId": {
                "type": "string"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 50,
          "minItems": 1
        },
        "store": {
          "type": "string",
          "maxLength": 40,
          "description": "The store's slug."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • plan_app unknown never probed

    Turn a plain-English app idea into a build plan: matched use case, page sections, features, a suggested data model, integrations, honest limits, a refined build prompt and a link that opens the GYSM builder with that prompt. Free and instant: it makes no AI call, creates nothing and changes nothing. It is a plan, not a generated app.

    mcp-tool

    {
      "type": "object",
      "required": [
        "idea"
      ],
      "properties": {
        "idea": {
          "type": "string",
          "maxLength": 600,
          "description": "What the app should do and who it is for, in plain English (max 600 characters)."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • plan_online_store unknown never probed

    Plan a small online store: page sections, product features, checkout options (Stripe Payment Links and/or thirdweb card-or-crypto checkout, both set up in the seller's own accounts), a compliance checklist, a launch checklist, honest limits and a link that opens the GYSM builder with a ready-made prompt. Free and instant: it makes no AI call and creates nothing. GYSM generates a single storefront page, not a full Shopify replacement.

    mcp-tool

    {
      "type": "object",
      "required": [
        "niche"
      ],
      "properties": {
        "niche": {
          "type": "string",
          "maxLength": 160,
          "description": "What the store sells, e.g. 'handmade candles' (max 160 characters)."
        },
        "currency": {
          "type": "string",
          "description": "ISO currency code such as EUR, USD or GBP. Defaults to EUR."
        },
        "payments": {
          "enum": [
            "stripe",
            "thirdweb",
            "both"
          ],
          "type": "string",
          "description": "Which checkout option to plan for. Defaults to stripe."
        },
        "products": {
          "type": "array",
          "items": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 80
              },
              {
                "type": "object",
                "required": [
                  "name"
                ],
                "properties": {
                  "name": {
                    "type": "string",
                    "maxLength": 80
                  },
                  "price": {
                    "type": "string",
                    "maxLength": 24
                  }
                },
                "additionalProperties": false
              }
            ]
          },
          "maxItems": 12,
          "description": "Optional product names, or objects with name and price."
        }
      },
      "additionalProperties": false
    }
    arguments 57 lines
  • list_use_cases unknown never probed

    List the kinds of sites and apps GYSM plans well (online store, restaurant, coaching, portfolio, event page, nonprofit, booking, SaaS and more) with an example prompt and a page for each. Read-only.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_build_link unknown never probed

    Return a link that opens the GYSM builder with a prompt already filled in. The user signs in and presses build themselves. Creates nothing and spends nothing.

    mcp-tool

    {
      "type": "object",
      "required": [
        "prompt"
      ],
      "properties": {
        "prompt": {
          "type": "string",
          "maxLength": 1800,
          "description": "The build prompt to pre-fill (max 1800 characters)."
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 20543bfffa200a11.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/20543bfffa200a11/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/20543bfffa200a11/badge.svg)](https://brick.blue/agent/20543bfffa200a11?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
100%

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.