# Tiana & Co. Seller Compliance (remote · www.tiana-co.com)

Which certificate (CPC, GCC, FCC, FDA), what marketplaces ask, supplier blacklists, customs holds.

- Trust score: 79/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.tiana-co.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/1294962213sh-tiana-co-free-checks/api-mcp.md), [page](https://verifymcp.io/servers/1294962213sh-tiana-co-free-checks/api-mcp)

## Channel facts

- Endpoint: `https://www.tiana-co.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 37/100
  - 0% 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 1977 tokens (~329/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Tiana & Co. Seller Compliance MCP server?

Tiana & Co. Seller Compliance is a hosted endpoint at https://www.tiana-co.com/api/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.

### Claude

```bash
claude mcp add --transport http 1294962213sh-tiana-co-free-checks 'https://www.tiana-co.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "1294962213sh-tiana-co-free-checks": {
      "url": "https://www.tiana-co.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "1294962213sh-tiana-co-free-checks": {
      "type": "http",
      "url": "https://www.tiana-co.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.1294962213sh-tiana-co-free-checks]
url = "https://www.tiana-co.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "1294962213sh-tiana-co-free-checks": {
      "type": "remote",
      "url": "https://www.tiana-co.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 1294962213sh-tiana-co-free-checks --url 'https://www.tiana-co.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  1294962213sh-tiana-co-free-checks:
    url: "https://www.tiana-co.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "1294962213sh-tiana-co-free-checks": {
      "Transport": "http",
      "Url": "https://www.tiana-co.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 1294962213sh-tiana-co-free-checks -t streamable-http -u 'https://www.tiana-co.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "1294962213sh-tiana-co-free-checks": {
      "type": "http",
      "url": "https://www.tiana-co.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 77, −4)

- [functional improvement] Schema quality: 394 → 329
- [functional] The server now declares the “resources” capability
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: 0
- [functional] Schema quality: excellent → good
- [functional] New resource “answer-card”

### 2026-10-30 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `seller_compliance.which_certificate` (~436 tokens)

Which safety certificate does my product need?

Use this when a seller asks which US safety certificate or import paperwork a product needs: a CPC (Children's Product Certificate) for children's products, a GCC (General Certificate of Conformity) for other regulated products, FCC authorization for electronics, or FDA's import steps for food, supplements, cosmetics, drugs and medical devices (facility registration, prior notice, FSVP). For example: "does my kids' raincoat need a CPC?", "do I need a GCC for a coffee mug?", "Amazon wants a certificate for my toy, which one?", "do I need FDA prior notice to import snacks?". Give the product in the seller's own words. It answers from US federal rules and returns the rule each answer rests on, the date that rule was read, and a link to the free plan. When questions are still open, it lists them with their answer keys: ask the seller all of them, then call again with the same product and their answers. Do not use for duties, tariffs or customs classification (HS or HTS codes), for rules outside the United States, or to fill out, file or declare anything at customs. If the seller asks you to fill out or file a customs entry, do not call this tool: a licensed customs broker files the entry.

Input parameters:

- `answers` (object): The seller's answers to the questions an earlier call listed: answer key → one of that question's values, exactly as listed. Only pass what the seller actually said.
- `fda_kind` (string): Only when an earlier call listed the answer key `fda_tap`: the value the seller chose.
- `made_for_children` (string): Whether the product is made mainly for children 12 or under. Leave it out unless the seller said.
- `other_kind` (string): Only when an earlier call listed the answer key `other_tap`: the value the seller chose.
- `product` (string, required): The product in the seller's own words, e.g. "plush teddy bear", "kids rain boots", "bluetooth speaker", "ceramic coffee mug".

### `seller_compliance.marketplace_asks` (~479 tokens)

Can I sell this on Amazon, Walmart, TikTok Shop or Etsy?

Use this when a seller asks whether they can sell a product on Amazon, Walmart, TikTok Shop or Etsy, to stores, or on their own website, and what each will ask for: "can I sell toys on Amazon?", "requirements for selling supplements on Amazon", "how do I get approved (ungated) to sell kids' clothes?", "Amazon asked for compliance documents, what do I send?", "can I sell a stroller on Etsy?". Give the product in the seller's words and the channels. It returns closed or restricted doors first, then each channel's own rules for that product and the US federal law that applies everywhere, each line numbered to its source with the page's date and the day it was read. It first needs the certificate answer for the product, so it may return questions instead: ask the seller all of them and call again with their answers. Do not use for duties, tariffs or customs classification (HS or HTS codes), for marketplaces outside the US (Amazon UK, Amazon.ca or EU sites, for example), or to promise that a listing will be approved.

Input parameters:

- `answers` (object): The seller's answers to the questions an earlier call listed: answer key → one of that question's values, exactly as listed. Only pass what the seller actually said.
- `channels` (array): Where the seller will sell, in the United States only: amazon (amazon.com, not Amazon UK, Amazon.ca or other countries), walmart, tiktok (TikTok Shop US), etsy, wholesale (to US stores), own (their o…
- `fda_kind` (string): Only when an earlier call listed the answer key `fda_tap`: the value the seller chose.
- `made_for_children` (string): Whether the product is made mainly for children 12 or under. Leave it out unless the seller said.
- `other_kind` (string): Only when an earlier call listed the answer key `other_tap`: the value the seller chose.
- `product` (string, required): The product in the seller's own words, e.g. "plush teddy bear", "kids rain boots", "bluetooth speaker", "ceramic coffee mug".

### `seller_compliance.screen_supplier` (~247 tokens)

Supplier on a blacklist?

Use this when a seller wants to check a supplier or factory against US government blacklists before paying it: "is this factory on the UFLPA list?", "is my Alibaba supplier sanctioned?", "check this supplier for forced labor". Give the company name as the seller has it, for example from the invoice or the store page. It searches the UFLPA Entity List and CBP Withhold Release Orders (forced labor) and the OFAC SDN and Consolidated lists and the US Consolidated Screening List (sanctions), and returns, per list, match, possible match, no match or not searched, with the list's size and date. It checks the name as typed, not a confirmed company, and it is not a record: no listed names, no citations. Do not use to check a person, to judge a supplier's quality, honesty or fraud risk, for lists outside the US, or as proof for customs.

Input parameters:

- `supplier_name` (string, required): The supplier's company name as the seller has it, e.g. from the invoice or the store page. A company only: if the seller names a person, do not call this tool.

### `seller_compliance.what_changed` (~107 tokens)

What changed for sellers this week?

Use this when a seller asks what changed recently in US selling rules: Amazon, Walmart, TikTok Shop or Etsy policy updates, or new federal rules ("did Amazon change anything for toys this week?", "any new seller rules?"). It returns this week's changes, each with its source, the page's own date and the day it was checked, and names the pages that could not be checked. Do not use for tariff or duty changes, or for rules outside the US.

### `seller_compliance.shipment_held` (~467 tokens)

Shipment stuck at customs?

Use this when a seller's shipment is held, detained or under review by US Customs (CBP) and they want to know what kind of hold it is, how long they have, and which documents are usually needed: "customs is holding my shipment, what does the detention notice mean?", "I got a CBP Form 4647", "my container has a CPSC hold", "my shipment says under CBP review", "CBP detained my goods under the UFLPA, how long do I have?". It works from the seller's answers to up to three questions about what the notice says (forced labor, another agency such as CPSC, FDA or FCC, or the stated reason, such as a CF-28 or CF-29), and it never sees the notice itself. It returns the hold type, the response deadline or where to find it on the notice, the usual path and who leads it, and the documents usually needed, each cited to its CBP or federal source with the date it was read. When questions are still open, it lists them with their answer keys: ask the seller, then call again with their answers. Do not use it to read or summarize the notice itself: point the seller to the customs-hold check on tiana-co.com, which reads a notice only after the seller agrees to send it. Do not use it to classify goods or give duty rates, to say whether a shipment will be released, or for customs outside the United States. If the seller asks you to write, argue or file a response to CBP or another agency, do not call this tool: a licensed customs broker or a customs attorney handles the response.

Input parameters:

- `answers` (object): The seller's answers about the notice, by answer key. Leave out any question the seller has not answered: never fill in "no", "unsure" or "none" for the seller, even when the form named seems to make…
- `notice_date` (string): The date printed on the notice, YYYY-MM-DD, only if the seller gives it. Used only for a forced-labor (UFLPA) detention, whose response window is counted from it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/1294962213sh-tiana-co-free-checks/api-mcp#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73

## Common questions

### What is the Tiana & Co. Seller Compliance MCP server?

Tiana & Co. Seller Compliance is an MCP server listed in the public MCP registry as io.github.1294962213sh/tiana-co-free-checks. Which certificate (CPC, GCC, FCC, FDA), what marketplaces ask, supplier blacklists, customs holds. This page covers its hosted endpoint (https://www.tiana-co.com/api/mcp).

### Is the Tiana & Co. Seller Compliance MCP server safe to use?

Tiana & Co. Seller Compliance scores 79 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 Tiana & Co. Seller Compliance MCP server expose?

Tiana & Co. Seller Compliance exposes 5 tools: seller_compliance.which_certificate, seller_compliance.marketplace_asks, seller_compliance.screen_supplier, seller_compliance.what_changed, seller_compliance.shipment_held. Their descriptions and schemas cost roughly 1,736 tokens of context every time the server is loaded.

### Does the Tiana & Co. Seller Compliance MCP server require authentication?

No. We connected to Tiana & Co. Seller Compliance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Tiana & Co. Seller Compliance MCP server still maintained?

Tiana & Co. Seller Compliance 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.

### What did VerifyMCP test on the Tiana & Co. Seller Compliance MCP server?

VerifyMCP ran 14 checks on Tiana & Co. Seller Compliance, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.tiana-co.com/api/mcp
- Website: https://www.tiana-co.com/for-ai
- Changelog RSS feed: https://verifymcp.io/servers/1294962213sh-tiana-co-free-checks/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/1294962213sh-tiana-co-free-checks/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/1294962213sh-tiana-co-free-checks/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/1294962213sh-tiana-co-free-checks/api-mcp