_ registry / mcp streamable-http · checked 27m ago

backlnk

https://backlnk.com

Registry code: cbfc1e31aa0cb43c

api record

Backlnk runs evidence-based technical SEO and AI-visibility checks on public web pages and reports what it measured.

Work in a loop: (1) run_checks on the page's public URL: you get the issues and warnings, most important first, each with evidence and a recommendation. (2) Fix them in the codebase, starting with the first findings. Changes are only visible to the checks once they are deployed to that public URL. (3) verify_fixes with each audit_id: it re-runs the same check fresh and reports what is fixed, new, still open or not re-checked.

endpoint
https://backlnk.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 backlnk live?
Yes — it answered the hub's last check (checked 27m ago). It answered 100% of checks over the last 30 days.
Is backlnk free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does backlnk have?
6 tools: run_checks, ai_crawler_policy, list_checks, usage, get_report, verify_fixes.
Is backlnk 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
176ms

last good check

priced tools
0

of 6 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 6 tools
6 auth-required 6 of 6 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.

  • run_checks auth-required never probed

    Runs Backlnk checks on one public URL and waits up to about 40 seconds. Returns, per check, its state, summary, counts and the issues and warnings to fix (most important first, with evidence and a recommendation), plus the audit ids for get_report and verify_fixes. Default checks: meta-tags, page-structure, ai-crawler-access, redirects-headers, entity-schema.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Public page or website URL, e.g. https://example.com/pricing"
    },
    "mode": {
      "enum": [
        "Source",
        "Rendered",
        "Auto"
      ],
      "type": "string",
      "description": "Source reads the HTML as served; Rendered runs JavaScript first; Auto decides per page."
    },
    "fresh": {
      "type": "boolean",
      "description": "Re-run even if the same check ran on this URL very recently (default false)."
    },
    "checks": {
      "type": "array",
      "items": {
        "enum": [
          "llms-txt-generate",
          "llms-txt-validate",
          "entity-schema",
          "answer-snippets",
          "sitemap-hygiene",
          "intent-focus",
          "internal-links",
          "page-structure",
          "ai-crawler-access",
          "meta-tags",
          "redirects-headers",
          "indexability",
          "hreflang",
          "duplicate-content",
          "image-seo",
          "page-speed"
        ],
        "type": "string"
      },
      "maxItems": 20,
      "minItems": 1,
      "description": "Check ids (see list_checks). Omit for the quick default set."
    }
  },
  "additionalProperties": false
}
    arguments 53 lines
  • ai_crawler_policy auth-required 27m ago

    Builds robots.txt lines that allow or block AI crawlers from Backlnk's reviewed crawler catalog, with what each line does and warnings. Use a preset (block-training: Block AI training, stay in AI search; block-ai: Block AI crawlers, keep search engines; allow-all: Allow every crawler) or decide per purpose and per crawler token.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "preset": {
      "enum": [
        "block-training",
        "block-ai",
        "allow-all"
      ],
      "type": "string"
    },
    "crawlers": {
      "type": "object",
      "description": "Per-crawler overrides by token, e.g. { \"GPTBot\": \"allow\" }.",
      "additionalProperties": {
        "enum": [
          "allow",
          "block"
        ],
        "type": "string"
      }
    },
    "purposes": {
      "type": "object",
      "properties": {
        "dataset": {
          "enum": [
            "allow",
            "block"
          ],
          "type": "string",
          "description": "Open crawl archives that anyone, including AI developers, can download and analyse."
        },
        "ai-search": {
          "enum": [
            "allow",
            "block"
          ],
          "type": "string",
          "description": "Crawlers that let AI assistants and AI search find, cite and link your pages."
        },
        "user-fetch": {
          "enum": [
            "allow",
            "block"
          ],
          "type": "string",
          "description": "Visits made when a person asks an assistant about a page or shares a link."
        },
        "ai-training": {
          "enum": [
            "allow",
            "block"
          ],
          "type": "string",
          "description": "Crawlers and control tokens that decide whether your content may be used to train AI models."
        },
        "search-engine": {
          "enum": [
            "allow",
            "block"
          ],
          "type": "string",
          "description": "Classic web search crawlers. Blocking one takes your site out of that search engine."
        }
      },
      "description": "Decision per purpose; purposes not named stay allowed when no preset is given.",
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}
    arguments 72 lines
  • list_checks auth-required 27m ago

    Lists every check Backlnk can run (id, what it looks at, its scope and limits). Use the ids with run_checks.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • usage auth-required 27m ago

    How many checks this API key has used and has left today and this hour.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_report auth-required never probed

    Returns the compact report of an earlier check: state, summary, counts and findings (detail "actions": issues and warnings only, the default; "all": every finding).

    mcp-tool

    {
  "type": "object",
  "required": [
    "audit_id"
  ],
  "properties": {
    "detail": {
      "enum": [
        "actions",
        "all"
      ],
      "type": "string",
      "description": "Default \"actions\"."
    },
    "audit_id": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Audit id returned by run_checks (a UUID)."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • verify_fixes auth-required never probed

    After the fixes are deployed: re-runs the same check fresh on the same URL and options, waits up to about 40 seconds and returns the comparison with the original run: fixed, new, still open and not re-checked findings.

    mcp-tool

    {
  "type": "object",
  "required": [
    "audit_id"
  ],
  "properties": {
    "audit_id": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Audit id returned by run_checks (a UUID)."
    }
  },
  "additionalProperties": false
}
    arguments 14 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 cbfc1e31aa0cb43c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cbfc1e31aa0cb43c/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/cbfc1e31aa0cb43c/badge.svg)](https://brick.blue/agent/cbfc1e31aa0cb43c?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
100%

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.