Manufact

LeaderboardBack to leaderboard

rdyrct

rdyrct.com/api/mcp

View checks

Protocol: MCP 2025-11-25
Server version: 1.0.0
Supports: Tools

Overall score

How is this score calculated?

Last reviewed at Nov 11, 2026, 21:36:33 UTC

Server metadata

Warnings30/100

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

Stable server name

rdyrct

10/10Source

Human-readable title

Add a human-readable title for clients and directories.

0/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

Add concise instructions that explain how an agent should use the server.

0/20Source

Declared capabilities

Supports Tools.

10/10Source

Discoverability

0/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.

No matching mcp.json manifest or MCP Server Card was found at the checked URLs.

Not foundSource

Setup instructions at MCP URL

The MCP endpoint requires authentication instead of publishing public setup instructions (HTTP 401).

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

9 tool(s) returned

Source

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 1083ms

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Issues78/100

Tool definitions, annotations, and client compatibility.

All tools have descriptions

All tools have non-empty descriptions

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

Claude Code metadata fits its 2 KB fields

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

Source

All tools have OpenAI behavior hints

27 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

Claude tool names are within 64 characters

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

Source

Cursor tool-name budget advisory

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

Observed behavior

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

All tools have a display title

9 tool(s) missing a display title: create_link, update_link, delete_link, list_links, get_link_stats, get_org_stats, get_plan_usage, invite_member, generate_qr_code

How to fix: Set the top-level tool.title to a short human-readable label (for example, "Search catalog"). Claude directory submission requires tool titles; annotations.title remains accepted only as a legacy fallback.

errorClaude.ai

Source

Claude tools declare applicable behavior hints

9 Claude behavior annotation issue(s) found

How to fix: For Claude directory submission, declare the applicable annotations.readOnlyHint or annotations.destructiveHint value as a boolean on every tool.

errorClaude.ai

Source

Tool names use valid characters

All tool names use valid characters

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

ChatGPT tool names are unique

All tool names are unique

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

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

MCP Apps

Not applicableOptional

App resources, metadata, and rendering requirements.

All discovered view resources were inspected

No view resources found — view checks skipped

Source

View resource metadata complete

No view resources found — view checks skipped

Source

View resources declare a domain

No view resources found — view checks skipped

Source

View resource envelope is valid

No view resources found — view checks skipped

Tool invocation metadata present

No view resources found — view checks skipped

Source

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

Views do not request nested iframe domains

No view resources found — view checks skipped

Source

Tool visibility metadata is valid

No view resources found — view checks skipped

Source

Tool documentation quality

45/100

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

create_linkTitles 76Descriptions 78Inputs 77Annotations 0Outputs 062/100

create_link

Title76/100

Not provided

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

Description78/100

Shorten a URL into an rdyrct link. Returns the short link and its destination.

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

Inputs77/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

destination

The URL to shorten

Clear enough to supply this argument.

slug

A chosen slug, custom domains only. Omit for random.

Clear enough to supply this argument.

title

An optional label for the link

Clear enough to supply this argument.

domain

Put it on this custom domain instead of the shared one

Clear enough to supply this argument.

org_id

Which organization, if the person has more than one

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations0/100

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

Not declared

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": "create_link",
  "description": "Shorten a URL into an rdyrct link. Returns the short link and its destination.",
  "inputSchema": {
    "type": "object",
    "required": [
      "destination"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "A chosen slug, custom domains only. Omit for random."
      },
      "title": {
        "type": "string",
        "description": "An optional label for the link"
      },
      "domain": {
        "type": "string",
        "description": "Put it on this custom domain instead of the shared one"
      },
      "org_id": {
        "type": "string",
        "description": "Which organization, if the person has more than one"
      },
      "destination": {
        "type": "string",
        "description": "The URL to shorten"
      }
    }
  }
}

update_linkTitles 75Descriptions 77Inputs 58Annotations 0Outputs 056/100

update_link

Title75/100

Not provided

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

Description77/100

Point an existing link at a new destination, or rename its title. Find it by slug (e.g. "promo") or by its current destination URL.

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

Inputs58/100

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

slug

The link's slug, e.g. "promo"

