MCP servers observed by Lowdown
io.github.JCLVSH/iris 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); 81 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.JCLVSH/iris
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.JCLVSH/iris?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.
- 2026-11-14: server version changed
What tools does it list?
81 tools on 2026-11-17:
add_campaign_contactsanalyze_campaignanalyze_responseapprove_messageattach_audience_to_campaignbulk_import_contactsbulk_message_actioncheck_channel_availabilityconfigure_autopilotconfigure_respondercreate_audiencecreate_campaigncreate_contactcreate_conversationcreate_conversation_messagecreate_responder_comment_triggercreate_target_profiledelete_audiencedelete_campaigndelete_campaign_chatdelete_contactdelete_notificationdelete_responder_comment_triggerdelete_target_profilegenerate_audiencesgenerate_campaign_contentgenerate_contentget_ai_usageget_analytics_overviewget_autopilot_statusget_billing_plansget_campaignget_campaign_analyticsget_campaign_chat_messagesget_campaign_usageget_changelogget_contactget_contact_handlesget_contact_typesget_contact_usageget_conversationget_conversation_messagesget_conversation_responderget_discovery_jobget_engagement_metricsget_performance_metricsget_responderget_response_timeget_usagelist_audienceslist_campaign_chatslist_campaign_contactslist_campaignslist_connected_accountslist_contact_conversationslist_contactslist_conversationslist_discovery_sourceslist_notificationslist_pending_messageslist_responder_activitylist_responder_comment_triggerslist_responder_postslist_target_profilesmark_all_notifications_readmark_conversation_readmark_message_sentreject_messagerename_campaign_chatretry_messagerun_autopilot_nowsearch_campaign_contactssearch_contactssend_channel_messageset_conversation_respondersubmit_message_feedbackupdate_campaignupdate_contactupdate_conversationupdate_notificationupdate_responder_comment_trigger
MCP Registry declaration
- Registry name:
io.github.JCLVSH/iris - Declared version: 0.25.3
- Status: active
- Declared hosts:
api.iris-ai.dev
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.JCLVSH/iris", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.JCLVSH/iris?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.JCLVSH/iris -- npx -y @jclvsh/iris
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).