Data · Remote MCP server
The Bot Wire
301 real-time data wires. Paid per call via x402, no API key, no free tier.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ArasPasha/botwire-mcp- Version
- 0.7.1
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-07
- Updated
- 2026-08-07
- Publisher
- ArasPasha (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ArasPasha) · how
- Website
- thebotwire.com
- Repository
- github.com/ArasPasha/botwire-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://thebotwire.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | botwire-mcp | 0.7.1 | stdio |
How to connect The Bot Wire
The Bot Wire is a remote MCP server: there is nothing to install. Its endpoint is https://thebotwire.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: botwire-mcp version 0.7.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y botwire-mcp@0.7.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"botwire-mcp": {
"command": "npx",
"args": [
"-y",
"botwire-mcp@0.7.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| That SEO AgentSEO analysis for sites you own: Google Search Console, GA4, PageSpeed, and full site audits. | Remote · HTTPLive check: sign-in required |
| The agent forumA public forum agents read and write to. Answer a thread, mark a post, attach data. No key. | Remote · HTTPLive check: ✗ no handshake |
| The Artillerist IntelligenceSearch art research, estimate commissions, and prepare company intelligence purchases via x402. | Remote · HTTPLive check: ✓ handshake |
| The Bot ForumData feeds for AI agents: list products, sign up, check balance, get a top-up link, fetch data. | Remote · HTTPLive check: ✓ handshake |
| The Company AtlasGlobal customs trade data and company registry. Search shipments, and look up legal entities. | Remote · HTTPLive check: sign-in required |
| The MCP CensusVet any MCP server before you depend on it. Stamp: PASS, REVIEW, or BLOCK. | Remote · HTTPLive check: ✓ handshake |
| The Network Catalog (webGCP)Semantic search over The Network catalog (skills, agencies, roles) with signed webGCP provenance. | Remote · HTTP, SSELive check: ✓ handshake |
| The Profound AgencySearch, price and order press placements across 1,600+ publications. Free AI-visibility audits too. | Remote · HTTPLive check: ✓ handshake |