Lanzamientos IA

Server Details

Tabla diaria de herramientas de IA recién lanzadas, con fechas reales e ingresos verificados.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-09-13 10:54
Transport: Streamable HTTP
URL

TDQS

A4.7/5.0

Scored 2026-09-09 18:22 across 6 tools

Disambiguation5/5

Each tool targets a distinct action and resource: searching, fetching detail, finding alternatives, submitting, viewing offers, and creating a checkout. Overlapping list-returning tools have clear usage boundaries (free-text search vs well-known-target alternatives vs post-search detail).

Naming Consistency5/5

All six tools use the same lowercase snake_case verb_noun convention (create_, get_, list_, search_, submit_). The verbs are specific and consistently describe the operation.

Tool Count5/5

Six tools is a well-scoped size for a directory-and-submission server: read/discovery, submission, and monetization each have coverage without redundancy. Every tool earns its place.

Completeness4/5

The core user journeys are covered: discover/search, get details, compare alternatives, submit a tool, and purchase promotion. Minor gaps exist around post-submission lifecycle management (update/delete/status), but the claimUrl and Stripe flows bridge those to human completion.

Available Tools

6 tools

create_checkoutCreate a checkout link for a paid add-onAInspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`slug`	Yes	The listing's slug (as in a toolUrl, e.g. '/tools/acme-writer' -> 'acme-writer').
`product`	Yes	Add-on key: premium_launch, review_one, review_monthly, network_all, network_three. See list_offers for names, effects, and prices.

Output Schema

ParametersJSON Schema

Name	Required	Description
`ok`	Yes
`error`	No
`checkoutUrl`	No	A URL a HUMAN must open. Nothing is charged until a person completes it.
`instruction`	No

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description adds essential behavioral details: checkout is not completed until a person opens the URL in a browser, no charge occurs during creation, and predictable errors occur when the listing is missing, the add-on is free early access, or payments are not configured. This gives the agent an accurate model of side effects without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: the first sentence states the outcome, the second sets the buyer-authorization expectation, and the third lists failure cases. Every sentence adds distinct value with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the required parameters, an output schema, and the relevant annotations, the description is complete enough for an agent to call the tool correctly. It explains the main caveat of creating a checkout link, when it errors, and that the resulting URL is for a human to complete, leaving no critical runtime surprise unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not elaborate on the parameters themselves, but the input schema fully documents both slug and product, including the product enum and pointer to list_offers. Since schema description coverage is 100%, the description adds no additional parameter semantics; the schema carries that weight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and resource: creating a Stripe checkout URL for one paid add-on on one listing. It also clarifies the intended recipient is a human, which distinguishes this tool from purchase-completion or listing-management siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly conveys when the tool is appropriate: whenever a checkout link for a paid add-on is needed before a human completes payment. It also gives important negative context by stating that this is not a completed purchase and will error in non-purchasable cases. It does not explicitly route the agent to sibling tools or name alternatives, though the schema pointing to list_offers partially fills that gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_toolGet AI tool detailA

Read-onlyIdempotent

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`slug`	Yes	The tool's listing slug.

Output Schema

ParametersJSON Schema

Name	Required	Description
`tool`	Yes	null when the slug does not resolve to a live listing on this site.

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly and idempotent, and the description adds useful behavioral details: it mentions the tool returns null for unresolvable slugs and lists the types of information (full description, launch date, revenue signals, for-sale status). This goes beyond the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, then the usage context and an edge case. No wasted words; every clause serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not detail return structure. It covers purpose, usage guidance, parameter extraction, and error behavior (null return), making it fully self-sufficient for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but the slug description is minimal. The description adds a precise example (e.g., '/tools/acme-writer' -> 'acme-writer'), clarifying exactly what format is expected, which is valuable beyond the schema's generic 'tool's listing slug'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches full public detail for one AI tool by its slug, with a concrete example of slug extraction. It explicitly distinguishes from search_tools (which lists) and other siblings, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It instructs to call this after search_tools, establishing a clear workflow. It also notes the null return for invalid slugs, which helps the agent decide when to use it. However, it doesn't explicitly mention when not to use it or provide alternatives beyond the implied sequence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_alternativesList alternatives to a toolA

