io.github.mikusnuz/meta-ads
NPM · @MIKUSNUZ/META-ADS-MCP · SCANNED SEP 20
MCP server for Meta Marketing API — Facebook & Instagram ad campaign management
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 44 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 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
- Tool/resource definitions use about 8658 tokens (~68/item across 126 items; 123 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 16 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_campaign" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 124 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 io.github.mikusnuz/meta-ads MCP server?
io.github.mikusnuz/meta-ads runs locally as an npm package, launched with npx -y @mikusnuz/meta-ads-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mikusnuz/meta-ads-mcp
claude mcp add mikusnuz-meta-ads -- npx -y @mikusnuz/meta-ads-mcp
{
"mcpServers": {
"mikusnuz-meta-ads": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/meta-ads-mcp"
]
}
}
} {
"servers": {
"mikusnuz-meta-ads": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/meta-ads-mcp"
]
}
}
} codex mcp add mikusnuz-meta-ads -- npx -y @mikusnuz/meta-ads-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mikusnuz-meta-ads": {
"type": "local",
"command": [
"npx",
"-y",
"@mikusnuz/meta-ads-mcp"
],
"enabled": true
}
}
} openclaw mcp add mikusnuz-meta-ads --command npx --arg -y --arg @mikusnuz/meta-ads-mcp
mcp_servers:
mikusnuz-meta-ads:
command: "npx"
args: ["-y", "@mikusnuz/meta-ads-mcp"] {
"McpServers": {
"mikusnuz-meta-ads": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mikusnuz/meta-ads-mcp"
]
}
}
} assistant mcp add mikusnuz-meta-ads -t stdio -c npx -a -y @mikusnuz/meta-ads-mcp
{
"mcpServers": {
"mikusnuz-meta-ads": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/meta-ads-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −2
- Stability: pass → 0.83 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 16 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.77 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@mikusnuz/meta-ads-mcp@1.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
remove_from_block_list ~52
Remove publisher URLs from an existing block list.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | Block list ID |
| urls | string | yes | JSON array of URLs to remove (e.g. '["example.com"]') |
No output schema declared.
No examples provided.
remove_users_from_audience ~83
Remove users from a custom audience. Payload format is the same as add_users_to_audience.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | Audience ID |
| payload | string | yes | JSON string: {schema: ['EMAIL','PHONE',...], data: [['hash1','hash2',...], ...]}. All PII must be SHA-256 hashed. |
No output schema declared.
No examples provided.
search_ad_library ~160
Search the Meta Ad Library for ads. Allows searching by keywords, countries, and ad type. Useful for competitive research and transparency.
| Name | Type | Req | Description |
|---|---|---|---|
| ad_reached_countries | string | yes | Comma-separated country codes where ads were shown (e.g. 'US,GB,KR') |
| ad_type | string | – | Ad type filter: ALL, POLITICAL_AND_ISSUE_ADS, HOUSING_ADS, etc. |
| after | string | – | Pagination cursor for next page |
| fields | string | – | Comma-separated fields to return |
| limit | number | – | Number of results (default 25) |
| order_by | string | – | Sort order for results |
| search_terms | string | yes | Keywords to search for in ads |
No output schema declared.
No examples provided.
search_locations ~91
Search for geographic locations (countries, regions, cities, zip codes) for ad targeting.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of results (default 25) |
| location_types | string | – | Comma-separated location types: country, region, city, zip, geo_market, electoral_district |
| q | string | yes | Search query (e.g. 'New York', 'California', 'United States') |
No output schema declared.
No examples provided.
search_targeting ~116
Search for targeting options (interests, behaviors, demographics, etc.) by keyword. Use this to find valid targeting IDs for ad set targeting specs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of results (default 25) |
| q | string | yes | Search query (e.g. 'fitness', 'technology', 'cooking') |
| type | string | – | Targeting type filter: adinterest, adgeolocation, adeducationschool, adeducationmajor, adworkemployer, adworkposition, adlocale, etc. |
No output schema declared.
No examples provided.
search_targeting_map ~49
Map targeting IDs to their full details (names, types, paths). Useful for resolving IDs obtained from other endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| targeting_list | string | yes | JSON array of targeting IDs to look up |
No output schema declared.
No examples provided.
send_conversion_event ~50
Send a server-side conversion event via the Conversions API (pixel).
| Name | Type | Req | Description |
|---|---|---|---|
| events | string | yes | JSON array of events: [{event_name, event_time, user_data, custom_data, action_source}] |
No output schema declared.
No examples provided.
send_offline_event ~46
Send an offline conversion event to an offline event set.
| Name | Type | Req | Description |
|---|---|---|---|
| event_set_id | string | yes | Offline event set ID |
| events | string | yes | JSON array of offline events |
No output schema declared.
No examples provided.
update_ad ~89
Update an existing ad. Only provided fields will be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| ad_id | string | yes | Ad ID to update |
| creative | string | – | New creative spec as JSON string |
| name | string | – | New ad name |
| status | string | – | New status: ACTIVE, PAUSED, DELETED, ARCHIVED |
| tracking_specs | string | – | New tracking specs as JSON string |
No output schema declared.
No examples provided.
update_ad_account ~80
Update the configured ad account settings. Only provided fields will be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | New account name |
| spend_cap | string | – | Account spend cap in currency cents (e.g. '100000' = $1000.00) |
| timezone_name | string | – | New timezone (e.g. 'America/New_York') |
No output schema declared.
No examples provided.
update_adset ~154
Update an existing ad set. Only provided fields will be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| adset_id | string | yes | Ad set ID to update |
| bid_amount | string | – | New bid amount in currency cents |
| daily_budget | string | – | New daily budget in currency cents |
| end_time | string | – | New end time (ISO 8601) |
| lifetime_budget | string | – | New lifetime budget in currency cents |
| name | string | – | New ad set name |
| start_time | string | – | New start time (ISO 8601) |
| status | string | – | New status: ACTIVE, PAUSED, DELETED, ARCHIVED |
| targeting | string | – | New targeting spec as JSON string |
No output schema declared.
No examples provided.
update_audience ~54
Update an existing custom audience. Only provided fields will be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | Audience ID to update |
| description | string | – | New audience description |
| name | string | – | New audience name |
No output schema declared.
No examples provided.
update_budget_schedule ~74
Update an existing budget schedule. Only provided fields will be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_value | string | – | New budget amount in account currency cents |
| schedule_id | string | yes | Budget schedule ID to update |
| time_end | string | – | New schedule end time |
| time_start | string | – | New schedule start time |
No output schema declared.
No examples provided.
update_campaign ~122
Update an existing campaign. Only provided fields will be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | Campaign ID to update |
| daily_budget | string | – | New daily budget in currency cents |
| lifetime_budget | string | – | New lifetime budget in currency cents |
| name | string | – | New campaign name |
| start_time | string | – | New start time (ISO 8601) |
| status | string | – | New status: ACTIVE, PAUSED, DELETED, ARCHIVED |
| stop_time | string | – | New stop time (ISO 8601) |
No output schema declared.
No examples provided.
update_catalog ~35
Update an existing product catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_id | string | yes | Product catalog ID |
| name | string | – | New catalog name |
No output schema declared.
No examples provided.
update_creative ~59
Update an existing ad creative. Only name and url_tags can be modified after creation.
| Name | Type | Req | Description |
|---|---|---|---|
| creative_id | string | yes | Creative ID to update |
| name | string | – | New creative name |
| url_tags | string | – | New URL tags |
No output schema declared.
No examples provided.
update_experiment ~51
Update an existing experiment (ad study).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New experiment description |
| experiment_id | string | yes | Experiment (ad study) ID |
| name | string | – | New experiment name |
No output schema declared.
No examples provided.
update_product ~100
Update an existing product in a catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | – | Product availability: in stock, out of stock, etc. |
| description | string | – | Product description |
| image_url | string | – | Product image URL |
| name | string | – | Product name |
| price | string | – | Product price (e.g. '9.99 USD') |
| product_id | string | yes | Product ID |
| url | string | – | Product URL |
No output schema declared.
No examples provided.
update_product_set ~50
Update an existing product set.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | JSON string of updated filter rules |
| name | string | – | New product set name |
| set_id | string | yes | Product set ID |
No output schema declared.
No examples provided.
update_rule ~91
Update an existing automated rule.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluation_spec | string | – | JSON string defining updated rule conditions |
| execution_spec | string | – | JSON string defining updated rule actions |
| name | string | – | New rule name |
| rule_id | string | yes | Rule ID |
| schedule_spec | string | – | JSON string defining updated rule schedule |
| status | string | – | Rule status: ENABLED, DISABLED |
No output schema declared.
No examples provided.
upload_feed ~45
Upload/trigger a feed file upload for a product feed.
| Name | Type | Req | Description |
|---|---|---|---|
| feed_id | string | yes | Product feed ID |
| url | string | yes | URL of the feed file to upload |
No output schema declared.
No examples provided.
upload_image ~40
Upload an ad image from a public URL. Returns image hash for use in ad creatives.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public URL of the image to upload |
No output schema declared.
No examples provided.
upload_video ~59
Upload an ad video from a public URL. Returns video ID for use in ad creatives.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Video description |
| file_url | string | yes | Public URL of the video to upload |
| title | string | – | Video title |
No output schema declared.
No examples provided.
What is the io.github.mikusnuz/meta-ads MCP server?
io.github.mikusnuz/meta-ads is an MCP server listed in the public MCP registry as io.github.mikusnuz/meta-ads. MCP server for Meta Marketing API, Facebook & Instagram ad campaign management. This page covers its npm package (@mikusnuz/meta-ads-mcp).
Is the io.github.mikusnuz/meta-ads MCP server safe to use?
io.github.mikusnuz/meta-ads scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.mikusnuz/meta-ads MCP server expose?
io.github.mikusnuz/meta-ads exposes 123 tools: list_campaigns, get_campaign, create_campaign, update_campaign, delete_campaign, and 118 more. Their descriptions and schemas cost roughly 8,605 tokens of context every time the server is loaded.
Is the io.github.mikusnuz/meta-ads MCP server still maintained?
io.github.mikusnuz/meta-ads is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mikusnuz/meta-ads MCP server under?
io.github.mikusnuz/meta-ads declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.