AEO Backlink
REMOTE · AEO.ADVANCELABS.DEV
Find brand mentions, link prospects and competitor link sources, and draft outreach. Read-only.
Available components
Last scanned (8 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 665 tokens (~95/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool “find_competitor_link_sources” rewrote its description, which is the text the model reads security
- Tool “find_mentions” rewrote its description, which is the text the model reads security
- Tool “find_prospects” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://aeo.advancelabs.dev/api/mcp/backlink/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.advancelabs.dev | CN=YR1,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | RSA 2048 | SHA256-RSA | 5bdd6e4439c5b08c6e07ab86c710c52d0e5 |
| SANs: *.advancelabs.dev, advancelabs.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aeo.advancelabs.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| advancelabs.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aeo.advancelabs.dev/api/mcp/backlink/mcp | Verified | 200 | |
| http (plaintext) | http://aeo.advancelabs.dev/api/mcp/backlink/mcp | HTTPS enforced | 308 | https://aeo.advancelabs.dev/api/mcp/backlink/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_page_history Check page history ~72
Return a Wayback Machine timeline for a URL: total snapshots, first/last archived dates, and a bounded list of snapshot records with direct archive links.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max snapshots to return (default 50). |
| url | string | yes | The URL to look up in the Wayback Machine. |
No output schema declared.
No examples provided.
extract_contact_info Extract contact info ~62
Fetch a page and extract contact emails (including de-obfuscated and mailto links) and social media handles (Twitter/X, LinkedIn, Facebook, Instagram, GitHub, YouTube).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page URL to extract contact info from. |
No output schema declared.
No examples provided.
find_competitor_link_sources Find competitor link sources ~100
Approximate the pages linking to a competitor using free web-search signals (domain mentions and brand mentions). De-duplicates by host and excludes the competitor's own domain. Not a complete backlink index — a free, directional starting point for prospecting.
| Name | Type | Req | Description |
|---|---|---|---|
| competitorUrl | string | yes | Competitor's URL or domain (e.g. https://competitor.com or competitor.com). |
| limit | integer | – | Max sources (default 20). |
No output schema declared.
No examples provided.
find_mentions Find brand mentions ~113
Find linked and unlinked mentions of a brand across the web via web search results. When a domain is supplied, classifies each mention as linked (on the brand domain) or unlinked (a third-party page — a potential backlink opportunity).
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand or product name to search mentions for. |
| domain | string | – | The brand's own domain (e.g. acme.com) — used to classify linked vs unlinked. |
| limit | integer | – | Max results (default 20). |
No output schema declared.
No examples provided.
find_prospects Find link prospects ~75
Find guest-post, resource-page, and roundup link-building prospects for a topic by running classic outreach footprints through web search and merging the results by host.
| Name | Type | Req | Description |
|---|---|---|---|
| limitPerAngle | integer | – | Max results per outreach angle (default 8). |
| topic | string | yes | Niche or topic to find link-building prospects for. |
No output schema declared.
No examples provided.
generate_outreach_email Generate outreach email ~164
Draft a short, personalized cold outreach email from a contact + context object using your own LLM key (BYOK). Returns a subject line and body. The API key is request-scoped and is never persisted or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | BYOK API key — request-scoped, never persisted or logged. |
| contact | object | yes | The recipient. All fields optional; more detail yields better personalization. |
| context | object | yes | The outreach angle and sender context. |
| maxTokens | integer | – | – |
| model | string | yes | Model id (e.g. claude-sonnet-4-20250514). |
| provider | string | yes | LLM provider for @advance-labs/llm. |
| temperature | number | – | – |
No output schema declared.
No examples provided.
verify_page_links Verify page links ~79
Fetch a page and confirm whether it contains a link to the target domain, reporting anchor text and rel attributes (nofollow/sponsored/ugc) and whether the link is dofollow.
| Name | Type | Req | Description |
|---|---|---|---|
| targetDomain | string | yes | The domain the link should point to (e.g. yoursite.com). |
| url | string | yes | The page URL to inspect. |
No output schema declared.
No examples provided.
How do I install the AEO Backlink MCP server?
AEO Backlink is a hosted endpoint at https://aeo.advancelabs.dev/api/mcp/backlink/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · aeo.advancelabs.dev
claude mcp add --transport http dev-advancelabs-aeo-backlink 'https://aeo.advancelabs.dev/api/mcp/backlink/mcp'
What is the AEO Backlink MCP server?
AEO Backlink is an MCP server listed in the public MCP registry as dev.advancelabs/aeo-backlink. Find brand mentions, link prospects and competitor link sources, and draft outreach. Read-only. This page covers its hosted endpoint (https://aeo.advancelabs.dev/api/mcp/backlink/mcp).
Is the AEO Backlink MCP server safe to use?
AEO Backlink scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AEO Backlink MCP server expose?
AEO Backlink exposes 7 tools: find_mentions, find_prospects, find_competitor_link_sources, verify_page_links, extract_contact_info, and 2 more. Their descriptions and schemas cost roughly 665 tokens of context every time the server is loaded.
Does the AEO Backlink MCP server require authentication?
No. We connected to AEO Backlink without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AEO Backlink MCP server still maintained?
AEO Backlink is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the AEO Backlink MCP server?
VerifyMCP ran 13 checks on AEO Backlink, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.