# star365 Commerce (remote · star365.site)

Buy a star365 subscription with USDT stablecoin: quote, pay, activate. No human in the loop.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `star365.site`: 65/100 (this document), [markdown](https://verifymcp.io/servers/site-star365-commerce/api-purchase-mcp.md), [page](https://verifymcp.io/servers/site-star365-commerce/api-purchase-mcp)

## Channel facts

- Endpoint: `https://star365.site/api/purchase/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 375 tokens (~125/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 43% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.

## Install

### How do I install the star365 Commerce MCP server?

star365 Commerce is a hosted endpoint at https://star365.site/api/purchase/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 site-star365-commerce 'https://star365.site/api/purchase/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "site-star365-commerce": {
      "url": "https://star365.site/api/purchase/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "site-star365-commerce": {
      "type": "http",
      "url": "https://star365.site/api/purchase/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.site-star365-commerce]
url = "https://star365.site/api/purchase/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-star365-commerce": {
      "type": "remote",
      "url": "https://star365.site/api/purchase/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add site-star365-commerce --url 'https://star365.site/api/purchase/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  site-star365-commerce:
    url: "https://star365.site/api/purchase/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "site-star365-commerce": {
      "Transport": "http",
      "Url": "https://star365.site/api/purchase/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add site-star365-commerce -t streamable-http -u 'https://star365.site/api/purchase/mcp'
```

### Other

```json
{
  "mcpServers": {
    "site-star365-commerce": {
      "type": "http",
      "url": "https://star365.site/api/purchase/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-09-25 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 65, +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-09-21 (score 64, +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.

### 2026-09-19 (score 63, +1)

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

### 2026-09-17 (score 62, +1)

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

### 2026-09-15 (score 61, +1)

- [security] Tool “purchase_intent” rewrote its description, which is the text the model reads
- [security] Tool “purchase_quote” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 50 → 125
- [functional improvement] Tool coverage: 33% → 43%
- [cosmetic] “purchase_intent” added an optional parameter “billing”

### 2026-09-14 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-13 (score 60)

First indexed and scored.

## MCP tools (3)

### `purchase_quote` (~133 tokens)

Price and contents of one star365 plan, in USDT — monthly and annual. Read-only, no account needed. Check billing_options[].payable: this deposit address has a network minimum, so cheap plans are payable annually, not monthly. / star365 요금제 1종의 가격과 구성(월간·연간). 읽기 전용, 계정 불필요. 저가 요금제는 수취 주소의 최소 입금액 때문에 연간으로만 결제됩니다 — billing_options[].payable 를 보세요.

Input parameters:

- `plan_code` (string, required): e.g. voice.pro

### `purchase_intent` (~220 tokens)

Open a payment for a plan. Returns a unique USDT amount and address. Send that exact amount, then call purchase_status: it confirms the payment and activates the subscription. Pass billing="annual" for plans under the network minimum. / 요금제 결제를 엽니다. 고유 USDT 금액과 주소를 돌려줍니다. 그 금액을 정확히 보낸 뒤 purchase_status 를 부르면 입금 확인과 구독 개시가 이루어집니다. 최소 입금액 미만인 요금제는 billing="annual" 로 부르세요.

Input parameters:

- `agent_id` (string, required)
- `billing` (string): Billing period. Default monthly. Annual is 12 months at the plan annual price. / 결제 주기. 기본 monthly. annual 은 12개월치입니다.
- `email` (string, required)
- `plan_code` (string, required)
- `user_confirmed` (boolean, required): true only after the person you act for has seen https://star365.site/agent-privacy

### `purchase_status` (~22 tokens)

Has this payment arrived yet?

Input parameters:

- `intent_id` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/site-star365-commerce/api-purchase-mcp#diagnostics

## Score history

- 2026-09-25: 65
- 2026-09-24: 65
- 2026-09-23: 64
- 2026-09-22: 64
- 2026-09-21: 64
- 2026-09-20: 63
- 2026-09-19: 63
- 2026-09-18: 62
- 2026-09-17: 62
- 2026-09-16: 61
- 2026-09-15: 61
- 2026-09-14: 60
- 2026-09-13: 60

## Common questions

### What is the star365 Commerce MCP server?

star365 Commerce is an MCP server listed in the public MCP registry as site.star365/commerce. Buy a star365 subscription with USDT stablecoin: quote, pay, activate. No human in the loop. This page covers its hosted endpoint (https://star365.site/api/purchase/mcp).

### Is the star365 Commerce MCP server safe to use?

star365 Commerce scores 65 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 star365 Commerce MCP server expose?

star365 Commerce exposes 3 tools: purchase_quote, purchase_intent, purchase_status. Their descriptions and schemas cost roughly 375 tokens of context every time the server is loaded.

### Does the star365 Commerce MCP server require authentication?

No. We connected to star365 Commerce without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the star365 Commerce MCP server still maintained?

star365 Commerce is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://star365.site/api/purchase/mcp
- Website: https://star365.site/
- Changelog RSS feed: https://verifymcp.io/servers/site-star365-commerce/api-purchase-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/site-star365-commerce/api-purchase-mcp.json
- HTML version of this page: https://verifymcp.io/servers/site-star365-commerce/api-purchase-mcp