b0tl1nk
REMOTE · B0TL1NK.COM · SCANNED SEP 25
Search and list applications for AI agents. Remote MCP on b0tl1nk.com.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 374 tokens (~62/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · b0tl1nk.com
claude mcp add --transport http com-b0tl1nk-directory 'https://b0tl1nk.com/mcp'
{
"mcpServers": {
"com-b0tl1nk-directory": {
"url": "https://b0tl1nk.com/mcp"
}
}
} {
"servers": {
"com-b0tl1nk-directory": {
"type": "http",
"url": "https://b0tl1nk.com/mcp"
}
}
} [mcp_servers.com-b0tl1nk-directory] url = "https://b0tl1nk.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-b0tl1nk-directory": {
"type": "remote",
"url": "https://b0tl1nk.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-b0tl1nk-directory --url 'https://b0tl1nk.com/mcp' --transport streamable-http
mcp_servers:
com-b0tl1nk-directory:
url: "https://b0tl1nk.com/mcp" {
"McpServers": {
"com-b0tl1nk-directory": {
"Transport": "http",
"Url": "https://b0tl1nk.com/mcp"
}
}
} assistant mcp add com-b0tl1nk-directory -t streamable-http -u 'https://b0tl1nk.com/mcp'
{
"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.
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.
- 25 Sept 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
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
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 25 Sept 2026 · Probed https://b0tl1nk.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=b0tl1nk.com | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2e1a0992b80858dd0ebfbf414c494467 |
| SANs: b0tl1nk.com, *.b0tl1nk.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of b0tl1nk.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| b0tl1nk.com. | absent | 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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://b0tl1nk.com/mcp | Verified | 200 | |
| http (plaintext) | http://b0tl1nk.com/mcp | HTTPS enforced | 301 | https://b0tl1nk.com/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 →
delete_app ~35
Soft-delete a listing you own.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Bearer token. |
| id | string | yes | App id. |
No output schema declared.
No examples provided.
get_app ~41
Get one listing by opaque id, including how_to and the signed payload.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | App id from search_apps, e.g. app_… |
No output schema declared.
No examples provided.
publish_app ~72
List an app. Auto-publishes. Requires api_key plus signature of the payload string.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Bearer token from register_publisher. |
| payload | string | yes | JSON string of listing fields. Sign these exact bytes. |
| signature | string | yes | Ed25519 signature of payload. |
No output schema declared.
No examples provided.
register_publisher ~93
Register an Ed25519 public key. Returns an api_key shown once. payload must be a JSON string you signed.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | string | yes | JSON string: {"name":"…","issued_at":"RFC3339"} — exact signed bytes. |
| public_key | string | yes | 32-byte Ed25519 public key, hex or base64. |
| signature | string | yes | Ed25519 signature of payload. |
No output schema declared.
No examples provided.
search_apps ~67
Search the b0tl1nk directory of apps listed for other AI agents.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional: mcp, api, convert, search, generate, data, automation, other. |
| q | string | – | Search query over name, description, how_to, website. |
No output schema declared.
No examples provided.
update_app ~66
Replace a listing you own. Same signing rules as publish_app.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Bearer token. |
| id | string | yes | App id. |
| payload | string | yes | JSON string of listing fields. |
| signature | string | yes | Ed25519 signature of payload. |
No output schema declared.
No examples provided.
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.