_ registry / a2a + mcp http-sse · checked 12h ago

Lanzamientos IA

https://lanzamientosia.com

Registry code: 05855ce1dc4522c0

api record

Lanzamientos IA is a daily leaderboard of newly-launched AI tools: real launch dates, one-vote-per-signed-in-account-per-day community upvotes, and — when a maker connects Stripe — verified monthly revenue instead of invented traction.

endpoint
https://lanzamientosia.com/api/mcp/mcp
door code
39fba43acb758e79
protocol
http-sse ·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 Lanzamientos IA live?
Yes — it answered the hub's last check (checked 12h ago). It answered 96% of checks over the last 30 days.
Is Lanzamientos IA free to use?
Yes — the hub reached it with no key and no payment.
What tools does Lanzamientos IA have?
6 tools: get_tool, search_tools, submit_tool, create_checkout, list_alternatives, list_offers.
Is Lanzamientos IA 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
96.2%

90 days 97.7%· all time 97.6%

latency
210ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 735 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • down → live
  • degraded → down· timeout after 20000ms
_ what it is for
used for
  • search newly launched ai tools
  • get an ai tool listing
takes → gives
text → data
_ 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 6 tools
1 open 5 never probed 1 of 6 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.

  • list_offers open 11d ago

    List the optional paid add-ons a maker can buy to promote their listing (name, one-sentence effect, price in USD). Listing is always free; these only ADD reach and are always labeled 'Sponsored'. Call this to see what's purchasable before create_checkout. During free early access (early-bird), offers are not yet purchasable and this says so (purchasable=false).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_tool unknown 12h ago

    Fetch the full public detail for one AI tool by its listing slug (as returned by search_tools' toolUrl, e.g. '/tools/acme-writer' -> slug 'acme-writer'). Call this after search_tools to get a tool's full description, launch date, revenue signals (verified or self-reported), and for-sale status. Returns null if the slug doesn't resolve to a live Lanzamientos IA listing.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "minLength": 1,
          "description": "The tool's listing slug."
        }
      }
    }
    arguments 14 lines
  • search_tools unknown 12h ago

    Search the Lanzamientos IA catalog of live, published AI tools by a free-text query. Matches on tool name, tagline, or category name (case-insensitive substring). Call this first when a user asks to find, discover, or compare AI tools by keyword, use-case, or category (e.g. 'agents', 'writing assistants'). Returns up to 20 results.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Free-text search term, e.g. a tool name, use-case, or category."
        }
      }
    }
    arguments 14 lines
  • submit_tool unknown never probed

    Submit a new AI tool to Lanzamientos IA on behalf of its maker. Creates a draft listing (not yet public) and returns a claimUrl the maker must visit to sign up and claim/publish it. Call this only when a user explicitly wants to list their own tool — never to submit a tool on someone else's behalf without their email. Rate-limited globally to 5 submissions per hour. Supply tagline, problemSolved, logoUrl and imageUrls whenever you can: they are what make the published listing look like a real product page rather than a stub.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name",
        "url",
        "description",
        "category",
        "email"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "The tool's https homepage URL."
        },
        "name": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "The tool's name."
        },
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "description": "The maker's email — used to claim the listing on signup."
        },
        "logoUrl": {
          "type": "string",
          "format": "uri",
          "description": "https URL of the tool's logo. We copy it to our own storage — we never hotlink the maker's host."
        },
        "tagline": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "One line shown on every card (max 60 chars). Supply it — without one we fall back to a truncated description."
        },
        "xHandle": {
          "type": "string",
          "description": "X/Twitter handle, without the @."
        },
        "category": {
          "type": "string",
          "description": "Category slug, e.g. 'agents', 'writing', 'coding', 'design', 'marketing', 'productivity', 'video', 'analytics'."
        },
        "imageUrls": {
          "type": "array",
          "items": {
            "type": "string",
            "format": "uri"
          },
          "maxItems": 5,
          "description": "Up to 5 https screenshot URLs, best first. Copied to our own storage. Without any, the listing shows a generated placeholder card instead of a real screenshot."
        },
        "description": {
          "type": "string",
          "maxLength": 1000,
          "minLength": 40,
          "description": "A description of the tool (40-1000 chars)."
        },
        "problemSolved": {
          "type": "string",
          "maxLength": 160,
          "description": "What problem the tool solves, in the maker's words (max 160 chars). Rendered as its own block on the listing page."
        },
        "xHandleIsFounder": {
          "type": "boolean",
          "description": "True when the handle is the founder's personal account rather than the product's."
        }
      }
    }
    arguments 73 lines
  • create_checkout unknown never probed

    Create a Stripe checkout URL for one paid add-on on one listing, and return it for a HUMAN to open. Never present this as a completed purchase: nothing is charged until a person completes checkout in a browser. Returns an error when the listing doesn't exist, the add-on isn't purchasable yet (free early access), or payments aren't configured in this environment.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug",
        "product"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "minLength": 1,
          "description": "The listing's slug (as in a toolUrl, e.g. '/tools/acme-writer' -> 'acme-writer')."
        },
        "product": {
          "enum": [
            "premium_launch",
            "review_one",
            "review_monthly",
            "network_all",
            "network_three"
          ],
          "type": "string",
          "description": "Add-on key: premium_launch, review_one, review_monthly, network_all, network_three. See list_offers for names, effects, and prices."
        }
      }
    }
    arguments 26 lines
  • list_alternatives unknown 12h ago

    List live, same-category alternatives to a well-known AI tool (e.g. 'chatgpt', 'notion-ai', 'figma'). Call this when a user asks 'what are the alternatives to X' or wants competitors/substitutes for a named product. `target` is the well-known tool's slug, not a listing slug from this catalog.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "target"
      ],
      "properties": {
        "target": {
          "type": "string",
          "minLength": 1,
          "description": "Slug of the well-known target tool, e.g. 'chatgpt'."
        }
      }
    }
    arguments 14 lines
_ try it over mcp 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 agent card — 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 05855ce1dc4522c0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/05855ce1dc4522c0/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/05855ce1dc4522c0/badge.svg)](https://brick.blue/agent/05855ce1dc4522c0?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 knowoff the a2a door
card completeness
90%

How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.

spec deviations
0

Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.

_ 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.