# Boterly (remote · boterly.si)

Search Grok Bot templates and install them into your Bot by message: skills, rules and routines.

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

## Components

- remote · `boterly.si`: 68/100 (this document), [markdown](https://verifymcp.io/servers/si-boterly-boterly/api-mcp.md), [page](https://verifymcp.io/servers/si-boterly-boterly/api-mcp)

## Channel facts

- Endpoint: `https://boterly.si/api/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-11-21.

- **Endpoint Security**: 57/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 2 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.
  - 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 (good).
  - Tool/resource definitions use about 590 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

Boterly is a hosted endpoint at https://boterly.si/api/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 si-boterly-boterly 'https://boterly.si/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "si-boterly-boterly": {
      "url": "https://boterly.si/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "si-boterly-boterly": {
      "type": "http",
      "url": "https://boterly.si/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.si-boterly-boterly]
url = "https://boterly.si/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "si-boterly-boterly": {
      "type": "remote",
      "url": "https://boterly.si/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add si-boterly-boterly --url 'https://boterly.si/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  si-boterly-boterly:
    url: "https://boterly.si/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "si-boterly-boterly": {
      "Transport": "http",
      "Url": "https://boterly.si/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add si-boterly-boterly -t streamable-http -u 'https://boterly.si/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "si-boterly-boterly": {
      "type": "http",
      "url": "https://boterly.si/api/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-11-19 (score 68, +1)

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

### 2026-11-17 (score 67, +1)

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

### 2026-11-15 (score 66, +1)

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

### 2026-11-13 (score 65, +1)

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

### 2026-11-11 (score 64, +1)

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

### 2026-11-10 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 63)

First indexed and scored.

## MCP tools (5)

### `search_templates` (~75 tokens)

Search Boterly templates

Find Grok Bot templates by job. Returns slug, name, tagline, category, required plugins and usage level. Leave query empty to list all.

Input parameters:

- `category` (string): Optional category filter.
- `query` (string): What the user wants done, e.g. "triage my inbox" or "competitor research".

### `install_template` (~89 tokens)

Install a Boterly template

Get step-by-step install instructions for one template. target "this_bot" (default) adds its skills, rules and paused routines to the current Bot without replacing its role; "new_bot" returns the setup prompt to paste as the first message of a new Bot.

Input parameters:

- `slug` (string, required): Template slug from search_templates.
- `target` (string): Where to install. Defaults to this_bot.

### `install_bundle` (~127 tokens)

Install a Boterly bundle

Install a kit of templates for one role into this Bot in one go. Bundles: founder (Founder kit: morning brief, competitors, leads and a weekly chief of staff); creator (Creator kit: repurpose posts, draft X posts, track your niche, tighten drafts); researcher (Research kit: check claims, audit sources, review memos, map consensus); developer (Developer kit: watch PRs and CI, debug to root cause, walk through code); inbox (Inbox kit: triage email, prep meetings, draft support replies).

Input parameters:

- `bundle` (string, required): Bundle id.

### `my_templates` (~43 tokens)

My installed templates

List the templates this Boterly account has installed, which have a newer version, and the plan and installs left. Reinstall a template with install_template to update it.

### `diagnose_problem` (~62 tokens)

Diagnose a Grok Bot problem

Look up sourced fixes for a Grok Bot problem, e.g. "routine not running", "skills missing after import", "plugin will not connect", "uses too much usage".

Input parameters:

- `symptom` (string, required): What is going wrong, in the user’s words.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/si-boterly-boterly/api-mcp#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 65
- 2026-11-13: 65
- 2026-11-12: 64
- 2026-11-11: 64
- 2026-11-10: 63
- 2026-11-09: 63

## Common questions

### What is the Boterly MCP server?

Boterly is an MCP server listed in the public MCP registry as si.boterly/boterly. Search Grok Bot templates and install them into your Bot by message: skills, rules and routines. This page covers its hosted endpoint (https://boterly.si/api/mcp).

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

Boterly scores 68 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 Boterly MCP server expose?

Boterly exposes 5 tools: search_templates, install_template, install_bundle, my_templates, diagnose_problem. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.

### Does the Boterly MCP server require authentication?

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

### Is the Boterly MCP server still maintained?

Boterly is still listed as active in the MCP registry. We last reached this channel on 21 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 Boterly MCP server?

VerifyMCP ran 12 checks on Boterly, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Boterly: Authorization. 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.

## Links

- Remote endpoint: https://boterly.si/api/mcp
- Website: https://boterly.si/connect
- Changelog RSS feed: https://verifymcp.io/servers/si-boterly-boterly/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/si-boterly-boterly/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/si-boterly-boterly/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/si-boterly-boterly/api-mcp
