MCP servers observed by Lowdown
io.github.Misar-AI/misarmail-mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 55 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 2 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:io.github.Misar-AI/misarmail-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Misar-AI/misarmail-mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
55 tools on 2026-11-17:
add_domainarchive_emailcategorize_inbox_emailscheck_dmarcclear_sandboxconfigure_inbound_domaincreate_ab_testcreate_automationcreate_campaigncreate_contactcreate_landing_pagecreate_templategenerate_reportgenerate_subject_linesget_analyticsget_analytics_timelineget_automationget_campaignget_contact_scoreget_deliverability_scoreget_emailget_formget_form_submissionsget_inbox_conversation_messagesget_integrationget_marketplace_itemget_monetization_statsget_revenue_attributionget_warmup_statusimport_contactslist_ab_testslist_api_keyslist_automationslist_campaignslist_contactslist_domainslist_emailslist_formslist_inbox_conversationslist_integrationslist_marketplace_itemslist_sandbox_sendslist_templatesrender_templatereply_to_emailrun_deliverability_auditselect_ab_test_winnersend_campaignsend_emailtoggle_automationtoggle_integrationupdate_contactupgradevalidate_emailverify_domain
MCP Registry declaration
- Registry name:
io.github.Misar-AI/misarmail-mcp - Declared version: 5.1.2
- Status: active
- Declared hosts:
api.misar.io
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:io.github.Misar-AI/misarmail-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Misar-AI/misarmail-mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.Misar-AI/misarmail-mcp -- npx -y @misarmail/mcp
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).