Sumhound — e-commerce platform changes & seller deadlines
REMOTE · SUMHOUND.COM · SCANNED SEP 20
Curated Amazon/Shopify/TikTok Shop changes (fees, policies, APIs) & upcoming seller deadlines.
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 Security74
- 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
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 626 tokens (~313/item across 2 items; 2 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 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 2 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
How do I install the Sumhound — e-commerce platform changes & seller deadlines MCP server?
Sumhound — e-commerce platform changes & seller deadlines is a hosted endpoint at https://sumhound.com/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 · sumhound.com
claude mcp add --transport http com-sumhound-sumhound-mcp 'https://sumhound.com/mcp'
{
"mcpServers": {
"com-sumhound-sumhound-mcp": {
"url": "https://sumhound.com/mcp"
}
}
} {
"servers": {
"com-sumhound-sumhound-mcp": {
"type": "http",
"url": "https://sumhound.com/mcp"
}
}
} [mcp_servers.com-sumhound-sumhound-mcp] url = "https://sumhound.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-sumhound-sumhound-mcp": {
"type": "remote",
"url": "https://sumhound.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-sumhound-sumhound-mcp --url 'https://sumhound.com/mcp' --transport streamable-http
mcp_servers:
com-sumhound-sumhound-mcp:
url: "https://sumhound.com/mcp" {
"McpServers": {
"com-sumhound-sumhound-mcp": {
"Transport": "http",
"Url": "https://sumhound.com/mcp"
}
}
} assistant mcp add com-sumhound-sumhound-mcp -t streamable-http -u 'https://sumhound.com/mcp'
{
"mcpServers": {
"com-sumhound-sumhound-mcp": {
"type": "http",
"url": "https://sumhound.com/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.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://sumhound.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sumhound.com | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8123d22ee860385e0ea0e6f5ee95a9ab |
| SANs: sumhound.com, *.sumhound.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 sumhound.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sumhound.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sumhound.com/mcp | Verified | 200 | |
| http (plaintext) | http://sumhound.com/mcp | HTTPS enforced | 302 | https://sumhound.com/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 →
get_platform_changes ~209
List recent seller-facing changes on Amazon, Shopify and/or TikTok Shop, newest first. Use for "what changed on TikTok Shop recently", "any new Amazon fees", "Shopify API updates this month". Each change is curated from the platform's official changelog/announcement and includes a summary, change type, impact types, effective date and the original source URL. Args: platform: Optional platform slug — amazon, shopify or tiktok-shop. Empty = all platforms. limit: Max changes to return, 1-100 (default 10). Returns {generated_at, source, platforms, total, changes:[{id, platform, publishedAt, title, summary, changeType, topics, impactTypes, effectiveAt, deadline, originalUrl}]}. Cite each record's originalUrl when presenting; mention generated_at if freshness matters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| platform | string | – | – |
No output schema declared.
No examples provided.
get_upcoming_deadlines ~187
List upcoming seller-facing deadlines on Amazon, Shopify and/or TikTok Shop, soonest first. Use for "any Amazon deadlines coming up", "what do TikTok Shop sellers need to do before month end". Deadlines come from curated official announcements (API sunsets, policy compliance dates, fee effective dates); past deadlines are excluded server-side. Free-form deadlines ("rolling") sort after dated ones. Args: platform: Optional platform slug — amazon, shopify or tiktok-shop. Empty = all platforms. Returns {generated_at, as_of, platforms, total, deadlines:[{id, platform, deadline, title, summary, effectiveAt, originalUrl, ...}]}. `as_of` is the server-side cutoff date used. Cite each record's originalUrl.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | – |
No output schema declared.
No examples provided.
What is the Sumhound — e-commerce platform changes & seller deadlines MCP server?
Sumhound — e-commerce platform changes & seller deadlines is an MCP server listed in the public MCP registry as com.sumhound/sumhound-mcp. Curated Amazon/Shopify/TikTok Shop changes (fees, policies, APIs) & upcoming seller deadlines. This page covers its hosted endpoint (https://sumhound.com/mcp).
Is the Sumhound — e-commerce platform changes & seller deadlines MCP server safe to use?
Sumhound — e-commerce platform changes & seller deadlines scores 81 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 Sumhound — e-commerce platform changes & seller deadlines MCP server expose?
Sumhound — e-commerce platform changes & seller deadlines exposes 2 tools: get_platform_changes, get_upcoming_deadlines. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.
Does the Sumhound — e-commerce platform changes & seller deadlines MCP server require authentication?
No. We connected to Sumhound — e-commerce platform changes & seller deadlines without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sumhound — e-commerce platform changes & seller deadlines MCP server still maintained?
Sumhound — e-commerce platform changes & seller deadlines is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.