# Smartwebchat (remote · smartwebchat.de)

Create and manage website chatbots for European SMBs: bots, chat, and captured leads.

- Trust score: 23/100 (low)
- Change this week: 0
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

> **Deprecated**: this server is marked deprecated in the MCP registry. The registry records this reason: "Moved to eu.smartwebchat/chatbots (`https://smartwebchat.eu/api/mcp).`"

## Components

- remote · `smartwebchat.de`: 23/100 (this document), [markdown](https://verifymcp.io/servers/de-smartwebchat-chatbots/api-mcp.md), [page](https://verifymcp.io/servers/de-smartwebchat-chatbots/api-mcp)

## Channel facts

- Endpoint: `https://smartwebchat.de/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-10-22.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 410.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Smartwebchat MCP server?

Smartwebchat is a hosted endpoint at https://smartwebchat.de/api/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 de-smartwebchat-chatbots 'https://smartwebchat.de/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "de-smartwebchat-chatbots": {
      "url": "https://smartwebchat.de/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "de-smartwebchat-chatbots": {
      "type": "http",
      "url": "https://smartwebchat.de/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.de-smartwebchat-chatbots]
url = "https://smartwebchat.de/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-smartwebchat-chatbots": {
      "type": "remote",
      "url": "https://smartwebchat.de/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add de-smartwebchat-chatbots --url 'https://smartwebchat.de/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  de-smartwebchat-chatbots:
    url: "https://smartwebchat.de/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "de-smartwebchat-chatbots": {
      "Transport": "http",
      "Url": "https://smartwebchat.de/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add de-smartwebchat-chatbots -t streamable-http -u 'https://smartwebchat.de/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "de-smartwebchat-chatbots": {
      "type": "http",
      "url": "https://smartwebchat.de/api/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-09-28 (score 23, 0)

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

### 2026-09-25 (score 23, 0)

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

### 2026-09-01 (score 0)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [security regression] Authorization: fail → unverified
- [security regression] Transport: pass → fail
- [security regression] HSTS header: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-08-27 (score 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-26 (score 0)

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

### 2026-08-25 (score 0)

First indexed and scored.

## MCP tools (6)

### `smartwebchat_service_info` (~66 tokens)

Get factual information about the Smartwebchat service itself: what it does, plans and prices, interface languages, where data is processed, and how to obtain an API key. Works without authentication — use it to answer questions about Smartwebchat before the user has an account.

### `smartwebchat_list_chatbots` (~48 tokens)

List the website chatbots in this account, with their IDs, names and the site each one runs on. Call this first — every other tool needs a botId from here.

### `smartwebchat_create_chatbot` (~246 tokens)

Create a new website chatbot for a business, including its greeting, personality and initial FAQ knowledge. Writes to the account: confirm the business details with the user before calling. Needs a key with full access; a read-only key gets 401 here.

Input parameters:

- `businessName` (string, required): Name of the business the chatbot speaks for
- `description` (string): What the business does — background knowledge for the chatbot
- `faqs` (array): Question and answer pairs the chatbot should know from the start
- `greeting` (string): First message the chatbot sends to a visitor
- `industry` (string, required): Industry of the business, e.g. 'Arztpraxis', 'Restaurant', 'Handwerk'. Used verbatim in the chatbot's prompt, so keep the user's own wording and language.
- `name` (string, required): Display name of the chatbot
- `personality` (string): Tone of voice. The values are German and go to the API verbatim: 'freundlich' (friendly), 'professionell' (professional), 'locker' (casual).
- `websiteUrl` (string): URL of the website the chatbot will run on

### `smartwebchat_chat` (~141 tokens)

Send a visitor message to a chatbot and get its reply, exactly as a website visitor would see it. Use this to test how the chatbot answers, or to check whether its knowledge base covers a topic. Records a conversation and uses the account's message quota, so it needs a key with full access; a read-only key gets 401 here.

Input parameters:

- `botId` (string, required): ID of the chatbot, taken from smartwebchat_list_chatbots
- `message` (string, required): The visitor message to send (max. 2000 characters)
- `sessionId` (string): Optional: pass the same session ID again to continue an existing conversation

### `smartwebchat_get_leads` (~80 tokens)

Retrieve the leads a website chatbot captured from visitors — contact requests, appointment bookings and callback requests, with the visitor's message and contact details. Without botId, returns the leads of every chatbot in the account.

Input parameters:

- `botId` (string): Optional: only return leads of this chatbot. Omit for all chatbots in the account.

### `smartwebchat_update_lead` (~99 tokens)

Change the status of a captured lead, for example to mark it as contacted or closed. Writes to the account. Needs a key with full access; a read-only key gets 401 here.

Input parameters:

- `botId` (string, required): ID of the chatbot the lead belongs to
- `leadId` (string, required): ID of the lead
- `status` (string, required): New status: 'new', 'contacted' or 'closed'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/de-smartwebchat-chatbots/api-mcp#diagnostics

## Score history

- 2026-10-22: 23
- 2026-10-21: 23
- 2026-10-20: 23
- 2026-10-19: 23
- 2026-10-18: 23
- 2026-10-17: 23
- 2026-10-16: 23
- 2026-10-15: 23
- 2026-10-14: 23
- 2026-10-13: 23
- 2026-10-12: 23
- 2026-10-10: 23
- 2026-10-07: 23
- 2026-10-04: 23
- 2026-10-03: 23
- 2026-10-02: 23
- 2026-10-01: 23
- 2026-09-30: 23
- 2026-09-29: 23
- 2026-09-28: 23
- 2026-09-27: 23
- 2026-09-26: 23
- 2026-09-25: 23
- 2026-09-24: 23
- 2026-09-23: 23
- 2026-09-22: 23
- 2026-09-21: 23
- 2026-09-20: 23
- 2026-09-19: 23
- 2026-09-18: 23

## Common questions

### What is the Smartwebchat MCP server?

Smartwebchat is an MCP server listed in the public MCP registry as de.smartwebchat/chatbots. Create and manage website chatbots for European SMBs: bots, chat, and captured leads. This page covers its hosted endpoint (https://smartwebchat.de/api/mcp).

### Is the Smartwebchat MCP server safe to use?

Smartwebchat scores 23 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 Smartwebchat MCP server expose?

Smartwebchat exposes 6 tools: smartwebchat_service_info, smartwebchat_list_chatbots, smartwebchat_create_chatbot, smartwebchat_chat, smartwebchat_get_leads, smartwebchat_update_lead. Their descriptions and schemas cost roughly 680 tokens of context every time the server is loaded.

### Does the Smartwebchat MCP server require authentication?

Its publisher declares that Smartwebchat requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

### Is the Smartwebchat MCP server still maintained?

Smartwebchat is marked deprecated in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://smartwebchat.de/api/mcp
- Authorisation metadata: https://smartwebchat.de/.well-known/oauth-protected-resource/api/mcp
- Website: https://smartwebchat.de/
- Changelog RSS feed: https://verifymcp.io/servers/de-smartwebchat-chatbots/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/de-smartwebchat-chatbots/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/de-smartwebchat-chatbots/api-mcp