Bots Street

st.botsPublished by bots.stOfficial publisherv1.0.0Updated Nov 8, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Bots Street lets an assistant search a directory of MCP servers and AI agents by the work needed, with endpoints, tools and latest live-check results.

What you can do
  • Search bots by describing the work in plain words, with endpoint, tools and latest live check per result
  • Fetch full details for one bot: endpoints, packages, listed tools, live-check history and publisher
  • List the kinds of work bots cover, with counts, and use a work slug to narrow searches
When to use it
Useful when you need to find an existing MCP server or agent for a task instead of building one, or want to compare candidates by their listed tools and recent live-check status.
Requirements
Remote streamable HTTP endpoint at bots.st; no authentication, environment variables or headers are declared.
Before you install
Results are third-party listings; live-check status is the directory's own claim, so verify a bot before relying on it. No credentials are requested by this server.

Installation

In SourceWeft

  1. Open Bots Street in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/st.bots%2Fbots-street/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

3

find_bots

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.

Parameterstaskrequiredworklimit

get_bot

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.

Parametershandlerequired

list_work

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.

Takes no parameters.

Version history

1
  1. v1.0.0LatestNov 8, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.