Clear enough to supply this argument.

destination

The link's current destination, to find it by

Clear enough to supply this argument.

new_destination

The new destination URL

Clear enough to supply this argument.

title

Not provided

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

org_id

Not provided

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

Annotations0/100

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

Not declared

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_link",
  "description": "Point an existing link at a new destination, or rename its title. Find it by slug (e.g. \"promo\") or by its current destination URL.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "description": "The link's slug, e.g. \"promo\""
      },
      "title": {
        "type": "string"
      },
      "org_id": {
        "type": "string"
      },
      "destination": {
        "type": "string",
        "description": "The link's current destination, to find it by"
      },
      "new_destination": {
        "type": "string",
        "description": "The new destination URL"
      }
    }
  }
}

delete_linkTitles 57Descriptions 71Inputs 25Annotations 0Outputs 041/100

delete_link

Title57/100

Not provided

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

Description71/100

Delete a link. Find it by slug or by the destination URL it points to.

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

Inputs25/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.

destination

The destination URL it points to

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

org_id

Not provided

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

Annotations0/100

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

Not declared

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": "delete_link",
  "description": "Delete a link. Find it by slug or by the destination URL it points to.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string"
      },
      "org_id": {
        "type": "string"
      },
      "destination": {
        "type": "string",
        "description": "The destination URL it points to"
      }
    }
  }
}

list_linksTitles 60Descriptions 69Inputs 38Annotations 0Outputs 045/100

list_links

Title60/100

Not provided

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

Description69/100

Search or list an organization's links, with their click counts.

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

Inputs38/100

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

query

Filter by slug, destination or title

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

org_id

Not provided

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

Annotations0/100

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

Not declared

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_links",
  "description": "Search or list an organization's links, with their click counts.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Filter by slug, destination or title"
      },
      "org_id": {
        "type": "string"
      }
    }
  }
}

get_link_statsTitles 60Descriptions 74Inputs 50Annotations 0Outputs 049/100

get_link_stats

Title60/100

Not provided

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

Description74/100

How many clicks one link has gotten, and where from: countries, referrers and devices.

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

Inputs50/100

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

slug

The link's slug, e.g. "promo"

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

domain

Its custom domain, if not on the shared domain

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

org_id

Not provided

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

Annotations0/100

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

Not declared

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_link_stats",
  "description": "How many clicks one link has gotten, and where from: countries, referrers and devices.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "The link's slug, e.g. \"promo\""
      },
      "domain": {
        "type": "string",
        "description": "Its custom domain, if not on the shared domain"
      },
      "org_id": {
        "type": "string"
      }
    }
  }
}

get_org_statsTitles 52Descriptions 78Inputs 38Annotations 0Outputs 045/100

get_org_stats

Title52/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description78/100

An organization's links overall: total and recent clicks, the top-performing links, and links with no clicks in the last 30 days.

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

Inputs38/100

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

days

The analytics window, in days. Defaults to 7.

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

org_id

Not provided

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

Annotations0/100

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

Not declared

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_org_stats",
  "description": "An organization's links overall: total and recent clicks, the top-performing links, and links with no clicks in the last 30 days.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "days": {
        "type": "integer",
        "description": "The analytics window, in days. Defaults to 7."
      },
      "org_id": {
        "type": "string"
      }
    }
  }
}

get_plan_usageTitles 54Descriptions 73Inputs 0Annotations 0Outputs 034/100

get_plan_usage

Title54/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description73/100

How many links the organization is allowed on its current plan, and how many are left.

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

Inputs0/100

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

org_id

Not provided

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

Annotations0/100

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

Not declared

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_plan_usage",
  "description": "How many links the organization is allowed on its current plan, and how many are left.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "org_id": {
        "type": "string"
      }
    }
  }
}

invite_memberTitles 39Descriptions 68Inputs 25Annotations 0Outputs 035/100

invite_member

Title39/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description68/100

Invite someone to an organization by email.

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

Inputs25/100

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

Not provided

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

role

Defaults to member

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

org_id

Not provided

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

Annotations0/100

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

