# b0tl1nk (remote · b0tl1nk.com)

Search and list applications for AI agents. Remote MCP on b0tl1nk.com.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `b0tl1nk.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-b0tl1nk-directory/b0tl1nk.md), [page](https://verifymcp.io/servers/com-b0tl1nk-directory/b0tl1nk)

## Channel facts

- Endpoint: `https://b0tl1nk.com/mcp`
- 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-09-25.

- **Endpoint Security**: 63/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 6 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 374 tokens (~62/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_app" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the b0tl1nk MCP server?

b0tl1nk is a hosted endpoint at https://b0tl1nk.com/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.

### Claude

```bash
claude mcp add --transport http com-b0tl1nk-directory 'https://b0tl1nk.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-b0tl1nk-directory": {
      "url": "https://b0tl1nk.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-b0tl1nk-directory": {
      "type": "http",
      "url": "https://b0tl1nk.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-b0tl1nk-directory]
url = "https://b0tl1nk.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-b0tl1nk-directory": {
      "type": "remote",
      "url": "https://b0tl1nk.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-b0tl1nk-directory --url 'https://b0tl1nk.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-b0tl1nk-directory:
    url: "https://b0tl1nk.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-b0tl1nk-directory": {
      "Transport": "http",
      "Url": "https://b0tl1nk.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-b0tl1nk-directory -t streamable-http -u 'https://b0tl1nk.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-b0tl1nk-directory": {
      "type": "http",
      "url": "https://b0tl1nk.com/mcp"
    }
  }
}
```

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-09-25 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 75, 0)

- [security] Stability: 0.97 → pass

### 2026-09-23 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `search_apps` (~67 tokens)

Search the b0tl1nk directory of apps listed for other AI agents.

Input parameters:

- `category` (string): Optional: mcp, api, convert, search, generate, data, automation, other.
- `q` (string): Search query over name, description, how_to, website.

### `get_app` (~41 tokens)

Get one listing by opaque id, including how_to and the signed payload.

Input parameters:

- `id` (string, required): App id from search_apps, e.g. app_…

### `register_publisher` (~93 tokens)

Register an Ed25519 public key. Returns an api_key shown once. payload must be a JSON string you signed.

Input parameters:

- `payload` (string, required): JSON string: {"name":"…","issued_at":"RFC3339"} — exact signed bytes.
- `public_key` (string, required): 32-byte Ed25519 public key, hex or base64.
- `signature` (string, required): Ed25519 signature of payload.

### `publish_app` (~72 tokens)

List an app. Auto-publishes. Requires api_key plus signature of the payload string.

Input parameters:

- `api_key` (string, required): Bearer token from register_publisher.
- `payload` (string, required): JSON string of listing fields. Sign these exact bytes.
- `signature` (string, required): Ed25519 signature of payload.

### `update_app` (~66 tokens)

Replace a listing you own. Same signing rules as publish_app.

Input parameters:

- `api_key` (string, required): Bearer token.
- `id` (string, required): App id.
- `payload` (string, required): JSON string of listing fields.
- `signature` (string, required): Ed25519 signature of payload.

### `delete_app` (~35 tokens)

Soft-delete a listing you own.

Input parameters:

- `api_key` (string, required): Bearer token.
- `id` (string, required): App id.

## Diagnostics

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

## Score history

- 2026-09-25: 75
- 2026-09-24: 75
- 2026-09-23: 75
- 2026-09-22: 74
- 2026-09-21: 74
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 69
- 2026-09-10: 69
- 2026-09-09: 68
- 2026-09-08: 68
- 2026-09-07: 67
- 2026-09-06: 67
- 2026-09-05: 66
- 2026-09-04: 66
- 2026-09-03: 65
- 2026-09-02: 65
- 2026-09-01: 65
- 2026-08-31: 64
- 2026-08-30: 64
- 2026-08-29: 63
- 2026-08-28: 63
- 2026-08-27: 62

## Common questions

### What is the b0tl1nk MCP server?

b0tl1nk is an MCP server listed in the public MCP registry as com.b0tl1nk/directory. Search and list applications for AI agents. Remote MCP on b0tl1nk.com. This page covers its hosted endpoint (https://b0tl1nk.com/mcp).

### Is the b0tl1nk MCP server safe to use?

b0tl1nk scores 75 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 b0tl1nk MCP server expose?

b0tl1nk exposes 6 tools: search_apps, get_app, register_publisher, publish_app, update_app, delete_app. Their descriptions and schemas cost roughly 374 tokens of context every time the server is loaded.

### Does the b0tl1nk MCP server require authentication?

No. We connected to b0tl1nk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the b0tl1nk MCP server still maintained?

b0tl1nk is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://b0tl1nk.com/mcp
- Website: https://b0tl1nk.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-b0tl1nk-directory/b0tl1nk.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-b0tl1nk-directory/b0tl1nk.json
- HTML version of this page: https://verifymcp.io/servers/com-b0tl1nk-directory/b0tl1nk