Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BotMarket

REMOTE · BOTMARKET.BOT

Search MCP servers, agent skills, tools and agents, with an install command for each.

Available components

72 Trust /100

Last scanned (13 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1034 tokens (~103/item across 10 items; 10 tools + 0 resources), lean.Pass
  • 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
  • 69% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 20 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.

  • 18 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.

  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 69

    First indexed and scored.

Diagnostics

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://botmarket.bot/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=botmarket.bot CN=YE1,O=Let's Encrypt,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA384 5cae24c3187bd72b3bcf990a04b2c081f3a
SANs: *.botmarket.bot, botmarket.bot
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 botmarket.bot. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
bot. DS published 58741 8 Verified
botmarket.bot. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self' https:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https: data:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; frame-src 'self' https:; worker-src 'self' blob: https:; child-src 'self' blob: https:; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://botmarket.bot/mcp Verified 200
http (plaintext) http://botmarket.bot/mcp HTTPS enforced 308 https://botmarket.bot/mcp
MCP tools · 10 exposed · ~902 tokens

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 →

Tool Tokens
get_detail ~52

Get full detail of one catalog entity by slug. Searches agents, MCP servers, tools, skills, and frameworks; returns the first match with its entity type.

NameTypeReqDescription
slugstringyesEntity slug (unique identifier).

No output schema declared.

No examples provided.

get_stats ~25

Get global BotMarket stats (counts of agents, MCPs, protocols, etc).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_x402_services ~53

List services accepting agent-native payments (x402, MTP, MRP, L402).

NameTypeReqDescription
categorystring––
limitinteger––
querystring–Free-text query.

No output schema declared.

No examples provided.

list_quests ~47

List BotMarket quests: verifiable tasks that seed the network (replicate a ceiba node, submit a working MCP). Experimental: no payouts yet.

NameTypeReqDescription
statusstring––

No output schema declared.

No examples provided.

search ~90

Search BotMarket across MCP servers, agent skills, tools and agents at once, best match first. Start here when you do not yet know what kind of thing solves the task. MCP results include how to install them.

NameTypeReqDescription
limitinteger–Max results per kind (default 5, max 25).
querystringyesWhat you need, e.g. 'postgres', 'knowledge graph'.

No output schema declared.

No examples provided.

search_agents ~57

Search the BotMarket catalog of A2A-compatible AI agents. Each agent is self-describing via .well-known/agent-card.json.

NameTypeReqDescription
categorystring––
limitinteger––
querystring––

No output schema declared.

No examples provided.

search_mcps ~222

Search the BotMarket catalog of MCP servers, best match first. Returns name, description, category, repository, stars, and `install` (command, config, required values). Use to find a server for a capability (e.g. 'github', 'postgres', 'browser').

NameTypeReqDescription
categorystring–Optional category filter.
include_hiddenboolean–Also return duplicates and listings with no link to the project (left out by default).
languagestring–Programming language, e.g. Python. Known for few rows.
licensestring–SPDX licence id, e.g. MIT. Known for few rows.
limitinteger–Max results (default 20, max 100).
offsetinteger–Rows to skip.
openboolean–true = only repos that declare a licence; false = only those that do not.
querystring–Free-text query.
sortstring––
updated_daysinteger–Only repos pushed in the last N days.

No output schema declared.

No examples provided.

search_protocols ~80

List protocols tracked by BotMarket: MCP, A2A, x402, MTP (Machine Tree Protocol), MRP, L402, AP2, ACP, ANP, AGNTCY, etc. Filter by kind: payments | agents | context | discovery | identity.

NameTypeReqDescription
kindstring––
querystring––

No output schema declared.

No examples provided.

search_skills ~174

Search the BotMarket catalog of agent skills. Returns name, description, tags, URL, and source. Use to find a skill for a given task (e.g. 'web-scraping', 'pdf').

NameTypeReqDescription
languagestring–Programming language, e.g. Python. Known for few rows.
licensestring–SPDX licence id, e.g. MIT. Known for few rows.
limitinteger–Max results (default 20, max 100).
offsetinteger–Rows to skip.
openboolean–true = only repos that declare a licence; false = only those that do not.
querystring–Free-text query.
sortstring––
updated_daysinteger–Only repos pushed in the last N days.

No output schema declared.

No examples provided.

search_tools ~102

Search the BotMarket catalog of AI tools. Returns name, description, category, and URL. Use to discover tools for a capability or category.

NameTypeReqDescription
categorystring–Optional category filter.
limitinteger–Max results (default 20, max 100).
offsetinteger–Rows to skip.
querystring–Free-text query.
sortstring––
typestring–Optional tool type filter.

No output schema declared.

No examples provided.

Install

How do I install the BotMarket MCP server?

BotMarket is a hosted endpoint at https://botmarket.bot/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 · botmarket.bot

# add to Claude Code
claude mcp add --transport http bot-botmarket-mcp 'https://botmarket.bot/mcp'
Common questions

What is the BotMarket MCP server?

BotMarket is an MCP server listed in the public MCP registry as bot.botmarket/mcp. Search MCP servers, agent skills, tools and agents, with an install command for each. This page covers its hosted endpoint (https://botmarket.bot/mcp).

Is the BotMarket MCP server safe to use?

BotMarket scores 72 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 BotMarket MCP server expose?

BotMarket exposes 10 tools: search, search_mcps, search_agents, search_protocols, get_x402_services, and 5 more. Their descriptions and schemas cost roughly 902 tokens of context every time the server is loaded.

Does the BotMarket MCP server require authentication?

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

Is the BotMarket MCP server still maintained?

BotMarket 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 BotMarket MCP server?

VerifyMCP ran 13 checks on BotMarket, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.