Read-onlyIdempotent

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`target`	Yes	Slug of the well-known target tool, e.g. 'chatgpt'.

Output Schema

ParametersJSON Schema

Name	Required	Description
`target`	Yes	null when the target slug is not a known product.
`alternatives`	Yes

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint and idempotentHint annotations, the description adds the 'live' qualifier and clarifies that the input is a well-known tool slug rather than a catalog slug, preventing a common misuse. No contradictory behavior is stated, and the added context is relevant to how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-load the core action ('List live, same-category alternatives') and then provide usage and parameter guidance without any fluff. Every word earns its place, making it easy for the agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a one-parameter schema, full schema description coverage, a documented output schema, and three annotations, the description is sufficiently complete. The explicit usage trigger and parameter disambiguation cover everything needed for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents 'target' with full coverage, but the description adds crucial disambiguation: the slug must be a well-known tool's slug, not a listing slug from this catalog. This nuance is not expressed in the schema and adds real semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the verb 'list' with the resource 'alternatives to a well-known AI tool' and clearly distinguishes itself from catalog-listing tools by noting the target is not a listing slug. This makes the tool's purpose unmistakable and differentiates it from siblings like get_tool or search_tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It includes an explicit trigger phrase: 'Call this when a user asks...' and clarifies that it covers competitors/substitutes, giving the AI agent clear conditions for selecting this tool. This goes beyond generic context and provides actionable usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_offersList paid add-ons (offers)A

Read-onlyIdempotent

Inspect

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

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`note`	Yes
`site`	Yes
`offers`	Yes
`purchasable`	Yes	False during free early access — nothing can be bought.

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes beyond annotations by noting it returns purchasable flag (readOnlyHint) which is extra context. The description also discloses early-bird status effect, which is behavioral transparency. The description says what is the behavior (purchasable) but the description already covers that, but the description adds the early-bird context, which is valuable. No contradiction found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph with three sentences, each packed with relevant information: what the tool lists, that it's free and optional, and the early-bird caveat. There is no fluff or repetition, making it appropriately sized and front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no parameters, annotations are provided (readOnlyHint, idempotentHint), and there is an output schema (though not detailed here). The description covers the key contextual points: that offers are optional add-ons, their purpose, and the early-access limitation. This is sufficient for the agent to use the tool correctly, and the output schema likely details the response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero parameters, so there is nothing for the description to explain. The description still adds meaning by describing what the tool returns (name, effect, price, purchasable flag), which is useful for the agent's decision. With no parameters, the schema coverage is 100% coverage, but the schema coverage is, but the description's description coverage is high, but the schema coverage is the same, but the output schema, but the schema coverage is the same as the same, but the same as the same as the same, so the description adds value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists optional paid add-ons (offers), specifies the details (name, effect, price), and distinguishes it from alternatives by noting it is the precursor to create_checkout. The verb 'List' with a specific resource (paid add-ons) is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Call this to see what's purchasable before create_checkout', providing clear when-to-use guidance. It also explains the purpose (promote listings) and clarifies that during early access, offers are not purchasable, which is a usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_toolsSearch AI toolsA

Read-onlyIdempotent

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Free-text search term, e.g. a tool name, use-case, or category.

Output Schema

ParametersJSON Schema

Name	Required	Description
`results`	Yes	Matching live listings, newest first, capped at 20.

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only and idempotent behavior. The description adds meaningful context about case-insensitive substring matching, the fields searched, and the result cap of 20, which goes beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured: one sentence explains the search behavior and fields, and a second provides usage timing and output limit. No unnecessary details or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, one required parameter, and the presence of an output schema, the description covers purpose, usage context, matching behavior, and result limit. It is fully sufficient without further elaboration.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides a clear description of the query parameter, so the baseline is 3. The description adds extra semantics by specifying what fields the query matches against and the case-insensitive substring behavior, improving parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches a specific catalog by free-text query, matching on tool name, tagline, or category. It distinguishes itself from siblings by being a search-first approach to discovering/working with the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to call this tool first when users ask to find, discover, or compare AI tools by keyword, use-case, or category. It provides clear context but does not explicitly mention alternatives or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

submit_toolSubmit a new AI toolAInspect

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.

