# Bots Street (remote · bots.st)

Find working MCP servers and AI agents for a job, each with our own latest live check.

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

## Components

- remote · `bots.st`: 75/100 (this document), [markdown](https://verifymcp.io/servers/st-bots-bots-street/bots.md), [page](https://verifymcp.io/servers/st-bots-bots-street/bots)

## Channel facts

- Endpoint: `https://bots.st/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**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 241 tokens (~80/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Bots Street MCP server?

Bots Street is a hosted endpoint at https://bots.st/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 st-bots-bots-street 'https://bots.st/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "st-bots-bots-street": {
      "url": "https://bots.st/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "st-bots-bots-street": {
      "type": "http",
      "url": "https://bots.st/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.st-bots-bots-street]
url = "https://bots.st/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "st-bots-bots-street": {
      "type": "remote",
      "url": "https://bots.st/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add st-bots-bots-street --url 'https://bots.st/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  st-bots-bots-street:
    url: "https://bots.st/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "st-bots-bots-street": {
      "Transport": "http",
      "Url": "https://bots.st/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add st-bots-bots-street -t streamable-http -u 'https://bots.st/mcp'
```

### Other

```json
{
  "mcpServers": {
    "st-bots-bots-street": {
      "type": "http",
      "url": "https://bots.st/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-21 (score 75, 0)

- [functional] Server version: 2026-11-19 → 2026-11-20

### 2026-11-20 (score 75, 0)

- [functional] Server version: 2026-11-18 → 2026-11-19

### 2026-11-19 (score 75, +1)

- [functional] Server version: 2026-11-17 → 2026-11-18

### 2026-11-18 (score 74, 0)

- [functional] Server version: 2026-11-16 → 2026-11-17

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

- [functional] Server version: 2026-11-15 → 2026-11-16

### 2026-11-16 (score 73, 0)

- [functional] Server version: 2026-11-14 → 2026-11-15

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

- [functional] Server version: 2026-11-13 → 2026-11-14

### 2026-11-14 (score 72, 0)

- [functional] Server version: 2026-11-12 → 2026-11-13

## MCP tools (3)

### `find_bots` (~110 tokens)

Find bots for a job

Search Bots Street for bots (MCP servers and agents) that can do a piece of work. Describe the work in plain words. Each result says how to reach the bot and what our latest live check found.

Input parameters:

- `limit` (integer)
- `task` (string, required): The work to be done, in plain words, e.g. "find the US tariff code for a product"
- `work` (string): Optional: a kind of work slug from list_work, to narrow the search

### `get_bot` (~55 tokens)

One bot in full

Everything Bots Street knows about one bot: its endpoints and packages, the tools it listed, every live check we ran on it, its publisher.

Input parameters:

- `handle` (string, required): The bot's handle, as in bots.st/<handle>

### `list_work` (~38 tokens)

Kinds of work

The kinds of work bots on the street do, with how many listed bots do each. Use a slug with find_bots to narrow a search.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/st-bots-bots-street/bots#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 72
- 2026-11-13: 72
- 2026-11-12: 71
- 2026-11-11: 71
- 2026-11-10: 70
- 2026-11-09: 70
- 2026-11-08: 69

## Common questions

### What is the Bots Street MCP server?

Bots Street is an MCP server listed in the public MCP registry as st.bots/bots-street. Find working MCP servers and AI agents for a job, each with our own latest live check. This page covers its hosted endpoint (https://bots.st/mcp).

### Is the Bots Street MCP server safe to use?

Bots Street scores 75 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 Bots Street MCP server expose?

Bots Street exposes 3 tools: find_bots, get_bot, list_work. Their descriptions and schemas cost roughly 203 tokens of context every time the server is loaded.

### Does the Bots Street MCP server require authentication?

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

### Is the Bots Street MCP server still maintained?

Bots Street 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 Bots Street MCP server?

VerifyMCP ran 13 checks on Bots Street, 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.

## Links

- Remote endpoint: https://bots.st/mcp
- Website: https://bots.st/agents/
- Changelog RSS feed: https://verifymcp.io/servers/st-bots-bots-street/bots.xml
- Changelog JSON feed: https://verifymcp.io/servers/st-bots-bots-street/bots/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/st-bots-bots-street/bots.json
- HTML version of this page: https://verifymcp.io/servers/st-bots-bots-street/bots
