Beste KI Tools

Server Details

KI-Tools nach Kategorien, mit echten Startdaten und über Stripe geprüften Umsätzen.

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 08:20
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, listing alternatives, viewing offers, creating checkout, and submitting. Even similar tools like list_alternatives and search_tools are clearly separated by their inputs and intended use cases.

Naming Consistency5/5

All tool names follow a consistent lowercase verb_noun snake_case pattern: create_checkout, get_tool, list_alternatives, list_offers, search_tools, submit_tool. The verb-first convention is uniform and predictable.

Tool Count5/5

Six tools is well-scoped for an AI tool directory covering discovery, details, alternatives, submission, and paid add-on checkout. Each tool earns its place and supports a clear workflow without redundancy.

Completeness4/5

The surface covers the main user journeys: search, view details, compare alternatives, submit a listing, and purchase promotion. Listing update or removal tools are not present, but that is likely handled through the maker claimUrl flow, so the gap is minor.

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 Beste KI Tools 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?

The annotations already declare readOnlyHint=true and idempotentHint=true, indicating a safe read operation. The description adds useful behavioral context beyond annotations: it discloses that the tool returns null for invalid slugs, indicating no error throw, and specifies the type of data returned (description, launch date, revenue signals, for-sale status). This is more than the annotations alone provide, hence a 4.

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 two sentences, tightly written, and front-loaded with the core action and input. Every phrase adds value: the slug format example, the recommended call sequence, and the null return behavior. There is no verbose or redundant text.

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 single parameter, high schema coverage, the presence of an output schema (automatically defining return structure), and read-only annotations, the description covers all necessary context: what to call, when to call, what to expect in return, and the null edge case. There is no gap that would hinder correct invocation.

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 schema has 100% coverage of the parameter 'slug' with its description 'The tool's listing slug.' The description reinforces this by explaining how the slug is derived (from search_tools' toolUrl) and gives an example. This matches the baseline of 3 for high schema coverage, and the added example provides slight extra value without overstepping.

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 slug, distinguishing it from siblings. It specifies the verb ('fetch'), the resource ('one AI tool'), and the precise input (slug from search_tools' toolUrl). It also provides an example of slug format, eliminating ambiguity.

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 to call this after search_tools to obtain full description, launch date, revenue signals, and for-sale status. It clarifies that the slug comes from search_tools' toolUrl, and notes that it returns null for unresolvable slugs, which guides the agent on when and how to use it.

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 Beste KI Tools 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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description doesn't need to restate that. It adds valuable behavioral details: case-insensitive substring matching on three fields, and a result cap of 20. This goes beyond annotations but doesn't cover pagination or sorting, which is minor given the output schema and simplicity.

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: the first covers purpose and matching scope, the second provides usage guidance and examples. No filler, front-loaded with the core purpose, and every sentence adds value.

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 simple tool (1 parameter, no nested objects) and presence of an output schema, the description fully covers what the agent needs: what it searches, how it matches, the usage context, and result limit. It is complete for its complexity level.

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 describes query as 'Free-text search term', but the description enriches it with what it matches against (name, tagline, category) and the case-insensitive nature. With 100% schema coverage, baseline is 3, but the added semantics about matching logic earns a 4.

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 the 'Beste KI Tools catalog' of live, published AI tools by free-text query, matching on name, tagline, or category. This specific verb+resource+scope distinguishes it from siblings like get_tool (exact retrieval) and list_alternatives (alternative discovery), and includes concrete examples.

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 explicitly instructs to 'Call this first when a user asks to find, discover, or compare AI tools by keyword, use-case, or category', providing clear guidance on when to use. It also gives example queries ('agents', 'writing assistants'). The mention of 'first' implies it's the entry point, aligning with sibling tools for follow-ups, though it doesn't enumerate exclusions. Still, the explicit directive is strong.

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 Beste KI Tools 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?

The description adds substantial behavioral detail beyond annotations: listings are drafts, not public; a claimUrl is returned; the tool is globally rate-limited to 5 submissions per hour; logo/image URLs are copied to storage. This gives the agent important operational expectations not conveyed by the readOnlyHint/idempotentHint/destructiveHint flags.

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?

Three sentences, front-loaded with the core purpose and result, followed by usage constraints and field guidance. No filler or repetition; every sentence adds value.

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?

For a tool with 11 parameters and an output schema, the description covers the most decision-critical context: draft vs public state, claim flow, rate limit, ownership/consent rule, and the role of optional fields. It is complete enough for an agent to invoke correctly without further documentation.

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 already 100%, so the baseline is 3. The description adds meaningful parameter guidance by emphasizing tagline, problemSolved, logoUrl, and imageUrls, explaining why they matter, and noting fallback behavior (e.g., truncated description, placeholder card) that is not in the schema itself.

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 Beste KI Tools on behalf of its maker') and the concrete result ('Creates a draft listing... returns a claimUrl'). It clearly differentiates this tool from read/list/search siblings by describing the submission and claimed-publish workflow.

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 when-to-use guidance is provided: 'Call this only when a user explicitly wants to list their own tool.' It also states a boundary condition ('never to submit a tool on someone else's behalf without their email'), which helps the agent avoid misuse despite there being no sibling tool with overlapping submission behavior.

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

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
KI Alternativen A
com.ki-alternativen
Alternativen zu bekannten KI-Tools, mit über Stripe geprüften Umsätzen statt Schätzungen.
AI & Machine Learning Finance
61
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
The AI Tools Index A
com.theaitoolsindex
AI tools filed by category, with real launch dates and revenue verified through Stripe.
AI & Machine Learning Open Data
61

Related MCP Servers

toolradar-mcp
Search Research & Data
Nadeus
A
license
A
quality
A
maintenance
Give your AI agent access to 8,400+ software tools — search, compare, get pricing, find alternatives, and discover the best tool for any use case.
Updated 19 days ago (2026-08-25 14:17 UTC)
8
119 npm
4
MIT
agent101-mcp
Search RAG Systems Agent Orchestration
rachelsu-blip
A
license
Not graded
quality
Not graded
maintenance
Search and discover 500+ tools, APIs, and services for AI agents. Browse 15 categories, get recommendations, and access structured metadata including auth methods, free tiers, and example calls.
Updated 6 months ago (2026-03-15 00:55 UTC)
1
-
ComparEdge Pricing API MCPofficial
AI & Machine Learning Search Data Platforms
comparedge
F
license
Not graded
quality
B
maintenance
Provides verified pricing data for SaaS, AI tools, and LLMs across 490+ tools. No API key required, returns sourced records with attribution links.
Updated 2 months ago (2026-07-15 11:25 UTC)
2
-
stripe-analytics-mcp
Finance Payments & Billing
npow
A
license
A
quality
F
maintenance
Provides real-time Stripe subscription analytics including MRR, churn, failed payments, and expiring trials. Enables AI assistants to answer business health questions like 'How's my business doing?'
Updated 6 months ago (2026-03-09 20:36 UTC)
8
MIT