Manufact

LeaderboardBack to leaderboard

AZN8 product directory

azn8.com/mcp

View checks

Protocol: MCP 2025-06-18
Server version: 1.0.0
Supports: Tools

Overall score

How is this score calculated?

Last reviewed at Nov 11, 2026, 23:50:46 UTC

Server metadata

Warnings60/100

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

azn8

10/10Source

Human-readable title

AZN8 product directory

10/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 1.0.0

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Usage instructions provided for agents.

20/20Source

Declared capabilities

Supports Tools.

10/10Source

Server instructions

AZN8 is a free SaaS/startup/AI product directory. Use search_listings and get_listing to browse live products. To publish a product: call register_account once with a real inbox, open the verification link it emails, sign in and mint a key (POST /api/auth/sign-in/email, POST /api/v1/api-keys), then submit_listing. Or reuse an existing azn8_ API key. To change an existing listing, including its website_url, call update_listing with its slug. Authenticate write tools with an Authorization: Bearer <api_key> header on the MCP connection, or pass api_key in the tool arguments. Submit genuine products only. Adult content, drugs, and illegal goods are rejected with code content_policy.

Discoverability

17/100

Client listings and public setup information.

mcp.json or server-card.json

Either mcp.json or an MCP Server Card declaring this endpoint passes.

The manifest declares this MCP server's exact endpoint.

FoundSource

Setup instructions at MCP URL

The public page returned HTTP 405.

Not foundSource

ChatGPT

No ChatGPT listing has been confirmed yet.

UnverifiedHow to get listed

Claude

No Claude listing has been confirmed yet.

UnverifiedHow to get listed

CursorGrok BotGrok

No Cursor marketplace listing has been confirmed yet.

UnverifiedHow to get listed

Muse

No Muse listing has been confirmed yet.

UnverifiedHow to get listed

4 unverified checks. Unverified checks earn no points until confirmed.

Protocol

Pass100/100

Connection, authentication, and protocol compatibility.

Resources list responds

0 resource(s) returned

Source

Tools list returns results

8 tool(s) returned

Source

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 532ms

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Issues93/100

Tool definitions, annotations, and client compatibility.

Claude Code metadata fits its 2 KB fields

Tool descriptions and server instructions fit Claude Code's 2 KB fields

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

Claude tools declare applicable behavior hints

All tools include an applicable readOnlyHint or destructiveHint

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

All tools have descriptions

All tools have non-empty descriptions

All tools have OpenAI behavior hints

3 behavior annotation issue(s) found

How to fix: On each tool, declare annotations.readOnlyHint, annotations.destructiveHint, and annotations.openWorldHint as booleans. The policy review separately assesses whether their values match the tool's actual behavior.

errorChatGPT

Source

Tool names use valid characters

All tool names use valid characters

Source

All tools have a display title

Source

ChatGPT tool names are unique

All tool names are unique

Source

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

Declared output schemas have a valid basic structure

0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

MCP Apps

Not applicableOptional

App resources, metadata, and rendering requirements.

CSP metadata covers literal external origins

No view resources found — view checks skipped

Source

Tool-linked resource URI is readable

No view resources found — view checks skipped

Source

Declared domains respond

No view resources found — view checks skipped

Tool invocation metadata present

No view resources found — view checks skipped

Source

Views do not request nested iframe domains

No view resources found — view checks skipped

Source

View resource metadata complete

No view resources found — view checks skipped

Source

All discovered view resources were inspected

No view resources found — view checks skipped

Source

Tool visibility metadata is valid

No view resources found — view checks skipped

Source

View resource envelope is valid

No view resources found — view checks skipped

View resources declare a domain

No view resources found — view checks skipped

Source

Tool documentation quality

70/100

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

search_listingsTitles 94Descriptions 90Inputs 17Annotations 50Outputs 059/100

search_listings

Title94/100

Search listings

The title clearly communicates the tool’s action and subject. Keep it concise.

Description90/100

Search live products in the AZN8 directory. Returns name, tagline, website, pricing, categories, and the AZN8 listing URL.

The description explains the capability, when to use it, and what to expect.

Inputs17/100

1 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

query

Free-text search over name, tagline, and description

