A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Nothing to run from here
Supovia Customer Support is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Reply to and resolve customer chats, search your help docs and see which conversations need you.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http supovia-mcp https://mcp.supovia.com/mcp
# 2 — ask your agent for something these tools do
# list_websites, get_website, list_conversations and 12 more
Supovia Customer Support costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SUAll 1 server
supovia1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http supovia-mcp https://mcp.supovia.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Websites per page, from 1 to 50; defaults to 20 |
| cursor | string | no | The page.nextCursor of the previous page; absent for the first page |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| idOrName | string | yes | Website id, exact vanity id (its lowercase public address) or exact display name |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| websiteId | string | no | Only conversations on this website; every website when absent |
| resolved | boolean | no | true for resolved conversations, false for open ones; omit for both |
| limit | integer | no | Conversations per page, from 1 to 50; defaults to 20 |
| cursor | string | no | The page.nextCursor of the previous page with the same filters; absent for the first page |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversationId | string | yes | Conversation id, up to 200 characters |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| websiteId | string | no | Only articles on this website; every website when absent |
| locale | string | no | Only articles in this language code, e.g. en, it or fr; every language when absent |
| slugOriginal | string | no | Only the language versions of one article: its original slug before translation |
| limit | integer | no | Articles per page, from 1 to 50; defaults to 20 |
| cursor | string | no | The page.nextCursor of the previous page with the same filters; absent for the first page |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| documentId | string | no | Article id; takes precedence over slug |
| slug | string | no | Article slug, used only when documentId is omitted |
| locale | string | no | Language code for the slug lookup, e.g. en, it or fr; defaults to en |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What the article should cover, in natural language, up to 500 characters |
| websiteId | string | yes | Website whose help center to search |
| locale | string | no | Language code to search in, e.g. en, it or fr; defaults to en |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| websiteId | string | yes | Website whose campaigns to list |
| limit | integer | no | Campaigns per page, from 1 to 50; defaults to 20 |
| cursor | string | no | The page.nextCursor of the previous page for the same website; absent for the first page |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversationId | string | yes | Conversation to reply in |
| content | string | yes | Exact reply text the user approved, 1 to 4,000 characters |
| idempotencyKey | string | yes | Unique key you generate for this conversation and text, up to 255 characters; reuse it only to retry the same send |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversationId | string | yes | Conversation to update |
| resolved | boolean | no | true to mark it resolved (the default), false to reopen it |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| websiteId | string | no | Only this website; every website when absent |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversationId | string | yes | Conversation id the user selected in the inbox view |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Supovia Customer Support or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.1.2 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest7c002634435f3e9b905c3922c627c37424e3402770143d5c13c2fa49842d11f0
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_websites | no tags | |
| get_website | no tags | |
| list_conversations | no tags | |
| get_conversation | no tags | |
| get_unresolved_conversation_counts | no tags | |
| list_documents | no tags | |
| get_document | no tags | |
| search_documents | no tags | |
| list_campaigns | no tags | |
| send_message | external-sinkstate-write | external-sink: keyword "send_message"; state-write: declares readOnlyHint: false, destructiveHint: true |
| resolve_conversation | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| open_supovia | untrusted-input | untrusted-input: keyword "browse" |
| show_support_overview | no tags | |
| show_customer_inbox | untrusted-input | untrusted-input: keyword "read_message" |
| open_customer_inbox_conversation | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest7c002634435f3e9b
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.2.
0.1.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Supovia Customer Support can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.