_ registry / mcp streamable-http · checked 1h ago

com.linkbreakers/docs-mcp

https://linkbreakers.com

Registry code: 5d81eb0a3893f66e

api record

Read-only access to the public Linkbreakers website: help center articles, guides, pricing and QR code templates. Start with search_docs, then call get_article with a result slug to read the full Markdown. To act on a Linkbreakers workspace (create links, read analytics), use the authenticated product server at https://mcp.linkbreakers.com instead.

endpoint
https://linkbreakers.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is com.linkbreakers/docs-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is com.linkbreakers/docs-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.linkbreakers/docs-mcp have?
5 tools: get_pricing, search_docs, get_article, list_features, list_qr_templates.
Is com.linkbreakers/docs-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
602ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_features open 1h ago

    List the product features included in every Linkbreakers plan, each with a short description and the help article that explains it.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_qr_templates open 1h ago

    List public Linkbreakers QR code design templates, optionally filtered by a search term. Each result links to its template page.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum number of templates"
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "description": "Optional search term, for example restaurant or wedding"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_pricing unknown never probed

    Return the current Linkbreakers plans with prices in USD per month, plan limits, signup links and how to reach sales for Enterprise.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "billing_cycle": {
          "enum": [
            "yearly",
            "monthly"
          ],
          "type": "string",
          "description": "Billing cycle to price the plans with. Omit to get both."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • search_docs unknown never probed

    Search the Linkbreakers help center, guides, integrations and product news. Returns ranked articles with their URL, Markdown URL, category and a snippet.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum number of results"
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Natural language question or keywords"
        },
        "category": {
          "enum": [
            "overview",
            "use-cases",
            "dashboard",
            "developer",
            "legal",
            "workflow",
            "guides",
            "alternatives",
            "research",
            "partnerships",
            "integrations",
            "news"
          ],
          "type": "string",
          "description": "Restrict results to one help center category"
        }
      },
      "additionalProperties": false
    }
    arguments 40 lines
  • get_article unknown 1h ago

    Return the full Markdown of a Linkbreakers help center article by slug (the last segment of https://linkbreakers.com/help/article/<slug>).

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "pattern": "^[a-z0-9-]+$",
          "maxLength": 200,
          "minLength": 1,
          "description": "Article slug"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5d81eb0a3893f66e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5d81eb0a3893f66e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5d81eb0a3893f66e/badge.svg)](https://brick.blue/agent/5d81eb0a3893f66e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on linkbreakers.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.