star365 Commerce
REMOTE · STAR365.SITE · SCANNED SEP 25
Buy a star365 subscription with USDT stablecoin: quote, pay, activate. No human in the loop.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 375 tokens (~125/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · star365.site
claude mcp add --transport http site-star365-commerce 'https://star365.site/api/purchase/mcp'
{
"mcpServers": {
"site-star365-commerce": {
"url": "https://star365.site/api/purchase/mcp"
}
}
} {
"servers": {
"site-star365-commerce": {
"type": "http",
"url": "https://star365.site/api/purchase/mcp"
}
}
} [mcp_servers.site-star365-commerce] url = "https://star365.site/api/purchase/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"site-star365-commerce": {
"type": "remote",
"url": "https://star365.site/api/purchase/mcp",
"enabled": true
}
}
} openclaw mcp add site-star365-commerce --url 'https://star365.site/api/purchase/mcp' --transport streamable-http
mcp_servers:
site-star365-commerce:
url: "https://star365.site/api/purchase/mcp" {
"McpServers": {
"site-star365-commerce": {
"Transport": "http",
"Url": "https://star365.site/api/purchase/mcp"
}
}
} assistant mcp add site-star365-commerce -t streamable-http -u 'https://star365.site/api/purchase/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +1
- 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 security
- Schema quality: 50 → 125 ▼ functional
- Tool coverage: 33% → 43% ▲ functional
- “purchase_intent” added an optional parameter “billing” cosmetic
- 14 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Sept 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://star365.site/api/purchase/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=star365.site | CN=YE2,O=Let's Encrypt,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 655bbc99489ddd08297fa43167dd1650cd1 |
| SANs: star365.site, www.star365.site | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of star365.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| star365.site. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://star365.site/api/purchase/mcp | Verified | 200 | |
| http (plaintext) | http://star365.site/api/purchase/mcp | HTTPS enforced | 301 | https://star365.site/api/purchase/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
purchase_intent ~220
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" 로 부르세요.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| billing | string | – | Billing period. Default monthly. Annual is 12 months at the plan annual price. / 결제 주기. 기본 monthly. annual 은 12개월치입니다. |
| string | yes | – | |
| plan_code | string | yes | – |
| user_confirmed | boolean | yes | true only after the person you act for has seen https://star365.site/agent-privacy |
No output schema declared.
No examples provided.
purchase_quote ~133
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 를 보세요.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_code | string | yes | e.g. voice.pro |
No output schema declared.
No examples provided.
purchase_status ~22
Has this payment arrived yet?
| Name | Type | Req | Description |
|---|---|---|---|
| intent_id | integer | yes | – |
No output schema declared.
No examples provided.
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.