Clear enough to supply this argument.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_listings",
  "title": "Search listings",
  "description": "Search live products in the AZN8 directory. Returns name, tagline, website, pricing, categories, and the AZN8 listing URL.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "page": {
        "type": "integer",
        "default": 1,
        "minimum": 1
      },
      "sort": {
        "enum": [
          "newest",
          "name"
        ],
        "type": "string",
        "default": "newest"
      },
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 50,
        "minimum": 1
      },
      "query": {
        "type": "string",
        "description": "Free-text search over name, tagline, and description"
      },
      "pricing": {
        "enum": [
          "free",
          "freemium",
          "subscription",
          "one-time",
          "usage",
          "contact"
        ],
        "type": "string"
      },
      "category": {
        "enum": [
          "saas",
          "developer-tools",
          "productivity",
          "marketing",
          "ai",
          "domains",
          "marketplace",
          "analytics",
          "design",
          "sales",
          "customer-support",
          "finance",
          "education",
          "security",
          "no-code",
          "other"
        ],
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false
  }
}

get_listingTitles 98Descriptions 78Inputs 91Annotations 50Outputs 076/100

get_listing

Title98/100

Get listing

The title clearly communicates the tool’s action and subject. Keep it concise.

Description78/100

Get one listing by slug, including description and features.

Describe the returned information so the agent knows whether it will answer the request.

Inputs91/100

Input documentation gives an agent enough context to populate the arguments.

slug

Listing slug, e.g. northstar-deploys

Clear enough to supply this argument.

api_key

AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>.

Clear enough to supply this argument.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_listing",
  "title": "Get listing",
  "description": "Get one listing by slug, including description and features.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "Listing slug, e.g. northstar-deploys"
      },
      "api_key": {
        "type": "string",
        "description": "AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false
  }
}

register_accountTitles 99Descriptions 92Inputs 19Annotations 100Outputs 066/100

register_account

Title99/100

The title clearly communicates the tool’s action and subject. Keep it concise.

Description92/100

Create an AZN8 account. Use a real inbox you can read (Gmail plus-aliases are fine); password must be 8+ characters. name must be a real person, team, or product name: random mixed-case letter strings (e.g. yPGhfPytTQLguskekmDMjPx) are rejected with invalid_name, and Gmail addresses split into many short dotted pieces (e.g. [email protected]) with invalid_email; no verification email is sent for either. A verification link is emailed; after opening it, sign in with POST /api/auth/sign-in/email and mint a key with POST /api/v1/api-keys for submit_listing. (If verification is turned off, the key is returned here once.)

Describe the returned information so the agent knows whether it will answer the request.

Inputs19/100

1 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

Display name for the account: a real person, team, or product name. Random letter strings are rejected (invalid_name).

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Not provided

Missing description. Explain what this value means and how to supply it.

password

Not provided

Missing description. Explain what this value means and how to supply it.

key_name

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "register_account",
  "title": "Register account",
  "description": "Create an AZN8 account. Use a real inbox you can read (Gmail plus-aliases are fine); password must be 8+ characters. name must be a real person, team, or product name: random mixed-case letter strings (e.g. yPGhfPytTQLguskekmDMjPx) are rejected with invalid_name, and Gmail addresses split into many short dotted pieces (e.g. [email protected]) with invalid_email; no verification email is sent for either. A verification link is emailed; after opening it, sign in with POST /api/auth/sign-in/email and mint a key with POST /api/v1/api-keys for submit_listing. (If verification is turned off, the key is returned here once.)",
  "inputSchema": {
    "type": "object",
    "required": [
      "name",
      "email",
      "password"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Display name for the account: a real person, team, or product name. Random letter strings are rejected (invalid_name)."
      },
      "email": {
        "type": "string",
        "format": "email"
      },
      "key_name": {
        "type": "string",
        "default": "primary",
        "maxLength": 60
      },
      "password": {
        "type": "string",
        "minLength": 8
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": false,
    "destructiveHint": false
  }
}

submit_listingTitles 96Descriptions 97Inputs 53Annotations 100Outputs 076/100

submit_listing

Title96/100

Submit listing

The title clearly communicates the tool’s action and subject. Keep it concise.

Description97/100

Create or update a product listing. website_url's domain is the idempotency key (one listing per domain): re-submitting your own domain updates the listing; someone else's domain returns their public record. Returns the public listing URL and status (live when auto-publish is on).

The description explains the capability, when to use it, and what to expect.

Inputs53/100

6 of 10 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

Product name

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

website_url

Product website on its own root domain (subdomains like app.example.com or x.vercel.app are rejected). One listing per domain: re-submitting a URL on your listed domain updates your listing.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