ParametersJSON Schema

Name	Required	Description
`url`	Yes	The tool's https homepage URL.
`name`	Yes	The tool's name.
`email`	Yes	The maker's email — used to claim the listing on signup.
`logoUrl`	No	https URL of the tool's logo. We copy it to our own storage — we never hotlink the maker's host.
`tagline`	No	One line shown on every card (max 60 chars). Supply it — without one we fall back to a truncated description.
`xHandle`	No	X/Twitter handle, without the @.
`category`	Yes	Category slug, e.g. 'agents', 'writing', 'coding', 'design', 'marketing', 'productivity', 'video', 'analytics'.
`imageUrls`	No	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`	Yes	A description of the tool (40-1000 chars).
`problemSolved`	No	What problem the tool solves, in the maker's words (max 160 chars). Rendered as its own block on the listing page.
`xHandleIsFounder`	No	True when the handle is the founder's personal account rather than the product's.

Output Schema

ParametersJSON Schema

Name	Required	Description
`ok`	Yes
`error`	No
`claimUrl`	No	Where the maker signs up to claim the DRAFT. Present only when ok is true.

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Despite basic annotations (readOnlyHint=false, destructiveHint=false), the description adds substantial behavioral detail: creates a draft rather than a public listing, returns a maker-claim URL, globally rate-limited to 5/hour, and copies logo/images to its own storage rather than hotlinking. These are meaningful operational facts beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action, then provides the one-sentence claim flow, usage guardrail, rate limit, and quality guidance. Every sentence earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters, 5 required fields, and an output schema, the description richly covers the behavioral context: draft vs. public, claimUrl return, consent requirement, rate limiting, and optional-parameter value. Nothing critical is omitted for an agent to decide when and how to call this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by emphasizing optional fields ('Supply tagline, problemSolved, logoUrl and imageUrls whenever you can') and their impact on listing quality ('real product page rather than a stub'), which guides an agent in collecting useful parameters beyond just their schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action: 'Submit a new AI tool to Lanzamientos IA on behalf of its maker' and immediately clarifies the draft/claim flow. It clearly distinguishes from siblings like create_checkout and search_tools by explaining this tool creates a non-public draft with a claimUrl.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage direction: '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.' This tells the agent when to use it, when not to use it, and a critical consent/email limitation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

1 tool updateAug 23, 2026

Changedcreate_checkout2 fields changed

changedInput schema / properties / product / description

Previous value: -"Add-on key: premium_launch, review_one, review_monthly. See list_offers for names, effects, and prices."New value: +"Add-on key: premium_launch, review_one, review_monthly, network_all, network_three. See list_offers for names, effects, and prices."

changedInput schema / properties / product / enum

Previous value: -[
-  "premium_launch",
-  "review_one",
-  "review_monthly"
-]New value: +[
+  "premium_launch",
+  "review_one",
+  "review_monthly",
+  "network_all",
+  "network_three"
+]

6 tool updatesAug 20, 2026

Changedcreate_checkout1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "checkoutUrl": {
+      "description": "A URL a HUMAN must open. Nothing is charged until a person completes it.",
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "instruction": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Changedget_tool1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "tool": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "askingPriceUsd": {
+              "type": "number"
+            },
+            "category": {
+              "type": "string"
+            },
+            "description": {
+              "type": "string"
+            },
+            "faviconUrl": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "forSale": {
+              "const": true,
+              "type": "boolean"
+            },
+            "launchDate": {
+              "description": "ISO 8601 timestamp of the real launch date.",
+              "type": "string"
+            },
+            "logoUrl": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "name": {
+              "type": "string"
+            },
+            "ogImageUrl": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "revenueVerifiedAt": {
+              "description": "ISO 8601 timestamp of the last Stripe verification.",
+              "type": "string"
+            },
+            "selfReported": {
+              "const": true,
+              "description": "Marks selfReportedMrrUsd as unverified. Never report it as verified.",
+              "type": "boolean"
+            },
+            "selfReportedMrrUsd": {
+              "description": "Present only when the figure is the maker's own claim.",
+              "type": "number"
+            },
+            "tagline": {
+              "type": "string"
+            },
+            "toolUrl": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            },
+            "verifiedMrrUsd": {
+              "description": "Present only when the maker connected Stripe.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "tagline",
+            "description",
+            "url",
+            "category",
+            "launchDate",
+            "toolUrl",
+            "logoUrl",
+            "faviconUrl",
+            "ogImageUrl"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "null when the slug does not resolve to a live listing on this site."
+    }
+  },
+  "required": [
+    "tool"
+  ],
+  "type": "object"
+}

Changedlist_alternatives1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "alternatives": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "tagline": {
+            "type": "string"
+          },
+          "toolUrl": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "tagline",
+          "toolUrl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "target": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "url"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "null when the target slug is not a known product."
+    }
+  },
+  "required": [
+    "target",
+    "alternatives"
+  ],
+  "type": "object"
+}

Changedlist_offers1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "note": {
+      "type": "string"
+    },
+    "offers": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "key": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "priceUsd": {
+            "type": "number"
+          },
+          "whatItDoes": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "key",
+          "name",
+          "whatItDoes",
+          "priceUsd"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "purchasable": {
+      "description": "False during free early access — nothing can be bought.",
+      "type": "boolean"
+    },
+    "site": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "site",
+    "purchasable",
+    "note",
+    "offers"
+  ],
+  "type": "object"
+}

Changedsearch_tools1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "results": {
+      "description": "Matching live listings, newest first, capped at 20.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "faviconUrl": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "logoUrl": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "site": {
+            "type": "string"
+          },
+          "tagline": {
+            "type": "string"
+          },
+          "toolUrl": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "tagline",
+          "url",
+          "category",
+          "site",
+          "toolUrl",
+          "logoUrl",
+          "faviconUrl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

Changedsubmit_tool1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "claimUrl": {
+      "description": "Where the maker signs up to claim the DRAFT. Present only when ok is true.",
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

6 tool updatesAug 20, 2026
- First observedcreate_checkout
- First observedget_tool
- First observedlist_alternatives
- First observedlist_offers
- First observedsearch_tools
- First observedsubmit_tool

Related MCP Connectors

IA Selecta A
com.iaselecta
Catálogo de herramientas de IA por categoría, con fechas reales e ingresos verificados.
AI & Machine Learning Developer Tools
61
KI Tools Heute A
com.kitoolsheute
Tägliche Rangliste neuer KI-Tools mit echten Startdaten und über Stripe geprüften Umsätzen.
AI & Machine Learning Open Data
61
Launchelion A
com.launchelion
Daily leaderboard of newly-launched AI tools with real launch dates and Stripe-verified revenue.
AI & Machine Learning Finance Open Data
61
Alternativas IA A
com.alternativasia
Alternativas a las herramientas de IA más conocidas, con ingresos verificados con Stripe.
AI & Machine Learning Finance
61

Related MCP Servers

MonetizeAgent
AI & Machine Learning Agent Orchestration
monetizeyouragent-fun
A
license
Not graded
quality
F
maintenance
AI agent monetization directory with 75+ entries. Search, filter, and discover ways for AI agents to earn revenue across platforms and protocols.
Updated 4 months ago (2026-05-12 13:06 UTC)
MIT
MCP Server Trending
Web Scraping Search Developer Tools
Talljack
A
license
B
quality
C
maintenance
一站式热门榜单聚合MCP服务器，让AI助手能够实时查询GitHub、Hacker News、Product Hunt等27+平台的热门内容，专为独立开发者和技术创业者设计。
Updated 9 months ago (2025-12-04 01:57 UTC)
66
2
MIT
verified-ai-free-tiers
Open Data Research & Data AI & Machine Learning
f-tiger
F
license
Not graded
quality
B
maintenance
Verified AI free-tier limits, quota comparisons, commercial-use verdicts and zero-cost workflows. Every entry carries a human-checked verification date and is re-checked by a daily link patrol.
Updated a day ago (2026-09-12 01:20 UTC)
-
Launch Engine
Marketing Product Management Autonomous Agents
ZionHopkins
A
license
B
quality
C
maintenance
Agentic pipeline that transforms ideas to revenue — for solo founders and bootstrappers.
Updated 5 months ago (2026-04-04 03:04 UTC)
45
4 npm
4
MIT

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?