Botsket
REMOTE · BOTSKET.COM
Product search over independent US stores, with whether an AI agent can check out at each
Available components
Last scanned (3 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 457 tokens (~152/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Tool “get_offer” changed its title: Re-check an offer cosmetic
- Tool “get_store” changed its title: Look up a store cosmetic
- Tool “search_products” changed its title: Search products cosmetic
- 30 Oct 26 71
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 5 Nov 2026 · Probed https://botsket.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=botsket.com | CN=YE1,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6ee6b611bdf167c8b226ba73f24d41a8916 |
| SANs: botsket.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of botsket.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| botsket.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 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://botsket.com/mcp | Verified | 200 | |
| http (plaintext) | http://botsket.com/mcp | HTTPS enforced | 308 | https://botsket.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 →
get_offer Re-check an offer ~52
Re-check one offer's price and stock with the store right now, and return it.
| Name | Type | Req | Description |
|---|---|---|---|
| offer_id | string | yes | The id from search_products, e.g. 'candlewic.com/10001660' |
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | – |
| categories | array | yes | – |
| currency | string | yes | – |
| id | string | yes | Pass to get_offer: store domain / product id |
| image | – | – | – |
| in_stock | boolean | yes | – |
| live | boolean | – | True when the price was re-checked for this call |
| matched_all_words | – | – | In search results: false when the offer matches only some query words |
| name | string | yes | – |
| price | number | yes | Lowest price an agent can pay, USD |
| price_checked_at | string | yes | When the price came from the store (UTC) |
| price_max | – | – | Highest variant price, when it differs |
| sku | – | – | – |
| store | – | yes | – |
| url | string | yes | The product page at the store |
No examples provided.
get_store Look up a store ~44
What Botsket knows about a store, including whether an AI agent can check out there.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Store domain, e.g. 'candlewic.com' |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_checkout | string | yes | – |
| agent_checkout_meaning | string | yes | – |
| agent_checkout_note | string | yes | – |
| agent_checkout_tested_at | – | yes | – |
| blocks_agents | array | yes | Shopping agents the store turns away |
| catalog_crawled_at | – | yes | – |
| domain | string | yes | – |
| name | string | yes | – |
| page | string | yes | – |
| products | integer | yes | – |
| url | string | yes | – |
No examples provided.
search_products Search products ~126
Search products across independent US stores. At most three offers per store.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_checkout | string | – | 'not_blocked' drops stores where our test agent could not reach the card form; 'clean' keeps only stores where it went through cleanly |
| in_stock_only | boolean | – | – |
| limit | integer | – | – |
| max_price | – | – | Highest price in USD |
| min_price | – | – | Lowest price in USD |
| query | string | yes | What to look for, e.g. 'beeswax tealight wicks' |
| sort | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| offers | array | yes | – |
| query | string | yes | – |
No examples provided.
How do I install the Botsket MCP server?
Botsket is a hosted endpoint at https://botsket.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 · botsket.com
claude mcp add --transport http com-botsket-search 'https://botsket.com/mcp'
What is the Botsket MCP server?
Botsket is an MCP server listed in the public MCP registry as com.botsket/search. Product search over independent US stores, with whether an AI agent can check out at each. This page covers its hosted endpoint (https://botsket.com/mcp).
Is the Botsket MCP server safe to use?
Botsket scores 74 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 Botsket MCP server expose?
Botsket exposes 3 tools: search_products, get_offer, get_store. Their descriptions and schemas cost roughly 222 tokens of context every time the server is loaded.
Does the Botsket MCP server require authentication?
No. We connected to Botsket without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Botsket MCP server still maintained?
Botsket is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.