tagline

One-line pitch

Clear enough to supply this argument.

description

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "submit_listing",
  "title": "Submit listing",
  "description": "Create or update a product listing. website_url's domain is the idempotency key (one listing per domain): re-submitting your own domain updates the listing; someone else's domain returns their public record. Returns the public listing URL and status (live when auto-publish is on).",
  "inputSchema": {
    "type": "object",
    "required": [
      "name",
      "website_url",
      "tagline"
    ],
    "properties": {
      "name": {
        "type": "string",
        "maxLength": 80,
        "description": "Product name"
      },
      "api_key": {
        "type": "string",
        "description": "AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>."
      },
      "tagline": {
        "type": "string",
        "maxLength": 160,
        "description": "One-line pitch"
      },
      "features": {
        "type": "array",
        "items": {
          "type": "string",
          "maxLength": 120
        },
        "maxItems": 8
      },
      "cta_label": {
        "type": "string",
        "maxLength": 40,
        "description": "Button text"
      },
      "categories": {
        "type": "array",
        "items": {
          "enum": [
            "saas",
            "developer-tools",
            "productivity",
            "marketing",
            "ai",
            "domains",
            "marketplace",
            "analytics",
            "design",
            "sales",
            "customer-support",
            "finance",
            "education",
            "security",
            "no-code",
            "other"
          ],
          "type": "string"
        },
        "maxItems": 5
      },
      "description": {
        "type": "string",
        "maxLength": 4000
      },
      "website_url": {
        "type": "string",
        "maxLength": 500,
        "description": "Product website on its own root domain (subdomains like app.example.com or x.vercel.app are rejected). One listing per domain: re-submitting a URL on your listed domain updates your listing."
      },
      "pricing_model": {
        "enum": [
          "free",
          "freemium",
          "subscription",
          "one-time",
          "usage",
          "contact"
        ],
        "type": "string"
      },
      "pricing_summary": {
        "type": "string",
        "maxLength": 80,
        "description": "Public price line, e.g. \"From $39/mo\""
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

update_listingTitles 99Descriptions 92Inputs 50Annotations 100Outputs 074/100

update_listing

Title99/100

Update listing

The title clearly communicates the tool’s action and subject. Keep it concise.

Description92/100

Edit one of your listings in place by slug. Use this to change website_url (for example to add utm_* parameters) without creating a new listing; slug, status, and owner stay the same. Omitted fields are left unchanged; send an empty string or array to clear an optional field.

The description explains the capability, when to use it, and what to expect.

Inputs50/100

7 of 11 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

slug

Listing slug, e.g. northstar-deploys

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

name

Product name

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

website_url

Product website on its own root domain (subdomains like app.example.com or x.vercel.app are rejected). One listing per domain: re-submitting a URL on your listed domain updates your listing.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

tagline

One-line pitch

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

description

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_listing",
  "title": "Update listing",
  "description": "Edit one of your listings in place by slug. Use this to change website_url (for example to add utm_* parameters) without creating a new listing; slug, status, and owner stay the same. Omitted fields are left unchanged; send an empty string or array to clear an optional field.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "name": {
        "type": "string",
        "maxLength": 80,
        "description": "Product name"
      },
      "slug": {
        "type": "string",
        "description": "Listing slug, e.g. northstar-deploys"
      },
      "api_key": {
        "type": "string",
        "description": "AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>."
      },
      "tagline": {
        "type": "string",
        "maxLength": 160,
        "description": "One-line pitch"
      },
      "features": {
        "type": "array",
        "items": {
          "type": "string",
          "maxLength": 120
        },
        "maxItems": 8
      },
      "cta_label": {
        "type": "string",
        "maxLength": 40,
        "description": "Button text"
      },
      "categories": {
        "type": "array",
        "items": {
          "enum": [
            "saas",
            "developer-tools",
            "productivity",
            "marketing",
            "ai",
            "domains",
            "marketplace",
            "analytics",
            "design",
            "sales",
            "customer-support",
            "finance",
            "education",
            "security",
            "no-code",
            "other"
          ],
          "type": "string"
        },
        "maxItems": 5
      },
      "description": {
        "type": "string",
        "maxLength": 4000
      },
      "website_url": {
        "type": "string",
        "maxLength": 500,
        "description": "Product website on its own root domain (subdomains like app.example.com or x.vercel.app are rejected). One listing per domain: re-submitting a URL on your listed domain updates your listing."
      },
      "pricing_model": {
        "enum": [
          "free",
          "freemium",
          "subscription",
          "one-time",
          "usage",
          "contact"
        ],
        "type": "string"
      },
      "pricing_summary": {
        "type": "string",
        "maxLength": 80,
        "description": "Public price line, e.g. \"From $39/mo\""
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

list_my_listingsTitles 98Descriptions 79Inputs 99Annotations 50Outputs 079/100

list_my_listings

Title98/100

List my listings

The title clearly communicates the tool’s action and subject. Keep it concise.

Description79/100

List every listing owned by the authenticated account, in any status.

Describe the returned information so the agent knows whether it will answer the request.

Inputs99/100

Input documentation gives an agent enough context to populate the arguments.

api_key

AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>.

Clear enough to supply this argument.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_my_listings",
  "title": "List my listings",
  "description": "List every listing owned by the authenticated account, in any status.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "api_key": {
        "type": "string",
        "description": "AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false
  }
}

set_listing_statusTitles 95Descriptions 84Inputs 25Annotations 100Outputs 064/100

set_listing_status

Title95/100

Archive or restore a listing

The title clearly communicates the tool’s action and subject. Keep it concise.

Description84/100

Archive one of your listings (hides it from the public directory) or restore an archived listing to live.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs25/100

1 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

slug

Not provided

Missing description. Explain what this value means and how to supply it.

action

Not provided

Missing description. Explain what this value means and how to supply it.

reason

Not provided

Missing description. Explain what this value means and how to supply it.

api_key

AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>.

Clear enough to supply this argument.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "set_listing_status",
  "title": "Archive or restore a listing",
  "description": "Archive one of your listings (hides it from the public directory) or restore an archived listing to live.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug",
      "action"
    ],
    "properties": {
      "slug": {
        "type": "string"
      },
      "action": {
        "enum": [
          "archive",
          "restore"
        ],
        "type": "string"
      },
      "reason": {
        "type": "string",
        "maxLength": 500
      },
      "api_key": {
        "type": "string",
        "description": "AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

boost_listingTitles 89Descriptions 94Inputs 33Annotations 100Outputs 068/100

boost_listing

Title89/100

Feature (boost) a listing

Shorten the title to an action and subject; move usage details into the description.

Description94/100

Optional paid placement: pin one of your live listings in the featured row on the home page and its category pages. Returns a Stripe checkout_url for a human to pay; the listing is featured once payment succeeds. One-time, no renewal: week ($9 once for 7 days). Subscriptions that renew until cancelled: month ($29/month), 6-months ($149 every 6 months), year ($249/year). Free listings never need this.

The description explains the capability, when to use it, and what to expect.

Inputs33/100

1 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

slug

Not provided

Missing description. Explain what this value means and how to supply it.

plan

Not provided

Missing description. Explain what this value means and how to supply it.

api_key

AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>.

Clear enough to supply this argument.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "boost_listing",
  "title": "Feature (boost) a listing",
  "description": "Optional paid placement: pin one of your live listings in the featured row on the home page and its category pages. Returns a Stripe checkout_url for a human to pay; the listing is featured once payment succeeds. One-time, no renewal: week ($9 once for 7 days). Subscriptions that renew until cancelled: month ($29/month), 6-months ($149 every 6 months), year ($249/year). Free listings never need this.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug",
      "plan"
    ],
    "properties": {
      "plan": {
        "enum": [
          "week",
          "month",
          "6-months",
          "year"
        ],
        "type": "string"
      },
      "slug": {
        "type": "string"
      },
      "api_key": {
        "type": "string",
        "description": "AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01Search listingsSearch live products in the AZN8 directory.
02Get listingGet one listing by slug, including description and features.
03List my listingsList every listing owned by the authenticated account, in any status.

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

Overview

Category: Commerce & shopping

FAQ

AZN8 product directory setup, tools, quality score, publishing readiness, and alternatives.

How do I add AZN8 product directory to Claude, ChatGPT, or Cursor?

Add AZN8 product directory to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://azn8.com/mcp.

Is AZN8 product directory MCP ready for ChatGPT and Claude?

As of November 11, 2026, AZN8 product directory scores 94/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is AZN8 product directory's MCP tool documentation?

As of November 11, 2026, AZN8 product directory scores 70/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 8 of 8 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What are the best alternatives to AZN8 product directory?

As of November 12, 2026, alternatives to AZN8 product directory in commerce-shopping on the Manufact MCP leaderboard include REMAX Europe, Product Hunt, Square Yards, AEDI-V, and abomio.de.

How can AZN8 product directory improve its MCP documentation?

search_listings is the lowest-scoring reviewed tool at 59/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

LeaderboardBack to leaderboardLeaderboardBack to leaderboard

Opening report…

Loading report overview

Server metadata

Loading server metadata

Discoverability

Loading discoverability

Protocol

Loading protocol

Tools

Loading tools

MCP Apps

Loading mcp apps

Tool documentation quality

Loading tool documentation quality

Title99/100

Update listing

The title clearly communicates the tool’s action and subject. Keep it concise.

Description92/100

The description explains the capability, when to use it, and what to expect.

Inputs50/100

7 of 11 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

slug

Listing slug, e.g. northstar-deploys

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

name

Product name

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

website_url

Product website on its own root domain (subdomains like app.example.com or x.vercel.app are rejected). One listing per domain: re-submitting a URL on your listed domain updates your listing.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

tagline

One-line pitch

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

description

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_listing",
  "title": "Update listing",
  "description": "Edit one of your listings in place by slug. Use this to change website_url (for example to add utm_* parameters) without creating a new listing; slug, status, and owner stay the same. Omitted fields are left unchanged; send an empty string or array to clear an optional field.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "name": {
        "type": "string",
        "maxLength": 80,
        "description": "Product name"
      },
      "slug": {
        "type": "string",
        "description": "Listing slug, e.g. northstar-deploys"
      },
      "api_key": {
        "type": "string",
        "description": "AZN8 API key (azn8_…). Optional when the MCP connection already sends Authorization: Bearer <api_key>."
      },
      "tagline": {
        "type": "string",
        "maxLength": 160,
        "description": "One-line pitch"
      },
      "features": {
        "type": "array",
        "items": {
          "type": "string",
          "maxLength": 120
        },
        "maxItems": 8
      },
      "cta_label": {
        "type": "string",
        "maxLength": 40,
        "description": "Button text"
      },
      "categories": {
        "type": "array",
        "items": {
          "enum": [
            "saas",
            "developer-tools",
            "productivity",
            "marketing",
            "ai",
            "domains",
            "marketplace",
            "analytics",
            "design",
            "sales",
            "customer-support",
            "finance",
            "education",
            "security",
            "no-code",
            "other"
          ],
          "type": "string"
        },
        "maxItems": 5
      },
      "description": {
        "type": "string",
        "maxLength": 4000
      },
      "website_url": {
        "type": "string",
        "maxLength": 500,
        "description": "Product website on its own root domain (subdomains like app.example.com or x.vercel.app are rejected). One listing per domain: re-submitting a URL on your listed domain updates your listing."
      },
      "pricing_model": {
        "enum": [
          "free",
          "freemium",
          "subscription",
          "one-time",
          "usage",
          "contact"
        ],
        "type": "string"
      },
      "pricing_summary": {
        "type": "string",
        "maxLength": 80,
        "description": "Public price line, e.g. \"From $39/mo\""
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

Manufact

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool docsTool documentation quality

Title94/100

Description90/100

Inputs17/100

Annotations50/100

Output schema0/100

Title98/100

Description78/100

Inputs91/100

Annotations50/100

Output schema0/100

Title99/100

Description92/100

Inputs19/100

Annotations100/100

Output schema0/100

Title96/100

Description97/100

Inputs53/100

Annotations100/100

Output schema0/100

Title99/100

Description92/100

Inputs50/100

Annotations100/100

Output schema0/100

Title98/100

Description79/100

Inputs99/100

Annotations50/100

Output schema0/100

Title95/100

Description84/100

Inputs25/100

Annotations100/100

Output schema0/100

Title89/100

Description94/100

Inputs33/100

Annotations100/100

Output schema0/100

Put your MCP to the test

Overview

Related MCP servers

FAQ

Not your MCP?

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool documentation quality

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool docsTool documentation quality

Title94/100

Description90/100

Inputs17/100

Annotations50/100

Output schema0/100

Title98/100

Description78/100

Inputs91/100

Annotations50/100

Output schema0/100

Title99/100

Description92/100

Inputs19/100

Annotations100/100

Output schema0/100

Title96/100

Tool documentation quality

Tool documentation quality