# com.handsofflinks/link-followability (remote · handsofflinks-mcp.lipmichal.workers.dev)

Check if a link on a live page is followable: rel tokens, meta robots and X-Robots-Tag

- Trust score: 57/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-09

## Components

- remote · `handsofflinks-mcp.lipmichal.workers.dev`: 57/100 (this document), [markdown](https://verifymcp.io/servers/com-handsofflinks-link-followability/handsofflinks-mcp.md), [page](https://verifymcp.io/servers/com-handsofflinks-link-followability/handsofflinks-mcp)

## Channel facts

- Endpoint: `https://handsofflinks-mcp.lipmichal.workers.dev`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-09.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 236 tokens (~236/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http com-handsofflinks-link-followability https://handsofflinks-mcp.lipmichal.workers.dev/
```

### Codex

```toml
[mcp_servers.com-handsofflinks-link-followability]
url = "https://handsofflinks-mcp.lipmichal.workers.dev/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-handsofflinks-link-followability": {
      "type": "remote",
      "url": "https://handsofflinks-mcp.lipmichal.workers.dev/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-handsofflinks-link-followability --url https://handsofflinks-mcp.lipmichal.workers.dev/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-handsofflinks-link-followability:
    url: "https://handsofflinks-mcp.lipmichal.workers.dev/"
```

### Other

```json
{
  "mcpServers": {
    "com-handsofflinks-link-followability": {
      "type": "http",
      "url": "https://handsofflinks-mcp.lipmichal.workers.dev/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-09 (score 57)

First indexed and scored.

## MCP tools (1)

### `check_link_followability` (~194 tokens)

Check whether a link on a page is followable

Fetch a live web page and decide whether a link on it is followable by a crawler. Combines the X-Robots-Tag response header, the robots/user-agent meta tags, and the anchor's own rel tokens (nofollow, ugc, sponsored), with the most restrictive signal winning. Returns a verdict per matching anchor plus the exact reasons it was blocked. Use it to verify a backlink you were promised is actually followable.

Input parameters:

- `page_url` (string, required): Absolute http(s) URL of the page that contains the link.
- `target` (string): Optional. Only report anchors whose href (raw or resolved) contains this string, or whose host equals it. Omit to evaluate every anchor on the page.
- `user_agent` (string): Optional crawler name to evaluate for, e.g. 'googlebot'. Directives addressed to another named agent are then ignored. Defaults to the wildcard agent.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-handsofflinks-link-followability/handsofflinks-mcp#diagnostics

## Score history

- 2026-08-09: 57

## Links

- Remote endpoint: https://handsofflinks-mcp.lipmichal.workers.dev/
- Website: https://handsofflinks.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-handsofflinks-link-followability/handsofflinks-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-handsofflinks-link-followability/handsofflinks-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-handsofflinks-link-followability/handsofflinks-mcp