Smartwebchat
REMOTE · SMARTWEBCHAT.DE · SCANNED OCT 15
Create and manage website chatbots for European SMBs: bots, chat, and captured leads.
Available components
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).
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 410. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
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.
remote · smartwebchat.de
claude mcp add --transport http de-smartwebchat-chatbots 'https://smartwebchat.de/api/mcp'
{
"mcpServers": {
"de-smartwebchat-chatbots": {
"url": "https://smartwebchat.de/api/mcp"
}
}
} {
"servers": {
"de-smartwebchat-chatbots": {
"type": "http",
"url": "https://smartwebchat.de/api/mcp"
}
}
} [mcp_servers.de-smartwebchat-chatbots] url = "https://smartwebchat.de/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"de-smartwebchat-chatbots": {
"type": "remote",
"url": "https://smartwebchat.de/api/mcp",
"enabled": true
}
}
} openclaw mcp add de-smartwebchat-chatbots --url 'https://smartwebchat.de/api/mcp' --transport streamable-http
mcp_servers:
de-smartwebchat-chatbots:
url: "https://smartwebchat.de/api/mcp" {
"McpServers": {
"de-smartwebchat-chatbots": {
"Transport": "http",
"Url": "https://smartwebchat.de/api/mcp"
}
}
} assistant mcp add de-smartwebchat-chatbots -t streamable-http -u 'https://smartwebchat.de/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- 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. functional
- 27 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 15 Oct 2026 · Probed https://smartwebchat.de/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=smartwebchat.de | CN=YE1,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 61c7f5d926eee21fb8bcadcd8ca2d6c0849 |
| SANs: smartwebchat.de | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of smartwebchat.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| smartwebchat.de. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 410 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://smartwebchat.de/api/mcp | HTTP error | 410 | |
| http (plaintext) | http://smartwebchat.de/api/mcp | HTTPS enforced | 308 | https://smartwebchat.de/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
smartwebchat_chat ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| botId | string | yes | ID of the chatbot, taken from smartwebchat_list_chatbots |
| message | string | yes | The visitor message to send (max. 2000 characters) |
| sessionId | string | – | Optional: pass the same session ID again to continue an existing conversation |
No output schema declared.
No examples provided.
smartwebchat_create_chatbot ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| businessName | string | yes | 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 | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
smartwebchat_get_leads ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| botId | string | – | Optional: only return leads of this chatbot. Omit for all chatbots in the account. |
No output schema declared.
No examples provided.
smartwebchat_list_chatbots ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smartwebchat_service_info ~66
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smartwebchat_update_lead ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| botId | string | yes | ID of the chatbot the lead belongs to |
| leadId | string | yes | ID of the lead |
| status | string | yes | New status: 'new', 'contacted' or 'closed' |
No output schema declared.
No examples provided.
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 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.