Ecomwith Commerce Desk
REMOTE · ECOMWITH.COM
Break-even ROAS and profit calculators, UTM link builder, and Ecomwith tutorial and report search.
Available components
Last scanned (6 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 872 tokens (~145/item across 6 items; 6 tools + 0 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 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.
- 26 Oct 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.
- 24 Oct 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.
- 21 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://ecomwith.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ecomwith.com | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2e41f6d7eb723aaf13327eafab35fe97 |
| SANs: ecomwith.com, brand-meta.ecomwith.com, *.brand-meta.ecomwith.com | ||||||
| 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 ecomwith.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ecomwith.com. | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=(), payment=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ecomwith.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://ecomwith.com/api/mcp | HTTPS enforced | 301 | https://ecomwith.com/api/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 →
build_campaign_utm Build a campaign UTM link ~120
Format one HTTP(S) campaign URL with source, medium and campaign, plus optional content and term. Trims and lowercases UTM values and replaces whitespace with underscores. Returns naming warnings. Never visits the URL, sends a message, saves a campaign or changes tracking settings.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | yes | – |
| content | string | – | – |
| medium | string | yes | – |
| source | string | yes | – |
| term | string | – | – |
| url | string | yes | Destination URL. This tool formats it locally and never fetches it. |
| Name | Type | Req | Description |
|---|---|---|---|
| fetched | boolean | yes | – |
| namingWarnings | array | yes | – |
| normalization | string | yes | – |
| url | string | yes | – |
No examples provided.
calculate_break_even_roas Calculate break-even ROAS ~289
Calculate break-even and target-profit ROAS and maximum CPA from user-supplied revenue, costs, percentage fees and refund reserve. Ask for missing inputs even if asked not to ask questions. Unknown fields must be null, never guessed zeros or a default currency. If any input is unknown, returns needs_input with questions and no estimate. Only explicit user-supplied zeros are valid. Does not read an ad account or change a budget.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | – | yes | User-supplied ISO 4217 currency code. Use null if unknown; never assume USD. |
| paymentFeeRate | – | yes | User-supplied payment fee percentage: 3 means 3%. Use null if unknown; do not substitute 0. |
| price | – | yes | User-supplied revenue per order after discounts and excluding collected taxes. Use null if unknown. |
| productCost | – | yes | User-supplied product cost per order. Use null if unknown; use 0 only when the user explicitly supplied zero. |
| refundRate | – | yes | User-supplied refund reserve percentage. Use null if unknown; do not substitute 0. |
| shippingCost | – | yes | User-supplied net shipping and fulfillment cost per order. Use null if unknown; do not substitute 0. |
| targetProfit | – | yes | User-supplied desired profit per order, or 0 when the user requests break-even only. Use null if unknown. |
| Name | Type | Req | Description |
|---|---|---|---|
| estimate | object | – | – |
| missingInputs | object | – | – |
| status | string | yes | – |
No examples provided.
compare_profit_scenarios Compare profit scenarios ~91
Compare two to five user-supplied pricing or cost scenarios in one currency. Unknown inputs must be null, never guessed zeros or a default currency. If any scenario is incomplete, returns needs_input with labeled questions and no numeric comparison; ask for those inputs. Complete scenarios return contribution, maximum CPA and ROAS. Does not predict sales or change pricing or advertising.
| Name | Type | Req | Description |
|---|---|---|---|
| scenarios | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| missingInputs | array | – | – |
| scenarios | array | – | – |
| status | string | yes | – |
No examples provided.
get_public_weekly_report Read a public ecommerce weekly report ~105
Read guest excerpts and cited source links for one published or corrected Ecomwith weekly report, using a slug returned by list_public_weekly_reports. Retain publication and correction dates and each cited source verificationStatus label; do not upgrade weaker evidence. Rechecks publication state each call. A withdrawn, unpublished, missing or unavailable-language report is not returned. No member content or private research notes are accessible.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| report | object | yes | – |
No examples provided.
list_public_weekly_reports List public ecommerce weekly reports ~73
List up to ten Ecomwith published or corrected ecommerce reports with public summaries and dates. Does not return drafts, withdrawn issues, member-only sections, subscriber data or unpublished research. These are dated editorial reports, not a live news feed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| locale | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| locale | string | yes | – |
No examples provided.
search_ecommerce_resources Search Ecomwith resources ~82
Search Ecomwith published tutorial metadata, internal tool descriptions and public answer summaries in English or Chinese. Returns up to ten source links with content access labels. Does not search the wider web, fetch websites or return paid lesson bodies, drafts or customer data.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| locale | string | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| locale | string | yes | – |
| scope | string | yes | – |
No examples provided.
How do I install the Ecomwith Commerce Desk MCP server?
Ecomwith Commerce Desk is a hosted endpoint at https://ecomwith.com/api/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 · ecomwith.com
claude mcp add --transport http com-ecomwith-commerce-desk 'https://ecomwith.com/api/mcp'
What is the Ecomwith Commerce Desk MCP server?
Ecomwith Commerce Desk is an MCP server listed in the public MCP registry as com.ecomwith/commerce-desk. Break-even ROAS and profit calculators, UTM link builder, and Ecomwith tutorial and report search. This page covers its hosted endpoint (https://ecomwith.com/api/mcp).
Is the Ecomwith Commerce Desk MCP server safe to use?
Ecomwith Commerce Desk scores 78 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 Ecomwith Commerce Desk MCP server expose?
Ecomwith Commerce Desk exposes 6 tools: calculate_break_even_roas, compare_profit_scenarios, build_campaign_utm, search_ecommerce_resources, list_public_weekly_reports, get_public_weekly_report. Their descriptions and schemas cost roughly 760 tokens of context every time the server is loaded.
Does the Ecomwith Commerce Desk MCP server require authentication?
No. We connected to Ecomwith Commerce Desk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ecomwith Commerce Desk MCP server still maintained?
Ecomwith Commerce Desk is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.