# com.seoapi/bingbot (remote · bingbot.seoapi.com)

Validate whether an IP address belongs to Bingbot. Remote MCP server exposing a validate_ip tool.

- Trust score: 63/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `bingbot.seoapi.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-seoapi-bingbot/bingbot.md), [page](https://verifymcp.io/servers/com-seoapi-bingbot/bingbot)

## Channel facts

- Endpoint: `https://bingbot.seoapi.com/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-08-03.

- **Endpoint Security**: 54/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 57 tokens (~57/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.com-seoapi-bingbot]
url = "https://bingbot.seoapi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-seoapi-bingbot": {
      "type": "remote",
      "url": "https://bingbot.seoapi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-seoapi-bingbot --url https://bingbot.seoapi.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-seoapi-bingbot:
    url: "https://bingbot.seoapi.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-seoapi-bingbot": {
      "type": "http",
      "url": "https://bingbot.seoapi.com/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-08-01 (score 63, +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.

### 2026-07-31 (score 62, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 63, +51)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 12)

First indexed and scored.

## MCP tools (1)

### `validate_ip` (~57 tokens)

Validate Bingbot IP

Check whether an IP address (IPv4 or IPv6) is a genuine Bingbot IP address, verified against Bingbot's published IP data on seoapi.com.

Input parameters:

- `ip` (string, required): The IPv4 or IPv6 address to validate

## Diagnostics

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

## Score history

- 2026-08-03: 63
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 63
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 63
- 2026-07-26: 12

## Links

- Remote endpoint: https://bingbot.seoapi.com/mcp
- Website: https://seoapi.com/bingbot/
- Changelog RSS feed: https://verifymcp.io/servers/com-seoapi-bingbot/bingbot/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-seoapi-bingbot/bingbot/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-seoapi-bingbot/bingbot