Neonjelly
REMOTE · MCP.NEONJELLY.IO · SCANNED SEP 21
Remote MCP over 1.37M Shopify stores. 14-day trial, 100/day, no account. Paid from $29/mo.
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6497 tokens (~103/item across 63 items; 60 tools + 3 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 60 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 62 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 Neonjelly MCP server?
Neonjelly is a hosted endpoint at https://mcp.neonjelly.io/c/%7Bconnect_token%7D/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.neonjelly.io
claude mcp add --transport http io-neonjelly-mcp 'https://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp'
{
"mcpServers": {
"io-neonjelly-mcp": {
"url": "https://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp"
}
}
} {
"servers": {
"io-neonjelly-mcp": {
"type": "http",
"url": "https://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp"
}
}
} [mcp_servers.io-neonjelly-mcp] url = "https://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-neonjelly-mcp": {
"type": "remote",
"url": "https://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp",
"enabled": true
}
}
} openclaw mcp add io-neonjelly-mcp --url 'https://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp' --transport streamable-http
mcp_servers:
io-neonjelly-mcp:
url: "https://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp" {
"McpServers": {
"io-neonjelly-mcp": {
"Transport": "http",
"Url": "https://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp"
}
}
} assistant mcp add io-neonjelly-mcp -t streamable-http -u 'https://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp'
{
"mcpServers": {
"io-neonjelly-mcp": {
"type": "http",
"url": "https://mcp.neonjelly.io/c/%7Bconnect_token%7D/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
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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 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.
- 11 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.
- 9 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.
- 7 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.
- 6 Sept 26 0
- 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 21 Sept 2026 · Probed https://mcp.neonjelly.io/c/{connect_token}/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.neonjelly.io | CN=YE2,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6d4eb7c0a4e42c136a3897c601f76eec678 |
| SANs: mcp.neonjelly.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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.neonjelly.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| neonjelly.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.neonjelly.io/c/{connect_token}/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.neonjelly.io/c/%7Bconnect_token%7D/mcp | HTTPS enforced | 301 | https://mcp.neonjelly.io/c/%7Bconnect_token%7D/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 →
search_apps Search Shopify apps ~191
Search the Shopify App Store catalog by name, category, pricing, or rating. Follow a slug with get_app_stores to see which merchants run it.
| Name | Type | Req | Description |
|---|---|---|---|
| builtForShopify | boolean | – | If true, only Built for Shopify apps. |
| category | string | – | Store category label from the catalog. |
| limit | integer | – | Page size. Default 20, max 100. |
| minRating | number | – | Minimum store or app rating 0–5. Example: 4.2 |
| offset | integer | – | Skip this many rows. Pair with limit to page. |
| order | string | – | Sort direction. Default desc. |
| pricingType | string | – | App Store pricing type filter. Example: free or subscription |
| q | string | – | Optional free-text query. Example: hoodie or gymshark |
| sort | string | – | App catalog sort. Default rating. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
search_product_ideas Search product ideas ~195
Search product names/categories and return ideas with seller count, price, and UNTAPPED→SATURATED verdict — not one-store listings. Prefer niche_research when the user asks “is this saturated?”
| Name | Type | Req | Description |
|---|---|---|---|
| countries | string | – | ISO-2 country list, comma-separated. Example: US,GB,CA |
| market | string | – | Comma verdicts: UNTAPPED,LOW COMPETITION,COMPETITIVE,SATURATED |
| page | integer | – | 1-based page. Default 1. |
| priceMax | number | – | Maximum listed price in store currency. |
| priceMin | number | – | Minimum listed price in store currency. |
| q | string | yes | Product name or category, not a domain. Example: neck fan or yoga mat |
| region | string | – | Optional region label for product-idea search. |
| trending | boolean | – | If true, only ideas marked trending. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
search_products Search catalog SKUs ~257
Search SKUs across the 368.9M-product catalog. At least one filter is required. For saturation or who-sells-this-idea, use niche_research.
| Name | Type | Req | Description |
|---|---|---|---|
| isBestSeller | boolean | – | If true, only SKUs currently flagged as bestsellers. |
| limit | integer | – | Page size. Default 20, max 100. |
| offset | integer | – | Skip this many rows. Pair with limit to page. |
| order | string | – | Sort direction. Default desc. |
| priceMax | number | – | Maximum listed price in store currency. |
| priceMin | number | – | Minimum listed price in store currency. |
| productType | string | – | Shopify product type. Example: T-Shirt or Hoodie |
| q | string | – | Optional free-text query. Example: hoodie or gymshark |
| sort | string | – | SKU sort: price, merchandising position, or last scrape. |
| storeDomain | string | – | Limit to one merchant hostname. Example: gymshark.com |
| storeVertical | string | – | Vertical of the selling store. Example: Apparel |
| tag | string | – | Shopify product tag. |
| vendor | string | – | Product vendor / supplier name as listed on the storefront. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
search_stores Search store lists ~422
Filter 1.37M Shopify stores into a list (emails/socials live on the card) or roll them up with groupBy. Without groupBy you get store cards; with groupBy you get breakdown rows, not stores. Country is a filter, not a login region.
| Name | Type | Req | Description |
|---|---|---|---|
| appSlug | string | – | Shopify app slug. Example: klaviyo-email-marketing |
| category | string | – | Store category label from the catalog. |
| countryCode | string | – | ISO-3166 alpha-2 country filter, not a login region. Example: US, GB, IN |
| groupBy | string | – | Roll rows into a breakdown table instead of store cards. |
| groupBy2 | string | – | Second breakdown axis. Same values as groupBy. Example: country |
| groupMetric | string | – | How to aggregate visits/revenue when groupBy is set. |
| industry | string | – | Store industry label from the catalog. |
| isDropshipper | boolean | – | If true, only stores the catalog flags as dropship. |
| limit | integer | – | Page size. Default 20, max 100. |
| maxRevenue | number | – | Maximum modeled monthly revenue in USD. Example: 1000000 |
| maxVisits | number | – | Maximum monthly visits. Example: 500000 |
| minRating | number | – | Minimum store or app rating 0–5. Example: 4.2 |
| minRevenue | number | – | Minimum modeled monthly revenue in USD. Example: 50000 |
| minVisits | number | – | Minimum monthly visits. Example: 10000 |
| offset | integer | – | Skip this many rows. Pair with limit to page. |
| order | string | – | Sort direction. Default desc. |
| q | string | – | Optional free-text query. Example: hoodie or gymshark |
| sort | string | – | Store list sort. Use stores when groupBy is set. |
| vertical | string | – | Catalog vertical. Example: Skincare, Apparel, Fashion |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
source_map Map SKU sources ~143
Group a SKU search by vendor: store count and price min/max across the catalog. Use for sourcing or arbitrage after niche_research names the product.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Vendor groups to return. Min 5, max 80. |
| priceMax | number | – | Maximum listed price in store currency. |
| productType | string | – | Shopify product type. Example: T-Shirt or Hoodie |
| q | string | – | Optional free-text query. Example: hoodie or gymshark |
| storeVertical | string | – | Vertical of the selling store. Example: Apparel |
| vendor | string | – | Product vendor / supplier name as listed on the storefront. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
suggest_product_ideas Suggest product ideas ~74
Autocomplete product-idea names as the user types. Follow with search_product_ideas or niche_research on the chosen row.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Autocomplete rows. Max 15. |
| q | string | yes | Brand, product, or free-text query. Example: gymshark or neck fan |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
trending_product_ideas Trending product ideas ~40
List product ideas the catalog marks as heating up. Pair a hit with get_product_research and list_product_sellers — do not invent trend scores.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
upgrade Get checkout URL ~45
Return the paid upgrade URL when trial expired, daily quota is 0, or Signals is blocked. Does not count against quota. Always show the returned URL — never invent a checkout link.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
whoami Check quota ~61
Return this key's plan, used today, remaining quota, rate limit, and expiry. Does not count against daily quota — call first when the user asks “what's my quota?” If remaining is 0 or trial expired, call upgrade and open the URL.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
winning_skus Winning SKUs ~102
List bestsellers, ≥10% markdowns, and new products for a vertical or one store. Require storeVertical or storeDomain — do not call empty.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Inclusive start date YYYY-MM-DD. Example: 2026-08-01 |
| storeDomain | string | – | Limit to one merchant hostname. Example: gymshark.com |
| storeVertical | string | – | Vertical of the selling store. Example: Apparel |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set when the call failed. Example: not_found |
| message | string | – | Human-readable error or hint |
No examples provided.
What is the Neonjelly MCP server?
Neonjelly is an MCP server listed in the public MCP registry as io.neonjelly/mcp. Remote MCP over 1.37M Shopify stores. 14-day trial, 100/day, no account. Paid from $29/mo. This page covers its hosted endpoint (https://mcp.neonjelly.io/c/{connect_token}/mcp).
Is the Neonjelly MCP server safe to use?
Neonjelly scores 84 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 Neonjelly MCP server expose?
Neonjelly exposes 60 tools: whoami, upgrade, resolve_store, list_playbooks, get_examples, and 55 more. Their descriptions and schemas cost roughly 6,122 tokens of context every time the server is loaded.
Does the Neonjelly MCP server require authentication?
Yes. Neonjelly 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 Neonjelly MCP server still maintained?
Neonjelly is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.