Boterly
REMOTE · BOTERLY.SI
Search Grok Bot templates and install them into your Bot by message: skills, rules and routines.
Available components
Last scanned (20 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
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 Security57
- 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 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 590 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 11 Nov 26 +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.
- 10 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 63
First indexed and scored.
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 21 Nov 2026 · Probed https://boterly.si/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=boterly.si | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2306ed22d53df89d0e203e4be47ffae2 |
| SANs: boterly.si, www.boterly.si, *.www.boterly.si | ||||||
| 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 boterly.si. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| si. | DS published | 42378 | 13 | Verified |
| boterly.si. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://boterly.si/api/mcp | Verified | 200 | |
| http (plaintext) | http://boterly.si/api/mcp | HTTPS enforced | 308 | https://boterly.si/api/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 →
diagnose_problem Diagnose a Grok Bot problem ~62
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".
| Name | Type | Req | Description |
|---|---|---|---|
| symptom | string | yes | What is going wrong, in the user’s words. |
No output schema declared.
No examples provided.
install_bundle Install a Boterly bundle ~127
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).
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | string | yes | Bundle id. |
No output schema declared.
No examples provided.
install_template Install a Boterly template ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Template slug from search_templates. |
| target | string | – | Where to install. Defaults to this_bot. |
No output schema declared.
No examples provided.
my_templates My installed templates ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_templates Search Boterly templates ~75
Find Grok Bot templates by job. Returns slug, name, tagline, category, required plugins and usage level. Leave query empty to list all.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter. |
| query | string | – | What the user wants done, e.g. "triage my inbox" or "competitor research". |
No output schema declared.
No examples provided.
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.
remote · boterly.si
claude mcp add --transport http si-boterly-boterly 'https://boterly.si/api/mcp'
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.