AET Machine Commerce
REMOTE · DEQJVHHMJUXTKDSYZKPY.SUPABASE.CO · SCANNED SEP 28
Read-only PAPER market research for autonomous agents; no live trading or alpha claim.
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 yet verified: we couldn't confirm whether this endpoint requires it. 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 40 tokens (~40/item across 1 items; 1 tools + 0 resources), lean.Pass
- 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 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the AET Machine Commerce MCP server?
AET Machine Commerce is a hosted endpoint at https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/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 · deqjvhhmjuxtkdsyzkpy.supabase.co
claude mcp add --transport http mnvhmslf-aet-machine-commerce 'https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp'
{
"mcpServers": {
"mnvhmslf-aet-machine-commerce": {
"url": "https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp"
}
}
} {
"servers": {
"mnvhmslf-aet-machine-commerce": {
"type": "http",
"url": "https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp"
}
}
} [mcp_servers.mnvhmslf-aet-machine-commerce] url = "https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mnvhmslf-aet-machine-commerce": {
"type": "remote",
"url": "https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp",
"enabled": true
}
}
} openclaw mcp add mnvhmslf-aet-machine-commerce --url 'https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp' --transport streamable-http
mcp_servers:
mnvhmslf-aet-machine-commerce:
url: "https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp" {
"McpServers": {
"mnvhmslf-aet-machine-commerce": {
"Transport": "http",
"Url": "https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp"
}
}
} assistant mcp add mnvhmslf-aet-machine-commerce -t streamable-http -u 'https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp'
{
"mcpServers": {
"mnvhmslf-aet-machine-commerce": {
"type": "http",
"url": "https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/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.
- 28 Sept 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 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.
- 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 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.
- 22 Sept 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.
- 21 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Sept 26 63
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 28 Sept 2026 · Probed https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| 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 deqjvhhmjuxtkdsyzkpy.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 400 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp | Verified | 200 | |
| http (plaintext) | http://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp | HTTPS enforced | 301 | https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/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 →
aet_opportunity_rank_sample AET Opportunity Rank Sample ~40
Return 1-5 sanitized PAPER-only AET opportunity research snapshots. No live-trading or execution authority.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
What is the AET Machine Commerce MCP server?
AET Machine Commerce is an MCP server listed in the public MCP registry as io.github.mnvhmslf/aet-machine-commerce. Read-only PAPER market research for autonomous agents; no live trading or alpha claim. This page covers its hosted endpoint (https://deqjvhhmjuxtkdsyzkpy.supabase.co/functions/v1/aet-agent-commerce-v0/mcp).
Is the AET Machine Commerce MCP server safe to use?
AET Machine Commerce scores 67 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 AET Machine Commerce MCP server expose?
AET Machine Commerce exposes 1 tool: aet_opportunity_rank_sample. Their descriptions and schemas cost roughly 40 tokens of context every time the server is loaded.
Does the AET Machine Commerce MCP server require authentication?
Its publisher declares no required credentials for AET Machine Commerce. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the AET Machine Commerce MCP server still maintained?
AET Machine Commerce is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.