# BotThru MCP server

> Read URLs as markdown, check sites and MCP servers, run DNS/RDAP lookups, convert time zones and exchange rates, and embed or rerank text.

- Listing: https://mcp.tc/i/botthru
- Connect: use the server's own URL `https://botthru.com/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Utilities](https://mcp.tc/c/utilities)
- Vendor: BotThru
- Homepage: <https://botthru.com>

## About

BotThru is a set of small utilities for AI agents. It reads public web pages as markdown, inspects a site's agent-facing files, checks URLs and remote MCP servers, and runs DNS and RDAP lookups. It also handles time zone conversion, date math, public holidays, fiat exchange rates, text embeddings and document reranking.

It runs as a hosted Streamable HTTP endpoint at https://botthru.com/mcp. No sign-in or API key is needed. The server asks clients not to send secrets or personal data, and the text of ask requests is stored.

## What it can do

- Read any public URL as markdown
- Discover robots.txt, llms.txt, sitemap and agent cards for a site
- Check URL status, TLS and headers
- Test a remote MCP server by listing its tools
- Look up DNS records and RDAP registration data
- Convert time zones and do date math
- Get public holidays and fiat exchange rates
- Embed text and rerank documents

## Tools (20)

- `read_url`: Read a public http(s) URL as markdown.
- `calculate`: Arithmetic, scientific functions, percentages, and unit conversion.
- `extract_page_data`: Fetch one public HTML page and return title, meta, Open Graph, JSON-LD, links, headings, feeds, and tables.
- `site_discovery`: Fetch a site's robots.txt, llms.txt, sitemap, agent cards, OpenAPI and security.txt.
- `check_url`: Report status, final URL, latency, content type, size, TLS and headers for a URL.
- `check_mcp_server`: Connect to a remote MCP server and list its tools, prompts or resources.
- `dns_lookup`: Look up DNS records via Cloudflare DNS, including email auth checks.
- `rdap_lookup`: Registration data for a domain, IP or ASN.
- `time_convert`: Convert a time between IANA time zones.
- `date_math`: Add or subtract days, hours or business days, or diff two dates.
- `holidays`: Public holidays for a country and year.
- `exchange_rate`: Fiat exchange rate from Frankfurter (ECB), with optional amount and date.
- `embed`: Embed up to 32 strings with Workers AI models.
- `rerank`: Score up to 32 documents against a query.
- `fetch_page`: Alias of read\_url.
- `ask`: Submit a need; answered when a simple tool ran, otherwise routed or logged.
- `time`: Current UTC time and the same instant in a chosen time zone.
- `uuid`: Generate one random UUID.
- `echo`: Show headers, country and bot classification of the request.
- `whoami`: Show which bot BotThru thinks is calling.

## Example prompts

- "Read https://example.com as markdown and summarize it."
- "What are the DNS MX and SPF records for example.org?"
- "Convert 9:00 in Chicago to Tokyo time."
- "Check whether this MCP server URL responds and list its tools."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http botthru https://botthru.com/mcp
```

2. Start Claude Code and type `/mcp`. **botthru** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **BotThru** and paste this URL:

```url
https://botthru.com/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=BotThru&connectorUrl=https%3A%2F%2Fbotthru.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://botthru.com/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://botthru.com/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=botthru&config=eyJ1cmwiOiJodHRwczovL2JvdHRocnUuY29tL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "botthru": {
      "url": "https://botthru.com/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=botthru&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fbotthru.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"botthru","type":"http","url":"https://botthru.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "botthru": {
      "type": "http",
      "url": "https://botthru.com/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "botthru": {
      "serverUrl": "https://botthru.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add botthru --url https://botthru.com/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.botthru]
url = "https://botthru.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http botthru https://botthru.com/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "botthru": {
      "type": "http",
      "url": "https://botthru.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://botthru.com/mcp`.

## Recent changes

- 2026-11-18 02:51 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions.
- 2026-11-17 23:50 UTC: 2 tools added. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Added: calculate, extract\_page\_data.
- 2026-11-17 20:27 UTC: Tracking started: 18 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/botthru#history (Atom feed: https://mcp.tc/i/botthru/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.2.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-11-17
- Updated: 2026-11-17

---
Source: https://mcp.tc/i/botthru (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
