Living Stack Agent Commerce
REMOTE · LIVING-STACK-AGENT-CHECKOUT-LIVE.NEOAETHEL.WORKERS.DEV
Remote MCP for Living Stack offer discovery and buyer-authorized checkout preparation.
Available components
Last scanned (6 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 6 Nov 2026.
Category E-commerce
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
- 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 113 tokens (~37/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 1 Oct 26 0
- Stability: 0.97 → pass security
- 28 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
- 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
- 6 Sept 26 0
- Server version: 0.3.0-beta.1 → 0.3.1-beta.1 functional
- 3 Sept 26 0
- Tool “livingstack.prepare_team_local_purchase” rewrote its description, which is the text the model reads security
- Server version: 0.1.0-beta.1 → 0.3.0-beta.1 functional
- Tool “livingstack.prepare_team_local_purchase” changed its title: Prepare a Team Local agent purchase → Prepare a Complete Local agent purchase cosmetic
- 2 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Sept 26 0
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 6 Nov 2026 · Probed https://living-stack-agent-checkout-live.neoaethel.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=neoaethel.workers.dev | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | eb1c31b2069737ae131fd5505fd0ce0a |
| SANs: neoaethel.workers.dev, *.neoaethel.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of living-stack-agent-checkout-live.neoaethel.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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 |
|---|---|
| x-content-type-options | nosniff |
| 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://living-stack-agent-checkout-live.neoaethel.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://living-stack-agent-checkout-live.neoaethel.workers.dev/mcp | Inconclusive | 405 |
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 →
livingstack.agent_offers List Living Stack offers ~30
Returns exact current Living Stack purchase boundaries and the shortest buyer handoff. This tool never charges.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
livingstack.prepare_claim_audit_purchase Prepare a signed claim-audit purchase ~39
Validates the request and returns the exact MPP-enabled HTTP request. This tool never charges.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | – |
No output schema declared.
No examples provided.
livingstack.prepare_team_local_purchase Prepare a Complete Local agent purchase ~44
Validates the exact Verified Mode release request and returns an MPP purchase route plus protected recovery token. This tool never charges.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | – |
No output schema declared.
No examples provided.
How do I install the Living Stack Agent Commerce MCP server?
Living Stack Agent Commerce is a hosted endpoint at https://living-stack-agent-checkout-live.neoaethel.workers.dev/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 · living-stack-agent-checkout-live.neoaethel.workers.dev
claude mcp add --transport http equinoxaifinance-rgb-living-stack-commerce 'https://living-stack-agent-checkout-live.neoaethel.workers.dev/mcp'
What is the Living Stack Agent Commerce MCP server?
Living Stack Agent Commerce is an MCP server listed in the public MCP registry as io.github.equinoxaifinance-rgb/living-stack-commerce. Remote MCP for Living Stack offer discovery and buyer-authorized checkout preparation. This page covers its hosted endpoint (https://living-stack-agent-checkout-live.neoaethel.workers.dev/mcp).
Is the Living Stack Agent Commerce MCP server safe to use?
Living Stack Agent Commerce scores 74 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 Living Stack Agent Commerce MCP server expose?
Living Stack Agent Commerce exposes 3 tools: livingstack.agent_offers, livingstack.prepare_claim_audit_purchase, livingstack.prepare_team_local_purchase. Their descriptions and schemas cost roughly 113 tokens of context every time the server is loaded.
Does the Living Stack Agent Commerce MCP server require authentication?
No. We connected to Living Stack Agent Commerce without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Living Stack Agent Commerce MCP server still maintained?
Living Stack Agent Commerce is still listed as active in the MCP registry. We last reached this channel on 6 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 Living Stack Agent Commerce MCP server?
VerifyMCP ran 12 checks on Living Stack Agent Commerce, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Living Stack Agent Commerce: HTTPS. 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.