# io.github.farssaadeldin7-ux/customer-sales-support (mcpb · customer-sales-support.mcpb)

AI-powered customer support agent trained on the company's own manuals and FAQs — pre-sales...

- Trust score: 36/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- mcpb · `customer-sales-support.mcpb`: 36/100 (this document), [markdown](https://verifymcp.io/servers/farssaadeldin7-ux-customer-sales-support/customer-sales-support.md), [page](https://verifymcp.io/servers/farssaadeldin7-ux-customer-sales-support/customer-sales-support)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/farssaadeldin7-ux/claude-plugin-suite/releases/download/mcpb-v0.1.3/customer-sales-support.mcpb`
- Version: `0.1.3`
- Transport: `stdio`
- SHA-256: `2c69690d8811f92a97989190dede05573aeaaf0129087303b7011128f1e13200`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-25.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1487 tokens (~114/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.farssaadeldin7-ux/customer-sales-support MCP server?

io.github.farssaadeldin7-ux/customer-sales-support ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 2c69690d8811f92a97989190dede05573aeaaf0129087303b7011128f1e13200; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/farssaadeldin7-ux/claude-plugin-suite/releases/download/mcpb-v0.1.3/customer-sales-support.mcpb`
- SHA-256: `2c69690d8811f92a97989190dede05573aeaaf0129087303b7011128f1e13200`

### Verify on macOS / Linux

```bash
echo "2c69690d8811f92a97989190dede05573aeaaf0129087303b7011128f1e13200  customer-sales-support.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\customer-sales-support.mcpb).Hash -eq "2c69690d8811f92a97989190dede05573aeaaf0129087303b7011128f1e13200"
```

## 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-10-21 (score 36)

First indexed and scored.

## MCP tools (13)

### `taxonomy_reference` (~118 tokens)

The intent-classification tables: the three kinds and their agent behaviour, the three-way test with its edge cases, the clustering method and thresholds, the two worked taxonomies (e-commerce and B2B SaaS, illustrative volumes), the recording format and the symptoms of a wrong taxonomy. Reference data only — it does not classify your intents. Omit section to get everything.

Input parameters:

- `section` (string): Optional: kinds, three_way_test, edge_cases, clustering, thresholds, worked_ecommerce, worked_saas, recording_format, symptoms.

### `article_rules` (~109 tokens)

The article architecture: the template, the style rules with their reasons, the policy-versus-procedure split and its one-question test, the five anti-patterns with their rewrites, the maintenance rules, and the four retrieval failure modes. Reference data only — use article_lint to check a draft against the mechanical subset. Omit section to get everything.

Input parameters:

- `section` (string): Optional: template, style_rules, policy_versus_procedure, anti_patterns, maintenance, retrieval_failure_modes.

### `escalation_reference` (~106 tokens)

The escalation and evaluation rules: the hard-trigger table with its detection cues, the refund-threshold guidance, the handover format and its rules, the grounding contract, the regression-set composition, the four outcomes, the metric definitions with formulas and targets, and the rollout gates. Reference data only. Omit section to get everything.

Input parameters:

- `section` (string): Optional: triggers, refund_threshold, handover, grounding_contract, regression_set, outcomes, metrics, rollout_gates, limits.

### `taxonomy_audit` (~203 tokens)

Audit a recorded ticket taxonomy against the method's stated thresholds: the 500-ticket volume floor, top-20 coverage of 70%, shares summing to 100%, the 0.5% article threshold, the policy-change rule, missing resolution paths, unclassified intents and the 15% multi-intent limit. Computes the containment ceiling by the step-2 arithmetic — static share plus automatable account-specific share — and the ordered article backlog. It does not re-classify intents and names no realistic containment figure, only the ceiling. Requires a paid plan.

Input parameters:

- `intents` (array, required): The taxonomy rows.
- `multi_intent_percent` (number): Share of tickets carrying more than one intent.
- `tail_percent` (number): Combined share of everything below the listed intents.
- `total_tickets` (number): Tickets in the export window. Needed for the 500-ticket volume floor check.
- `window_days` (number): Days the export covers.

### `article_lint` (~182 tokens)

Mechanical checks on one drafted article with the evidence quoted: length over 400 words, a title without a question, missing "Applies to", owner or review date, preamble phrases before the answer, failure talk with no literal error string, policy-looking values in a procedure article, region words under an "all customers" scope, plus the template sections present and the extracted first two sentences. Facts only — whether the first two sentences answer the intent is a judgement it does not make, and set-level failures (near-duplicates, stale outranking) are outside a single-article lint. Requires a paid plan.

Input parameters:

- `body` (string, required): The full article text, including the metadata lines.
- `kind` (string): policy or procedure, if not declared in a "Kind:" line in the body.
- `title` (string): The article title.

### `escalation_screen` (~171 tokens)

Screen one customer message, plus any supplied conversation state, against the hard-trigger table's literal detection phrases, quoting every match. Literal matching only: it misses paraphrase, reads no sentiment, and a message can require escalation without matching anything here — no match is not clearance. For exercising the trigger list against real ticket text, not a replacement for the agent's own trigger implementation. Requires a paid plan.

Input parameters:

- `message` (string, required): The customer message, verbatim.
- `refund_amount` (number): Requested or implied refund amount, if any.
- `refund_threshold` (number): Your refund limit, in the same currency.
- `turns_without_resolution` (number): Agent responses so far without resolution in this conversation.
- `vip_account` (boolean): Whether the account is above your VIP or enterprise revenue threshold.

### `regression_score` (~191 tokens)

Compute the metrics for one scored regression run by the stated formulas — containment, accuracy on contained, false-containment, over-escalation — check the set's composition minimums, flag internally inconsistent cases, and read the two rollout gates a regression run can assess. Arithmetic over outcomes a person has already assigned: it does not judge whether any answer was correct. Set record to true to add the run to the local history. Requires a paid plan.

Input parameters:

- `cases` (array, required): One entry per scored case.
- `change_note` (string): What changed since the previous run — article edit, prompt change, retriever change.
- `label` (string): Short name for the recorded run, e.g. "v3 articles".
- `record` (boolean): Also record this run in the local history on this machine. Nothing about the run itself leaves this computer — the licence check this tool requires still does.

### `regression_history` (~74 tokens)

The recorded regression runs on this machine, newest first, each with the arithmetic difference from the previous run in percentage points. Counting and subtraction only — it does not say whether a movement is significant. Requires a paid plan; the licence check is the only thing this tool sends anywhere.

Input parameters:

- `limit` (number): Default 20.

### `license_status` (~50 tokens)

Check the Customer Sales Support licence on this machine: plan, included capabilities, remaining quota and seat usage. Call this when a paid tool reports a licence problem, or when the user asks what their plan includes.

### `license_activate` (~67 tokens)

Store and activate a Customer Sales Support licence key on this machine. Use when the user pastes a licence key, or after a purchase completes.

Input parameters:

- `license_key` (string, required): The licence key, e.g. PS-XXX-00000-00000-00000-0000

### `start_checkout` (~74 tokens)

Begin a Customer Sales Support purchase. Returns a Stripe Checkout link. Call list_plans first if the user has not chosen a plan.

Input parameters:

- `email` (string): Email address for the receipt and licence.
- `plan` (string, required): Plan id: "pro" or "team". Use list_plans to see the options.

### `list_plans` (~24 tokens)

List the available Customer Sales Support plans, prices and what each one includes.

### `billing_portal` (~30 tokens)

Open the Stripe billing portal to change plan, update the card, or cancel the Customer Sales Support subscription.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/farssaadeldin7-ux-customer-sales-support/customer-sales-support#diagnostics

## Score history

- 2026-10-25: 36
- 2026-10-24: 36
- 2026-10-23: 36
- 2026-10-22: 36
- 2026-10-21: 36

## Common questions

### What is the io.github.farssaadeldin7-ux/customer-sales-support MCP server?

io.github.farssaadeldin7-ux/customer-sales-support is an MCP server listed in the public MCP registry as io.github.farssaadeldin7-ux/customer-sales-support. AI-powered customer support agent trained on the company's own manuals and FAQs, pre-sales... This page covers its MCPB bundle (https://github.com/farssaadeldin7-ux/claude-plugin-suite/releases/download/mcpb-v0.1.3/customer-sales-support.mcpb).

### Is the io.github.farssaadeldin7-ux/customer-sales-support MCP server safe to use?

io.github.farssaadeldin7-ux/customer-sales-support scores 36 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 io.github.farssaadeldin7-ux/customer-sales-support MCP server expose?

io.github.farssaadeldin7-ux/customer-sales-support exposes 13 tools: taxonomy_reference, article_rules, escalation_reference, taxonomy_audit, article_lint, and 8 more. Their descriptions and schemas cost roughly 1,399 tokens of context every time the server is loaded.

## Links

- Repository: https://github.com/farssaadeldin7-ux/claude-plugin-suite
- Changelog RSS feed: https://verifymcp.io/servers/farssaadeldin7-ux-customer-sales-support/customer-sales-support.xml
- Changelog JSON feed: https://verifymcp.io/servers/farssaadeldin7-ux-customer-sales-support/customer-sales-support.json
- HTML version of this page: https://verifymcp.io/servers/farssaadeldin7-ux-customer-sales-support/customer-sales-support