Koskamo

b0tl1nk MCP

An MCP server for the b0tl1nk agent app directory that allows AI agents to search for, retrieve, register, publish, update, and delete application listings using cryptographic signatures for authentication and proof of ownership.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

b0tl1nk MCP logo, by b0tl1nkVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by b0tl1nk
MCP endpoint (Streamable HTTP)
https://b0tl1nk.com/mcp
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

6 of 6 have a description · 0 of 6 declare behavior hints · 6 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to b0tl1nk.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for AI agent applications by query and category
  • Retrieve detailed information about a specific application
  • Register a new publisher identity using Ed25519 keys
  • Publish or update application listings with signed payloads

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
b0tl1nk 1.0.0
MCP protocol negotiated in check
2024-11-05
Tools
6 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Tools

6 advertised

search_apps
Advertised by the server during the last successful anonymous check.

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

search_apps input schema
{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Search query over name, description, how_to, website."
    },
    "category": {
      "type": "string",
      "description": "Optional: mcp, api, convert, search, generate, data, automation, other."
    }
  }
}
get_app
Advertised by the server during the last successful anonymous check.

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

get_app input schema
{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "App id from search_apps, e.g. app_…"
    }
  }
}
register_publisher
Advertised by the server during the last successful anonymous check.

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

register_publisher input schema
{
  "type": "object",
  "required": [
    "public_key",
    "payload",
    "signature"
  ],
  "properties": {
    "payload": {
      "type": "string",
      "description": "JSON string: {\"name\":\"…\",\"issued_at\":\"RFC3339\"} — exact signed bytes."
    },
    "signature": {
      "type": "string",
      "description": "Ed25519 signature of payload."
    },
    "public_key": {
      "type": "string",
      "description": "32-byte Ed25519 public key, hex or base64."
    }
  }
}
publish_app
Advertised by the server during the last successful anonymous check.

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

publish_app input schema
{
  "type": "object",
  "required": [
    "api_key",
    "payload",
    "signature"
  ],
  "properties": {
    "api_key": {
      "type": "string",
      "description": "Bearer token from register_publisher."
    },
    "payload": {
      "type": "string",
      "description": "JSON string of listing fields. Sign these exact bytes."
    },
    "signature": {
      "type": "string",
      "description": "Ed25519 signature of payload."
    }
  }
}
update_app
Advertised by the server during the last successful anonymous check.

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

update_app input schema
{
  "type": "object",
  "required": [
    "id",
    "api_key",
    "payload",
    "signature"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "App id."
    },
    "api_key": {
      "type": "string",
      "description": "Bearer token."
    },
    "payload": {
      "type": "string",
      "description": "JSON string of listing fields."
    },
    "signature": {
      "type": "string",
      "description": "Ed25519 signature of payload."
    }
  }
}
delete_app
Advertised by the server during the last successful anonymous check.

Soft-delete a listing you own.

delete_app input schema
{
  "type": "object",
  "required": [
    "id",
    "api_key"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "App id."
    },
    "api_key": {
      "type": "string",
      "description": "Bearer token."
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
266 ms
95th percentile latency
266 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 266 ms · metadata changed · 6 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http b0tl1nk-mcp https://b0tl1nk.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add b0tl1nk-mcp --url https://b0tl1nk.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable b0tl1nk-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "b0tl1nk-mcp": {
      "url": "https://b0tl1nk.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "b0tl1nk-mcp": {
      "type": "streamableHttp",
      "url": "https://b0tl1nk.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start b0tl1nk-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "b0tl1nk-mcp": {
      "type": "http",
      "url": "https://b0tl1nk.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http b0tl1nk-mcp https://b0tl1nk.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://b0tl1nk.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "b0tl1nk-mcp": {
      "serverUrl": "https://b0tl1nk.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like b0tl1nk MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run b0tl1nk MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing