MCP servers observed by Lowdown
app.shopemail/shopemail MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 80 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.shopemail/shopemail
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.shopemail/shopemail?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
80 tools on 2026-11-18:
add_blockadd_data_fieldadd_detail_fieldarchive_themecopy_brand_settingscopy_themecreate_custom_themeduplicate_blockexport_emailexport_themeget_block_formatsget_change_historyget_contextget_editor_formatsget_email_optionsget_preview_dataget_shopify_data_catalogget_themeget_theme_exampleimport_email_contentinspect_emaillist_blockslist_data_fieldslist_emailslist_imageslist_rule_recipeslist_theme_exampleslist_themesmove_blockopen_editorpreview_emailread_emailremove_blockremove_block_contentremove_block_ruleremove_data_fieldremove_rule_reciperemove_sectionremove_section_rulerename_themereorder_blocksrestore_sectionrestore_themesave_rule_recipeselect_themeset_block_contentset_block_ruleset_block_styleset_brand_colorset_brand_detailsset_brand_logoset_brand_shapeset_brand_typographyset_checklist_itemset_custom_codeset_dark_theme_tokenset_email_brand_defaultsset_email_contentset_email_copyset_email_item_layoutset_email_styleset_native_block_visibilityset_preview_dataset_section_lockset_section_ruleset_section_visibilityset_shared_block_contentset_shared_settingset_store_brand_logoset_theme_fontset_theme_layoutset_theme_settingset_theme_tokenset_workspace_active_themestudio_savestudio_snapshotundo_editupdate_blockupload_imageuse_store_brand_logo
MCP Registry declaration
- Registry name:
app.shopemail/shopemail - Declared version: 0.2.0
- Status: active
- Declared hosts:
shopemail.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:app.shopemail/shopemail", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.shopemail/shopemail?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).