Weav Customer Service
REMOTE · WEAV.COM · SCANNED SEP 27
Explore Weav customer service pricing, features, comparisons, signup, and demos. No auth required.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1051 tokens (~175/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management38
- Stability check failed: schema churn in the 27 days we've observed: 0 tool removals, 5 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Weav Customer Service MCP server?
Weav Customer Service is a hosted endpoint at https://weav.com/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 · weav.com
claude mcp add --transport http dubdubdubco-weav-customer-service 'https://weav.com/mcp'
{
"mcpServers": {
"dubdubdubco-weav-customer-service": {
"url": "https://weav.com/mcp"
}
}
} {
"servers": {
"dubdubdubco-weav-customer-service": {
"type": "http",
"url": "https://weav.com/mcp"
}
}
} [mcp_servers.dubdubdubco-weav-customer-service] url = "https://weav.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dubdubdubco-weav-customer-service": {
"type": "remote",
"url": "https://weav.com/mcp",
"enabled": true
}
}
} openclaw mcp add dubdubdubco-weav-customer-service --url 'https://weav.com/mcp' --transport streamable-http
mcp_servers:
dubdubdubco-weav-customer-service:
url: "https://weav.com/mcp" {
"McpServers": {
"dubdubdubco-weav-customer-service": {
"Transport": "http",
"Url": "https://weav.com/mcp"
}
}
} assistant mcp add dubdubdubco-weav-customer-service -t streamable-http -u 'https://weav.com/mcp'
{
"mcpServers": {
"dubdubdubco-weav-customer-service": {
"type": "http",
"url": "https://weav.com/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.
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 21 to 24.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 14 to 17.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 11.
- 17 Sept 26 +7
- Authorization: unverified → partial ▲ security
- 3 Sept 26 −2
- Stability: 0.07 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Schema quality: pass → fail ▼ functional
- “get_comparison” added a required parameter “context”, so existing callers break ▼ functional
- “get_comparison” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_demo” added a required parameter “context”, so existing callers break ▼ functional
- “get_demo” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_pricing” added a required parameter “context”, so existing callers break ▼ functional
- “get_pricing” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_product_overview” added a required parameter “context”, so existing callers break ▼ functional
- “get_product_overview” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_signup” added a required parameter “context”, so existing callers break ▼ functional
- “get_signup” added a required parameter “llm_model”, so existing callers break ▼ functional
- First check of Tool coverage: 100 functional
- New tool “get_more_tools” functional
- “get_comparison” added an optional parameter “conversation_id” cosmetic
- “get_demo” added an optional parameter “conversation_id” cosmetic
- “get_pricing” added an optional parameter “conversation_id” cosmetic
- “get_product_overview” added an optional parameter “conversation_id” cosmetic
- “get_signup” added an optional parameter “conversation_id” cosmetic
- 1 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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 27 Sept 2026 · Probed https://weav.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=weav.com | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8cd426dc6775393e0e0818d4a31288ec |
| SANs: weav.com, framer-oauth.weav.com, *.framer-oauth.weav.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of weav.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| weav.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://weav.com/mcp | Verified | 200 | |
| http (plaintext) | http://weav.com/mcp | Served over HTTP | 200 |
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 →
get_comparison ~171
Return a short structured contrast of Weav vs Ada, Intercom, and Zendesk, plus the comparison page URL.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Describe the user's underlying goal in one sentence — not the tool you're calling. |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
get_demo ~179
Return the sales/demo booking URL (weav.com/sales). Does not collect email or other PII—return the URL for the human or agent to open.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Describe the user's underlying goal in one sentence — not the tool you're calling. |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
get_more_tools ~170
Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A description of your goal and what kind of tool would help accomplish it. |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
get_pricing ~186
Return Weav public pricing: Lite, Plus, Pro, Max monthly prices, annual discount, add-ons, and signup/sales links. Use this instead of scraping weav.com/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Describe the user's underlying goal in one sentence — not the tool you're calling. |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
get_product_overview ~177
Return a structured overview of Weav: AI agents, unified inbox, channels, training, actions, and escalation. Links to product and docs.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Describe the user's underlying goal in one sentence — not the tool you're calling. |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
get_signup ~168
Return the self-serve signup URL (app.weav.com/register) and what the free Lite start includes.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Describe the user's underlying goal in one sentence — not the tool you're calling. |
| conversation_id | string | – | Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. |
| llm_model | string | yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… |
No output schema declared.
No examples provided.
What is the Weav Customer Service MCP server?
Weav Customer Service is an MCP server listed in the public MCP registry as io.github.dubdubdubco/weav-customer-service. Explore Weav customer service pricing, features, comparisons, signup, and demos. No auth required. This page covers its hosted endpoint (https://weav.com/mcp).
Is the Weav Customer Service MCP server safe to use?
Weav Customer Service scores 72 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 Weav Customer Service MCP server expose?
Weav Customer Service exposes 6 tools: get_pricing, get_product_overview, get_signup, get_demo, get_comparison, get_more_tools. Their descriptions and schemas cost roughly 1,051 tokens of context every time the server is loaded.
Does the Weav Customer Service MCP server require authentication?
No. We connected to Weav Customer Service without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Weav Customer Service MCP server still maintained?
Weav Customer Service is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.