Commerce Intelligence
REMOTE · MCP.PHOSLABS.IO
Behavioral-science tools for commerce: checkout, drop-off, pricing, churn. 5 free calls, then paid.
Available components
Last scanned (11 hours ago)
Scores higher than 57% 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 786 tokens (~98/item across 8 items; 8 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 Coverage71
- 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
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 4 Nov 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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 67
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 5 Nov 2026 · Probed https://mcp.phoslabs.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=phoslabs.io | CN=YE1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 56a0c62d6744a635830cc52dbb77cd297e5 |
| SANs: *.phoslabs.io, phoslabs.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.phoslabs.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| phoslabs.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.phoslabs.io/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.phoslabs.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://mcp.phoslabs.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.phoslabs.io/mcp |
| Authorisation server | https://mcp.phoslabs.io/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.phoslabs.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.phoslabs.io/mcp | Inconclusive | 401 |
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 →
detect_biases ~72
Find cognitive biases in your messaging, UX copy, or product framing. Returns biases found with severity and debiasing recommendations. UNDERSTAND. 20 credits (€0.20 per call).
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | – |
| session_id | string | – | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diagnose_dropoff ~101
Find where and why customers abandon your funnel. Analyzes each step for statistically significant drop-offs and identifies the behavioral barrier at each point. Input: describe the funnel steps, optionally with data as JSON {steps: [{name, users}, ...]}. CONVERT. 20 credits (€0.20 per call).
| Name | Type | Req | Description |
|---|---|---|---|
| funnel_data | string | – | – |
| funnel_description | string | yes | – |
| session_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
find_hidden_barriers ~75
Identify what's really blocking customers from converting — not what they say, but the actual capability gaps, missing motivation, and environmental friction. UNDERSTAND. 20 credits (€0.20 per call).
| Name | Type | Req | Description |
|---|---|---|---|
| behavior | string | yes | – |
| population | string | yes | – |
| session_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
fix_checkout ~67
Redesign a checkout, signup, or purchase flow to reduce abandonment. Returns step-by-step redesigned flow with friction removed and behavioral principles applied. CONVERT. 20 credits (€0.20 per call).
| Name | Type | Req | Description |
|---|---|---|---|
| current_flow | string | yes | – |
| session_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
optimize_onboarding ~69
Reduce time-to-value for new signups. Identifies onboarding friction and designs a flow that gets users to their 'aha moment' faster. RETAIN. 20 credits (€0.20 per call).
| Name | Type | Req | Description |
|---|---|---|---|
| current_flow | string | yes | – |
| session_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
optimize_pricing ~72
Design price framing, anchoring, and tier structure to maximize willingness to pay. Includes decoy pricing analysis and value articulation strategy. CONVERT. 20 credits (€0.20 per call).
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| product | string | yes | – |
| session_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
predict_churn ~68
Identify which customers are about to leave and why. Returns churn risk scores with behavioral drivers and retention interventions. RETAIN. 20 credits (€0.20 per call).
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| session_id | string | – | – |
| user_behavior | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
write_product_copy ~85
Write product descriptions, landing page copy, or marketing messages that convert. Uses social proof, loss framing, anchoring, and scarcity — without being manipulative. CONVERT. 20 credits (€0.20 per call).
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| draft | string | yes | – |
| goal | string | yes | – |
| session_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Commerce Intelligence MCP server?
Commerce Intelligence is a hosted endpoint at https://mcp.phoslabs.io/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 · mcp.phoslabs.io
claude mcp add --transport http io-phoslabs-commerce-intelligence 'https://mcp.phoslabs.io/mcp'
What is the Commerce Intelligence MCP server?
Commerce Intelligence is an MCP server listed in the public MCP registry as io.phoslabs/commerce-intelligence. Behavioral-science tools for commerce: checkout, drop-off, pricing, churn. 5 free calls, then paid. This page covers its hosted endpoint (https://mcp.phoslabs.io/mcp).
Is the Commerce Intelligence MCP server safe to use?
Commerce Intelligence scores 71 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 Commerce Intelligence MCP server expose?
Commerce Intelligence exposes 8 tools: write_product_copy, diagnose_dropoff, find_hidden_barriers, fix_checkout, optimize_onboarding, and 3 more. Their descriptions and schemas cost roughly 609 tokens of context every time the server is loaded.
Does the Commerce Intelligence MCP server require authentication?
Yes. Commerce Intelligence asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Commerce Intelligence MCP server still maintained?
Commerce Intelligence 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.