Skip to content

BACKLNK MCP server

com.backlnk/backlnkbacklnk.comstreamable-httpv1.0.4Scanned

Free technical SEO, AEO, LLMO and GEO checks for AI agents: check a page, fix it, verify the fix.

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BACKLNK MCP server can do

The BACKLNK MCP server is published by backlnk.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: run_checks, verify_fixes, ai_crawler_policy and usage), but cannot delete data. 2 tools only read.

3 tools bring in text other people can write (run_checks, get_report and verify_fixes); 1 tool can send data out of your system (run_checks).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 1.0.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 4Claude Code: ask
  • ai_crawler_policyBuilds robots.txt lines that allow or block AI crawlers from BACKLNK's reviewed crawler catalog, with what each line does and warnings.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: AI crawler robots.txt rules
    • readOnlyHint: true
    • openWorldHint: false
  • run_checksRuns BACKLNK checks on one public URL and waits up to about 40 seconds.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "run_checks" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "run_checks" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":true}; The name "run_checks" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a page
    • readOnlyHint: true
    • idempotentHint: false
    • openWorldHint: true
  • usageHow many checks this API key has used and has left today and this hour.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How many checks this API key has used and has left today and this hour.

    Annotations the server declares

    • title: API key usage
    • readOnlyHint: true
    • openWorldHint: false
  • verify_fixesAfter 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, s…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Verify fixes
    • readOnlyHint: true
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_reportReturns the compact report of an earlier check: state, summary, counts and findings (detail "actions": issues and warnings only, the default; "all": every finding).Reads text others writeNo findings

    Why it is in this group

    • The name "get_report" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Returns the compact report of an earlier check: state, summary, counts and findings (detail "actions": issues and warnings only, the default; "all": every finding).

    Annotations the server declares

    • title: Get a check's report
    • readOnlyHint: true
    • openWorldHint: false
  • list_checksLists every check BACKLNK can run (id, what it looks at, its scope and limits).No findings

    Why it is in this group

    • The name "list_checks" says "list": a word for reading.
    Description, as the server wrote it
    Lists every check BACKLNK can run (id, what it looks at, its scope and limits). Use the ids with run_checks.

    Annotations the server declares

    • title: List BACKLNK checks
    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://backlnk.com/mcp: tools/list returned 6 tools to an anonymous client, including run_checks (write), verify_fixes (write), ai_crawler_policy (write), usage (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "run_checks" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":true}; The name "run_checks" says "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 changed.~6 changedView diff

Install

Pinned to version 1.0.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http backlnk https://backlnk.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http backlnk https://backlnk.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__backlnk__list_checks",
      "mcp__backlnk__get_report"
    ],
    "ask": [
      "mcp__backlnk__run_checks",
      "mcp__backlnk__verify_fixes",
      "mcp__backlnk__ai_crawler_policy",
      "mcp__backlnk__usage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as backlnk. Review it before you use it.

Capability tags behind 3 rules
  • mcp__backlnk__run_checks untrusted-input, outbound
  • mcp__backlnk__get_report untrusted-input
  • mcp__backlnk__verify_fixes untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.backlnk/backlnk/verify?hash=fc9c8fae626e6d526fcf767543be8375213fd0ec386e5f34fd11e5a6f5f26a64" | jq -e '.changed == false'

Pinned hash fc9c8fae626e, from Nov 8, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.backlnk/backlnk/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.backlnk/backlnk
[![Anlyon Radar](https://radar.anlyon.com/badge/com.backlnk/backlnk.svg)](https://radar.anlyon.com/servers/com.backlnk/backlnk)

Source: MCP Registry · repository. Synced Nov 8, 2026, 20:17 UTC.

BACKLNK MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BACKLNK MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BACKLNK MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BACKLNK MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BACKLNK MCP server have?

6 tools: 4 write, 2 read. run_checks, verify_fixes, ai_crawler_policy, usage, list_checks and get_report.

Does the BACKLNK MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BACKLNK MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): run_checks.

Has the BACKLNK MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.