# io.github.sugar-co-dev/roc-mcp-server

Creator commerce intelligence for TikTok Shop brands — benchmarks, ROC calculator, and brand fit.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** io.github.sugar-co-dev
- **License:** Unknown
- **Endpoints:** sse https://roc-mcp-jvutdol4j-ro-ct-eam.vercel.app/mcp
- **Source:** https://github.com/sugar-co-dev/roc-mcp-server
- **Endpoint health:** reachable (last checked 2026-09-28T06:48:46.234Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 113 days — stale; the grade is a claim about the present made from dated evidence

## Security scan

- **Status:** clean
- **Scanned:** 2026-06-14T11:33:59.681Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

8 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `roc_get_category_benchmarks`
- `roc_calculate_projected_roc`
- `roc_get_creator_profile`
- `roc_get_content_formats`
- `roc_get_commission_guidance`
- `roc_analyze_brand_fit`
- `roc_get_tiktok_shop_readiness`
- `roc_get_amplifier_fit`

## Install

**Verdict: review** — Installable, but 3 things to check first: The last scan is 113 days old — the evidence behind this verdict is dated.
**Cautions** (coverage gaps and advisories — never blocking)
- The last scan is 113 days old — the evidence behind this verdict is dated.
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"roc-mcp-server\": {\n      \"type\": \"sse\",\n      \"url\": \"https://roc-mcp-jvutdol4j-ro-ct-eam.vercel.app/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.sugar-co-dev%2Froc-mcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.sugar-co-dev%2Froc-mcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.sugar-co-dev%2Froc-mcp-server
- HTML page: https://forgeregistry.com/registry/io.github.sugar-co-dev%2Froc-mcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.