Skybridge Ecommerce Example
REMOTE · ECOMMERCE.SKYBRIDGE.TECH · SCANNED AUG 3
Example MCP App based on Skybridge framework showing an e-commerce products based on request
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 →
Endpoint Security57
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 748 tokens (~187/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · ecommerce.skybridge.tech
claude mcp add --transport http tech-skybridge-ecommerce-ecom-carousel https://ecommerce.skybridge.tech/
[mcp_servers.tech-skybridge-ecommerce-ecom-carousel] url = "https://ecommerce.skybridge.tech/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tech-skybridge-ecommerce-ecom-carousel": {
"type": "remote",
"url": "https://ecommerce.skybridge.tech/",
"enabled": true
}
}
} openclaw mcp add tech-skybridge-ecommerce-ecom-carousel --url https://ecommerce.skybridge.tech/ --transport streamable-http
mcp_servers:
tech-skybridge-ecommerce-ecom-carousel:
url: "https://ecommerce.skybridge.tech/" {
"mcpServers": {
"tech-skybridge-ecommerce-ecom-carousel": {
"type": "http",
"url": "https://ecommerce.skybridge.tech/"
}
}
} 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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
- Resource “browse-catalog” now points somewhere else: ui://views/ext-apps/browse-catalog.html?v=d9a3cec4 → ui://views/ext-apps/browse-catalog.html?v=c2bca992 security
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 58
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 3 Aug 2026 · Probed https://ecommerce.skybridge.tech
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ecommerce.skybridge.tech | CN=Amazon ECDSA 256 M04,O=Amazon,C=US | 12 Jan 2026 | 10 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 5cf83da8a7be3ac0987e7c5d9677e6b |
| SANs: ecommerce.skybridge.tech | ||||||
| CN=Amazon ECDSA 256 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 3,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | ECDSA 256 | ECDSA-SHA256 | 7731272b752ac8adccb0a3027f7dfec18424a |
| CN=Amazon Root CA 3,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | ECDSA 256 | SHA256-RSA | 67f944a30cfcc4f74b5f5306e54d3b7be0ac3 |
DNSSEC insecure
Validation of ecommerce.skybridge.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| skybridge.tech. | 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 |
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ecommerce.skybridge.tech | Verified | 200 | |
| sse | https://ecommerce.skybridge.tech | Verified | 200 | |
| http (plaintext) | http://ecommerce.skybridge.tech | HTTPS enforced | 301 | https://ecommerce.skybridge.tech/ |
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.
browse-catalog ~246
Display a carousel of products from the store.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Filter by product category |
| maxPrice | number | — | Maximum price filter |
| user_intent | string | — | A concise, natural-language summary of what the user is trying to accomplish, derived from the conversation that triggered this tool call. Base it on the user's own words. This is context that helps… |
No output schema declared.
No examples provided.
check-checkout-status ~246
Check the status of a Stripe Checkout session. Returns open, complete, or expired.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | The Stripe Checkout Session ID |
| user_intent | string | — | A concise, natural-language summary of what the user is trying to accomplish, derived from the conversation that triggered this tool call. Base it on the user's own words. This is context that helps… |
No output schema declared.
No examples provided.
create-checkout ~245
Create a Stripe Checkout session for the selected products and return the checkout URL.
| Name | Type | Req | Description |
|---|---|---|---|
| productIds | array | yes | Product IDs to include in the checkout |
| user_intent | string | — | A concise, natural-language summary of what the user is trying to accomplish, derived from the conversation that triggered this tool call. Base it on the user's own words. This is context that helps… |
No output schema declared.
No examples provided.