MCP servers observed by Lowdown
io.github.mcp-dir/meta_ads-mcp 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); 44 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:io.github.mcp-dir/meta_ads-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.mcp-dir/meta_ads-mcp?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.
- 2026-11-18: server version changed
- 2026-11-15: server version changed
- 2026-11-12: server version changed
What tools does it list?
44 tools on 2026-11-18:
authenticateconnectmarketplacemeta_ads_adsmeta_ads_adset_deletemeta_ads_adset_detailmeta_ads_adset_write_createmeta_ads_adset_write_updatemeta_ads_audiencemeta_ads_audience_deletemeta_ads_audience_write_add_usersmeta_ads_audience_write_createmeta_ads_business_accountsmeta_ads_business_listmeta_ads_business_pagesmeta_ads_business_pixelsmeta_ads_business_usersmeta_ads_campaign_deletemeta_ads_campaign_write_activatemeta_ads_campaign_write_createmeta_ads_campaign_write_pausemeta_ads_campaign_write_updatemeta_ads_campaignsmeta_ads_creative_deletemeta_ads_creative_write_create_admeta_ads_creative_write_create_creativemeta_ads_creative_write_update_admeta_ads_list_accountsmeta_ads_media_list_imagesmeta_ads_media_list_videosmeta_ads_media_write_get_upload_commandmeta_ads_media_write_upload_imagemeta_ads_media_write_upload_videometa_ads_pages_insightsmeta_ads_pages_listmeta_ads_pages_post_insightsmeta_ads_pages_postsmeta_ads_realtimemeta_ads_roasmeta_ads_statusmeta_ads_todayreport_bugshow_versiontoolkit_info
MCP Registry declaration
- Registry name:
io.github.mcp-dir/meta_ads-mcp - Declared version: 0.1.0
- Status: active
- Declared hosts:
api.mcp.ai
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.mcp-dir/meta_ads-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.mcp-dir/meta_ads-mcp?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).