Supovia Customer Support
REMOTE · MCP.SUPOVIA.COM
Reply to and resolve customer chats, search your help docs and see which conversations need you.
Available components
Last scanned (4 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 75% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3847 tokens (~167/item across 23 items; 15 tools + 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 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
- Supports UI / widget rendering.Pass
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.
- 3 Oct 26 −1
- Resource “supovia-workspace” now points somewhere else: ui://supovia/workspace-v1.html → ui://supovia/workspace-v2.html security
- Schema quality: 86% → 75% ▼ functional
- New resource “supovia-workspace-v1” functional
- 2 Oct 26 93
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 100% → 86% ▼ functional
- New resource “supovia-workspace” functional
- New tool “open_supovia” functional
- 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
- 27 Sept 26 0
- Server version: 0.1.1 → 0.1.2 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
- 18 Sept 26 0
- Authorization: partial → pass ▲ security
- Resource “skill-supovia” was removed ▼ functional
- Resource “skill-support-operations” was removed ▼ functional
- Resource “skill-triage-inbox” was removed ▼ functional
- Resource “supovia-skills-index” was removed ▼ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- New resource “supovia” functional
- New resource “support-operations” functional
- New resource “triage-inbox” functional
- 17 Sept 26 0
- “get_website” reworded the description of “idOrName” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 1 Sept 26 0
- New resource “skill-triage-inbox” 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 5 Nov 2026 · Probed https://mcp.supovia.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.supovia.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 1 Nov 2026 | 17 May 2027 | RSA 2048 | SHA256-RSA | 5875d5af3ccd14afe4baa34bb5950be |
| SANs: *.supovia.com, supovia.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.supovia.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| supovia.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="supovia", resource_metadata="https://mcp.supovia.com/.well-known/oauth-protected-resource", scope="supovia:read supovia:write", error="invalid_token", error_description="missing Bearer token"
Bearer realm="supovia", resource_metadata="https://mcp.supovia.com/.well-known/oauth-protected-resource", scope="supovia:read supovia:write", error="invalid_token", error_description="missing Bearer token"Protected resource metadata
| Document | https://mcp.supovia.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.supovia.com |
| Authorisation server | https://api.authrice.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.supovia.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.supovia.com/mcp | HTTPS enforced |
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_conversation Check one conversation's status ~95
Use this when someone asks about one customer conversation's status, such as whether it is resolved or unread and how many messages the customer, staff and AI agent sent. Returns its channel, status, unread count, times and sender counts from the latest 50 public messages (no message text or internal notes). Not for reading or quoting what was said.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string | yes | Conversation id, up to 200 characters |
| Name | Type | Req | Description |
|---|---|---|---|
| conversation | – | yes | Safe conversation metadata with sender counts over at most the 50 most recent public messages; null when not found. No message body, preview, message id, customer identifier, staff id, internal note,… |
| status | string | yes | – |
No examples provided.
get_document Read a help-center article ~131
Use this when someone needs the text of one help-center article, to quote it or answer a customer from it. Returns the article's title, slug, language, published flag and text up to 20000 characters, with the text's format (html, markdown, plain-text). Not for finding articles on a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | – | Article id; takes precedence over slug |
| locale | string | – | Language code for the slug lookup, e.g. en, it or fr; defaults to en |
| slug | string | – | Article slug, used only when documentId is omitted |
| Name | Type | Req | Description |
|---|---|---|---|
| document | – | yes | The article; null when it is missing or belongs to another organization. Organization ids, translator ids, deprecated slugs, embeddings and arbitrary metadata are never returned. |
| status | string | yes | – |
No examples provided.
get_unresolved_conversation_counts Count open conversations ~67
Use this when someone asks how many customer conversations are still open or unresolved, in total or per website. Returns the total plus a per-website count, largest first, listing up to 100 websites (no customer or message data). Not for finding which conversations are open.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| totalClamped | boolean | yes | – |
| totalUnresolved | integer | yes | Unresolved conversations across every website, listed or not |
| websiteCount | integer | yes | – |
| websites | array | yes | Up to 100 websites with the most unresolved conversations, largest first. Customer identifiers, staff ids, message text and organization ids are never returned. |
| websitesTruncated | boolean | yes | True when more than 100 websites have unresolved conversations |
No examples provided.
get_website Get support website details ~93
Use this when someone asks about one of their Supovia websites by name or id, such as whether its AI customer agent is on. Returns the website's id, name, domain, AI-agent status and created and edited times, or not-found. Not for the help articles published on it.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrName | string | yes | Website id, exact vanity id (its lowercase public address) or exact display name |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
| website | – | yes | Safe website metadata; null when not found. Organization ids, agent prompts, credentials, integration configuration and arbitrary metadata are never returned. |
No examples provided.
list_campaigns List email campaigns ~117
Use this when someone asks which email campaigns one of their websites has. Returns each campaign's id, name and created and edited times, 20 per page by default (no recipients, subject or content). Not for sending a campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The page.nextCursor of the previous page for the same website; absent for the first page |
| limit | integer | – | Campaigns per page, from 1 to 50; defaults to 20 |
| websiteId | string | yes | Website whose campaigns to list |
| Name | Type | Req | Description |
|---|---|---|---|
| campaigns | array | yes | Campaign identity only. Recipient lists, subjects, message content, user ids, organization ids and arbitrary metadata are excluded. |
| page | object | yes | hasMore is true when more campaigns follow; pass nextCursor as cursor to get them |
No examples provided.
list_conversations List customer conversations ~157
Use this when someone asks which customer conversations are open, unread or recently active, optionally for one website. Returns conversation ids with website, channel, resolved flag, unread count and times, most recent activity first, 20 per page by default (no message text or customer details). Not for open-conversation totals.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The page.nextCursor of the previous page with the same filters; absent for the first page |
| limit | integer | – | Conversations per page, from 1 to 50; defaults to 20 |
| resolved | boolean | – | true for resolved conversations, false for open ones; omit for both |
| websiteId | string | – | Only conversations on this website; every website when absent |
| Name | Type | Req | Description |
|---|---|---|---|
| conversations | array | yes | Most recent activity first: the id needed for a follow-up call, website id, channel, resolved state, unread count and timestamps. Message bodies, message ids, customer identifiers, internal notes, ar… |
| page | object | yes | hasMore is true when more conversations follow; pass nextCursor as cursor to get them |
No examples provided.
list_documents List help-center articles ~185
Use this when someone asks which help articles or support docs exist, optionally for one website, language or article. Returns each article's id, title, slug, language, website and published flag, most recently edited first, 20 per page by default, without the article text. Not for finding articles about a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The page.nextCursor of the previous page with the same filters; absent for the first page |
| limit | integer | – | Articles per page, from 1 to 50; defaults to 20 |
| locale | string | – | Only articles in this language code, e.g. en, it or fr; every language when absent |
| slugOriginal | string | – | Only the language versions of one article: its original slug before translation |
| websiteId | string | – | Only articles on this website; every website when absent |
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | yes | Article metadata, most recently edited first. Document content, embeddings, prompts, organization ids and arbitrary metadata are excluded. |
| page | object | yes | hasMore is true when more articles follow; pass nextCursor as cursor to get them |
No examples provided.
list_websites List your support websites ~110
Use this when someone asks which websites their Supovia support chat runs on, or a website's id is needed. Returns each website's id, name, domain and whether its AI customer agent is on, most recently edited first, 20 per page by default. Not for customer conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The page.nextCursor of the previous page; absent for the first page |
| limit | integer | – | Websites per page, from 1 to 50; defaults to 20 |
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | yes | hasMore is true when more websites follow; pass nextCursor as cursor to get them |
| websites | array | yes | Websites in the signed-in organization, most recently edited first. Prompts, credentials, integration configuration, organization ids and arbitrary metadata are excluded. |
No examples provided.
open_customer_inbox_conversation Open a conversation from the inbox ~77
Use this when the embedded Supovia inbox opens a conversation the user selected. Returns whether it was found and gives the view its channel, status, unread count and times (no message text or customer details). Not for questions asked in chat.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string | yes | Conversation id the user selected in the inbox view |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
No examples provided.
open_supovia Supovia ~47
Use this when someone wants to open Supovia and browse their workspace interactively. Support websites, conversation activity and help articles. Starts with up to 100 items. Not for changing data.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
resolve_conversation Resolve or reopen a conversation ~94
Use this when someone wants to mark a customer conversation resolved or done, or reopen it. Returns the conversation id, resolved state and last edit time, and the operator dashboard updates live. Repeating the same state has no further effect. Not for replying to the customer.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string | yes | Conversation to update |
| resolved | boolean | – | true to mark it resolved (the default), false to reopen it |
| Name | Type | Req | Description |
|---|---|---|---|
| conversation | – | yes | Only the id, resolved state and last edit time; null when not found. Customer identifiers, staff ids and organization ids are never returned. |
| status | string | yes | – |
No examples provided.
search_documents Search help-center articles ~124
Use this when someone asks which help article covers a topic or question on one of their websites. Returns up to 5 matching published articles with id, title, slug and language, matched by meaning in one language (English by default). Not for reading an article's text.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language code to search in, e.g. en, it or fr; defaults to en |
| query | string | yes | What the article should cover, in natural language, up to 500 characters |
| websiteId | string | yes | Website whose help center to search |
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | yes | Closest matches first. Content chunks, embeddings, scores, prompts and arbitrary metadata are excluded. |
No examples provided.
send_message Reply to a customer ~142
Use this when the user approves an exact reply to send to a customer in one Supovia conversation. Returns the conversation id and send time. The reply reaches the customer on the conversation's own channels (chat, email, WhatsApp or Messenger); replies to app-store reviews are public. Not for internal notes or closing the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Exact reply text the user approved, 1 to 4,000 characters |
| conversationId | string | yes | Conversation to reply in |
| idempotencyKey | string | yes | Unique key you generate for this conversation and text, up to 255 characters; reuse it only to retry the same send |
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string | yes | Conversation the reply was added to |
| creationTime | – | yes | When the reply was recorded; no message id or text is echoed |
| status | string | yes | – |
No examples provided.
show_customer_inbox Show unread conversations ~73
Use this when someone wants to see their unread customer conversations in an inbox view. Returns how many of the 50 most recently active conversations have unread messages; the view lists up to 20 with channel, status, unread count and times (no message text or customer details). Not for complete open-conversation totals.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationsHaveMore | boolean | yes | True when conversations exist beyond the 50 sampled or the 20 the view lists |
| unreadConversationCount | integer | yes | Conversations with unread messages among the 50 most recently active |
No examples provided.
show_support_overview Show support overview ~90
Use this when someone wants a quick visual summary of their customer support. Returns a card with up to 20 websites (name, domain, AI agent on or off) and the 20 most recently active conversations (channel, open or resolved, times), optionally for one website. Not for complete open-conversation totals.
| Name | Type | Req | Description |
|---|---|---|---|
| websiteId | string | – | Only this website; every website when absent |
| Name | Type | Req | Description |
|---|---|---|---|
| conversations | array | yes | The 20 most recently active conversations: channel, resolved state and timestamps. Customer identifiers, internal record ids, message bodies, prompts, credentials, internal notes, organization ids an… |
| conversationsHaveMore | boolean | yes | – |
| openConversationCount | integer | yes | Open conversations among the 20 shown, not the organization total |
| websites | array | yes | Up to 20 websites: name, domain and AI-agent status only |
| websitesHaveMore | boolean | yes | – |
No examples provided.
How do I install the Supovia Customer Support MCP server?
Supovia Customer Support is a hosted endpoint at https://mcp.supovia.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 · mcp.supovia.com
claude mcp add --transport http com-supovia-supovia 'https://mcp.supovia.com/mcp'
What is the Supovia Customer Support MCP server?
Supovia Customer Support is an MCP server listed in the public MCP registry as com.supovia/supovia. Reply to and resolve customer chats, search your help docs and see which conversations need you. This page covers its hosted endpoint (https://mcp.supovia.com/mcp).
Is the Supovia Customer Support MCP server safe to use?
Supovia Customer Support scores 92 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 Supovia Customer Support MCP server expose?
Supovia Customer Support exposes 15 tools: list_websites, get_website, list_conversations, get_conversation, get_unresolved_conversation_counts, and 10 more. Their descriptions and schemas cost roughly 1,602 tokens of context every time the server is loaded.
Does the Supovia Customer Support MCP server require authentication?
Yes. Supovia Customer Support asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Supovia Customer Support MCP server still maintained?
Supovia Customer Support is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.