Not declared

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": "invite_member",
  "description": "Invite someone to an organization by email.",
  "inputSchema": {
    "type": "object",
    "required": [
      "email"
    ],
    "properties": {
      "role": {
        "enum": [
          "viewer",
          "member",
          "admin"
        ],
        "type": "string",
        "description": "Defaults to member"
      },
      "email": {
        "type": "string"
      },
      "org_id": {
        "type": "string"
      }
    }
  }
}

generate_qr_codeTitles 47Descriptions 85Inputs 0Annotations 0Outputs 035/100

generate_qr_code

Title47/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description85/100

Make a QR code for a URL. Returns a PNG image.

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

Inputs0/100

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

url

Not provided

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

Annotations0/100

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

Not declared

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": "generate_qr_code",
  "description": "Make a QR code for a URL. Returns a PNG image.",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string"
      }
    }
  }
}

Put your MCP to the test

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

01Get link statsHow many clicks one link has gotten, and where from: countries, referrers and devices.
02Make a QR code for a URL
03Get org statsAn organization's links overall: total and recent clicks, the top-performing links, and links with no clicks in the last 30 days.
04List linksSearch or list an organization's links, with their click counts.
05Get plan usageHow many links the organization is allowed on its current plan, and how many are left.

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

Test your MCP in Cloud Book a test call

Overview

Category: Marketing & SEO

FAQ

rdyrct setup, tools, quality score, publishing readiness, and alternatives.

How do I add rdyrct to Claude, ChatGPT, or Cursor?

Add rdyrct 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://rdyrct.com/api/mcp.

Is rdyrct MCP ready for ChatGPT and Claude?

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

How clear is rdyrct's MCP tool documentation?

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

What are the best alternatives to rdyrct?

As of November 12, 2026, alternatives to rdyrct in marketing-seo on the Manufact MCP leaderboard include BulkPublish, Fuxux, Refluenced, The Prompting Company MCP, and Buzzmark.

How can rdyrct improve its MCP documentation?

get_plan_usage is the lowest-scoring reviewed tool at 34/100. 0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values. 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

Title76/100

Not provided

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

Description78/100

Shorten a URL into an rdyrct link. Returns the short link and its destination.

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

Inputs77/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

destination

The URL to shorten

Clear enough to supply this argument.

slug

A chosen slug, custom domains only. Omit for random.

Clear enough to supply this argument.

title

An optional label for the link

Clear enough to supply this argument.

domain

Put it on this custom domain instead of the shared one

Clear enough to supply this argument.

org_id

Which organization, if the person has more than one

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations0/100

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

Not declared

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": "create_link",
  "description": "Shorten a URL into an rdyrct link. Returns the short link and its destination.",
  "inputSchema": {
    "type": "object",
    "required": [
      "destination"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "A chosen slug, custom domains only. Omit for random."
      },
      "title": {
        "type": "string",
        "description": "An optional label for the link"
      },
      "domain": {
        "type": "string",
        "description": "Put it on this custom domain instead of the shared one"
      },
      "org_id": {
        "type": "string",
        "description": "Which organization, if the person has more than one"
      },
      "destination": {
        "type": "string",
        "description": "The URL to shorten"
      }
    }
  }
}

Manufact

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool docsTool documentation quality

Title76/100

Description78/100

Inputs77/100

Annotations0/100

Output schema0/100

Title75/100

Description77/100

Inputs58/100

Annotations0/100

Output schema0/100

Title57/100

Description71/100

Inputs25/100

Annotations0/100

Output schema0/100

Title60/100

Description69/100

Inputs38/100

Annotations0/100

Output schema0/100

Title60/100

Description74/100

Inputs50/100

Annotations0/100

Output schema0/100

Title52/100

Description78/100

Inputs38/100

Annotations0/100

Output schema0/100

Title54/100

Description73/100

Inputs0/100

Annotations0/100

Output schema0/100

Title39/100

Description68/100

Inputs25/100

Annotations0/100

Output schema0/100

Title47/100

Description85/100

Inputs0/100

Annotations0/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

Title76/100

Description78/100

Inputs77/100

Annotations0/100

Output schema0/100

Title75/100

Description77/100

Inputs58/100

Annotations0/100

Output schema0/100

Title57/100

Tool documentation quality

Tool documentation quality