AdButler
NPM · @ADBUTLER/MCP-SERVER · 3 COMPONENTS
Manage AdButler campaigns, zones, ad items, VAST, and reports from Claude, ChatGPT, and Cursor.
Available components
Last scanned (17 hours ago)
Scores higher than 60% of npm servers
Category Marketing and SEO
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 36354 tokens (~57/item across 628 items; 628 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 105 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_advertiser" 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 628 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 9 Nov 26 +5
- Source repository: unverified → pass ▲ security
- 8 Nov 26 −5
- Provenance: pass → unverified ▼ security
- 6 Nov 26 0
- Stability: 0.97 → pass security
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.90 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ 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 10 Nov 2026 · Analysed npm/@adbutler/mcp-server@2.8.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
add_user_list_attribute_values ~65
Add values to a list attribute for a user
| Name | Type | Req | Description |
|---|---|---|---|
| list_attribute_name | string | yes | List attribute name |
| user_db_id | number | yes | User database ID |
| user_id | string | yes | User ID |
| values | array | – | Values to add |
No output schema declared.
No examples provided.
archive_advertiser ~32
Archive an advertiser (soft-delete, can be restored later)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Advertiser ID |
No output schema declared.
No examples provided.
archive_campaign ~30
Archive a standard campaign (soft-delete, can be restored later)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Campaign ID |
No output schema declared.
No examples provided.
archive_channel ~29
Archive a channel (soft-delete, can be restored later)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Channel ID |
No output schema declared.
No examples provided.
archive_contract ~29
Archive a contract (soft-delete, can be restored later)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Contract ID |
No output schema declared.
No examples provided.
archive_email_zone ~24
Archive an email zone
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Email zone ID |
No output schema declared.
No examples provided.
archive_publisher ~30
Archive a publisher (soft-delete, can be restored later)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Publisher ID |
No output schema declared.
No examples provided.
archive_zone ~30
Archive a standard zone (soft-delete, can be restored later)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Zone ID |
No output schema declared.
No examples provided.
bulk_create_product_sources ~41
Bulk create product sources for a publisher
| Name | Type | Req | Description |
|---|---|---|---|
| publisher_id | number | yes | Publisher ID |
| sources | array | – | Array of source objects to create |
No output schema declared.
No examples provided.
bulk_upload_add_data_list ~40
Bulk add entries to a data list
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | CSV data to add |
| id | number | yes | Data list ID |
No output schema declared.
No examples provided.
bulk_upload_product_catalog ~38
Bulk upload items to a product catalog
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_id | number | yes | Catalog ID |
| publisher_id | number | yes | Publisher ID |
No output schema declared.
No examples provided.
bulk_upload_remove_data_list ~40
Bulk remove entries from a data list
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | CSV data to remove |
| id | number | yes | Data list ID |
No output schema declared.
No examples provided.
bulk_upload_replace_data_list ~43
Bulk replace all entries in a data list
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | CSV data to replace list with |
| id | number | yes | Data list ID |
No output schema declared.
No examples provided.
bulk_upload_replace_user_db ~33
Bulk upload to replace all user data in a user database
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | User database ID |
No output schema declared.
No examples provided.
call_adbutler_api ~203
Call any AdButler API endpoint directly. Use this only when no specific tool wraps the endpoint you need. The session's configured API key is used automatically — do NOT pass an api_key argument. Substitute path placeholders via path_params: e.g. path="/campaigns/{id}", path_params={ "id": 123 } → /campaigns/123.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON request body (for POST/PUT/PATCH). |
| method | string | yes | HTTP method, e.g. "GET", "POST", "PUT", "DELETE". |
| path | string | yes | Endpoint path with `{placeholder}` syntax for path params, exactly as returned by search_adbutler_api (e.g. "/campaigns/{id}"). |
| path_params | object | – | Map of path placeholder names to values, e.g. { "id": 123 }. |
| query_params | object | – | Query string parameters appended to the URL. |
No output schema declared.
No examples provided.
campaign_bulk_create_catalog_ad_items ~46
Bulk create catalog ad items in a campaign
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | number | yes | Campaign ID |
| items | array | yes | Array of catalog ad item objects to create |
No output schema declared.
No examples provided.
campaign_bulk_delete_catalog_ad_items ~46
Bulk delete catalog ad items from a campaign
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | number | yes | Campaign ID |
| items | array | yes | Array of catalog ad item IDs to delete |
No output schema declared.
No examples provided.
cancel_signature_request ~35
Cancel a signature request
| Name | Type | Req | Description |
|---|---|---|---|
| contract_id | number | yes | Contract ID |
| request_id | number | yes | Signature request ID |
No output schema declared.
No examples provided.
convert_native_to_image ~32
Convert a native ad item to an image ad item
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Native ad item ID |
No output schema declared.
No examples provided.
create_advertiser ~101
Create a new advertiser
| Name | Type | Req | Description |
|---|---|---|---|
| can_add_ad_items | boolean | – | Whether advertiser can submit advertisements for scheduling |
| can_change_password | boolean | – | Whether advertiser can change password |
| string | – | Contact email | |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | yes | Advertiser name |
| password | string | – | Password for advertiser portal (min 8 chars, must include upper, lower, number) |
No output schema declared.
No examples provided.
create_audience ~72
Create a new audience in a user database
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | – | Attribute targets defining the audience (e.g. { "gender": { "operator": "=", "operand": "male" } }) |
| name | string | – | Audience name |
| user_db_id | number | yes | User database ID |
No output schema declared.
No examples provided.
create_audio_creative ~51
Create a new audio creative. The API uses multipart file upload.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Creative description |
| group | number | yes | Media group ID |
| name | string | – | Creative name |
No output schema declared.
No examples provided.
create_beacon_signing_key ~31
Create a new beacon signing key
| Name | Type | Req | Description |
|---|---|---|---|
| key_name | string | yes | Beacon signing key name |
No output schema declared.
No examples provided.
create_bidder ~45
Create a new bidder
| Name | Type | Req | Description |
|---|---|---|---|
| bid_url | string | – | Bid endpoint URL |
| name | string | yes | Bidder name |
| status | string | – | Bidder status |
No output schema declared.
No examples provided.
create_campaign ~144
Create a new standard campaign
| Name | Type | Req | Description |
|---|---|---|---|
| advertiser | number | – | Advertiser ID |
| budget | object | – | Budget limits (daily/weekly/monthly/lifetime) |
| contract | number | – | Contract ID (requires Contract Management add-on) |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | yes | Campaign name |
| roadblock_tags | string | – | Tag to link campaign to a roadblock |
| scheduling_source | string | – | Whether scheduling is set at campaign or ad item level |
| targeting_source | string | – | Whether targeting is set at campaign or ad item level |
| trusted_redirect_domains | array | – | Array of trusted redirect domains |
No output schema declared.
No examples provided.
create_campaign_assignment ~179
Create a new campaign assignment (assign an ad item to a campaign)
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether assignment is active (defaults to true) |
| advertisement | object | yes | Advertisement object with id and type |
| campaign | object | yes | Campaign object with id and type |
| data_key_target | number | – | Data Key Target ID |
| geo_target | number | – | Geo Target ID (only if campaign targeting_source is "AD_ITEM") |
| keywords | string | – | Comma-separated keywords for targeting |
| keywords_match_method | string | – | Keyword matching method |
| list_target | number | – | List Target ID |
| platform_target | number | – | Platform Target ID |
| schedule | number | – | Schedule ID (only if campaign scheduling_source is "AD_ITEM") |
| weight | number | – | Relative delivery weight (defaults to 1) |
No output schema declared.
No examples provided.
create_catalog_ad_item ~100
Create a new catalog ad item
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_id | number | yes | Catalog ID |
| catalog_item_identifier | string | yes | Unique identifier for the catalog item |
| location | string | – | Click-through URL |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | yes | Ad item name |
| tracking_pixel | string | – | Third-party tracking pixel URL |
| tracking_pixels | array | – | Array of tracking pixel URLs |
No output schema declared.
No examples provided.
create_catalog_zone ~152
Create a new catalog zone for product/retail ad serving
| Name | Type | Req | Description |
|---|---|---|---|
| advertiser_cost_type | string | – | Billing model |
| auction_type | string | – | Auction type |
| bid_floor | number | – | Default bid floor |
| bid_floor_cpc | number | – | CPC bid floor |
| bid_floor_cpm | number | – | CPM bid floor |
| catalog_id | number | yes | Catalog ID |
| click_cooldown_period | number | – | Click cooldown period in seconds (1-86400) |
| conversion_lookback_period | number | – | Conversion lookback period in seconds (1-7776000) |
| name | string | yes | Zone name |
| publisher | number | – | Publisher ID |
No output schema declared.
No examples provided.
create_channel ~59
Create a new channel
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Channel name |
| priority | string | – | Serving priority (default: standard) |
| use_share_of_voice | boolean | – | Whether to use share of voice as serving strategy (false = use weight) |
No output schema declared.
No examples provided.
create_channel_zone_assignment ~39
Assign a zone to a channel
| Name | Type | Req | Description |
|---|---|---|---|
| channel | number | yes | Channel ID |
| zone | object | yes | Zone object with id and type |
No output schema declared.
No examples provided.
create_contact ~52
Create a new contact
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Contact email address (must be unique) | |
| name | string | yes | Contact name (full name recommended) |
| notes | string | – | Additional notes about the contact |
No output schema declared.
No examples provided.
create_contract ~109
Create a new contract
| Name | Type | Req | Description |
|---|---|---|---|
| advertiser | number | yes | Advertiser ID |
| description | string | – | Contract description |
| end_at | string | – | Contract end date (YYYY-MM-DD) |
| name | string | yes | Contract name |
| payment_due_date | string | – | Payment due date (YYYY-MM-DD) |
| rate | number | – | Contract rate (in account currency) |
| start_at | string | – | Contract start date (YYYY-MM-DD) |
| status | string | – | Contract status |
No output schema declared.
No examples provided.
create_contract_document ~51
Create a new document for a contract
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | string | – | JSON-encoded object with name, admin_executed, vendor_executed fields |
| contract_id | number | yes | Contract ID |
No output schema declared.
No examples provided.
create_contract_document_from_template ~39
Create a contract document from a template
| Name | Type | Req | Description |
|---|---|---|---|
| contract_id | number | yes | Contract ID |
| template_id | number | – | Template ID |
No output schema declared.
No examples provided.
create_contract_payment ~53
Create a new payment for a contract
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount paid (can be negative for refunds) |
| contract_id | number | yes | Contract ID |
| note | string | – | Payment note or description |
No output schema declared.
No examples provided.
create_contract_template ~120
Create a new contract template. Requires name, file, attributes (JSON string), email_subject, and email_body.
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | string | yes | JSON-encoded object containing name, email_subject, email_body, and optionally signing_service, basic_inputs, contract_column_inputs, signers |
| email_body | string | yes | Email body text when sending for signature |
| email_subject | string | yes | Email subject line when sending for signature |
| file | string | yes | URL or path to the contract template file |
| name | string | yes | Template name |
No output schema declared.
No examples provided.
create_creative ~59
Create a new image creative. The API uses multipart file upload — pass the media group ID and file attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Creative description |
| group | number | yes | Media group ID |
| name | string | – | Creative name |
No output schema declared.
No examples provided.
create_custom_html_ad_item ~174
Create a new custom HTML ad item
| Name | Type | Req | Description |
|---|---|---|---|
| custom_html | string | yes | The HTML content of the ad item |
| expand_horizontal_direction | string | – | Horizontal expand direction |
| expand_vertical_direction | string | – | Vertical expand direction |
| height | number | – | Ad height in pixels (0 for flexible) |
| html_content_below | string | – | HTML content below the ad item |
| location | string | – | Click-through URL |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | yes | Ad item name |
| tracking_pixel | string | – | Third-party tracking pixel URL |
| tracking_pixels | array | – | Array of tracking pixel URLs |
| trusted_redirect_domains | array | – | Trusted redirect domains |
| width | number | – | Ad width in pixels (0 for flexible) |
No output schema declared.
No examples provided.
create_custom_report ~207
Create a new report configuration
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | – | Columns to include: impressions, eligible, viewable, clicks, conversions, ctr, cvr, e_cpm, e_cpc, e_cpa, cost, payout, revenue |
| date | object | yes | Date configuration (either preset or start+end required) |
| exclude_campaign_ad_items | boolean | – | Exclude ad items in campaigns |
| exclude_channel_stats | boolean | – | Exclude stats from channel-served ads |
| exclude_publisher_ad_items | boolean | – | Exclude ad items directly in zones |
| filters | object | – | Filter criteria: { publishers: [...], advertisers: [...], zones: [...], campaigns: [...], ad_items: [...], channels: [...] } |
| name | string | yes | Report name |
| period | string | yes | Data grouping period |
| require_channel_stats | boolean | – | Only include stats from channel-served ads |
| type | string | yes | Report type |
No output schema declared.
No examples provided.
create_data_key ~48
Create a new data key for custom targeting
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Data key name (max 32 chars, must be unique) |
| type | string | yes | Data key value type |
No output schema declared.
No examples provided.
create_data_key_target ~71
Create a new data key target (targeting rule)
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Data key target name |
| target | string | yes | JSON formatted target logic, e.g. ["OR", {"my_number": {"=": "5"}}, {"my_string": {"=": "test"}}] |
No output schema declared.
No examples provided.
create_data_list ~26
Create a new data list
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | Data list label/name |
No output schema declared.
No examples provided.
create_day_parting ~146
Create a new day parting rule for time-of-day targeting. Ranges is an object with day names as keys and arrays of time range strings (e.g. "09:00:00-17:00:00") as values.
| Name | Type | Req | Description |
|---|---|---|---|
| is_template | boolean | – | If true, shown in UI when creating/editing schedules |
| name | string | – | Day parting name |
| ranges | object | – | Object mapping day names (monday-sunday) to arrays of time ranges like "09:00:00-17:00:00" |
| use_member_timezone | boolean | – | If true, use account timezone; if false, use viewer timezone |
No output schema declared.
No examples provided.
create_demand_endpoint ~250
Create a new demand endpoint
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_sizes | array | – | Allowed zone sizes (e.g. ["300x250", "728x90"]) |
| bid_floor | number | – | Default CPM bid floor |
| default_parameters | object | yes | Default parameters for the endpoint (e.g. { url: "https://..." }) |
| demand_source | number | yes | Demand Source ID this endpoint belongs to |
| filter_type | string | – | Zone filtering type |
| filtered_vast_zones | array | – | VAST zone IDs for the filter list |
| filtered_zones | array | – | Zone IDs for the filter list |
| geo_target | number | – | Geo target ID for geographic targeting |
| markup_percent | number | – | Markup percent applied to zone bid floor |
| name | string | yes | Demand endpoint name |
| native_json_encoded | boolean | – | Whether native JSON should be encoded |
| priority | string | – | Serving priority |
| revenue_share | number | – | Revenue share percentage paid to publisher |
| status | string | – | Whether to send bid requests (default: active) |
| supported_formats | array | yes | Supported ad formats: "display", "native", "video" |
No output schema declared.
No examples provided.
create_demand_source ~181
Create a new demand source
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Demand source name |
| network | string | yes | Network type: 'adview', 'aerserv', 'inmobi', 'inneractive', 'loopme', 'mobilefuse', 'onebyaol', 'pubmatic', 'pubnative', 'smaato', 'startapp', 'tappx', 'consumable', 'bidphysics', or 'openrtb' |
| spend_limit | number | – | Spend limit amount |
| spend_limit_end | string | – | Spend limit end date (ISO-8601) |
| spend_limit_period | string | – | Spend limit reset interval |
| spend_limit_start | string | – | Spend limit start date (ISO-8601) |
| status | string | – | Whether to send bid requests (default: active) |
No output schema declared.
No examples provided.
create_email_zone ~117
Create a new email zone for serving ads in email newsletters
| Name | Type | Req | Description |
|---|---|---|---|
| auction_tie_break | string | – | Tie-breaking method for auctions |
| height | number | yes | Zone height in pixels |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | yes | Zone name |
| publisher | number | – | Publisher ID |
| rotate_timer | object | – | Period after which user sees a new ad |
| uid_rotate | boolean | – | Serve different ads per user |
| width | number | yes | Zone width in pixels |
No output schema declared.
No examples provided.
create_event_log_upload_config ~86
Create a new event log upload configuration
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | number | – | SFTP connection ID to use for upload |
| enabled | boolean | – | Whether the upload configuration is enabled |
| format | string | – | Log file format |
| frequency | string | – | Upload frequency (e.g. "daily", "hourly") |
| name | string | – | Configuration name |
No output schema declared.
No examples provided.
create_geo_target ~115
Create a new geo target for geographic targeting. Areas is an array of objects with continent, country (2-letter code), region, city fields.
| Name | Type | Req | Description |
|---|---|---|---|
| areas | array | yes | Array of geographic areas to target |
| inclusive | boolean | – | If true, target users IN these areas; if false, EXCLUDE these areas |
| name | string | yes | Geo target name |
| range | number | – | Radius range for geo-fencing (only applies when targeting a city) |
| unit | string | – | Distance unit for range |
No output schema declared.
No examples provided.
create_image_ad_item ~212
Create a new image ad item (banner)
| Name | Type | Req | Description |
|---|---|---|---|
| creative | number | – | Image creative ID (mutually exclusive with creative_url) |
| creative_url | string | – | URL to image file — PNG, JPEG, or GIF (mutually exclusive with creative) |
| height | number | – | Ad height in pixels (defaults to 0) |
| html_alt_text | string | – | Alt text for the image |
| html_content_below | string | – | HTML content below the ad item |
| html_target | string | – | Window/frame for destination URL (e.g. "_blank") |
| location | string | – | Click-through URL |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | yes | Ad item name |
| tracking_pixel | string | – | Third-party tracking pixel URL |
| tracking_pixels | array | – | Array of tracking pixel URLs |
| trusted_redirect_domains | array | – | Trusted redirect domains |
| width | number | – | Ad width in pixels (defaults to 0) |
No output schema declared.
No examples provided.
create_list_target ~68
Create a new list target (inclusion/exclusion using a data list)
| Name | Type | Req | Description |
|---|---|---|---|
| data_list | number | – | Data list ID containing the values to target |
| inclusive | boolean | – | If true, inclusion target; if false, exclusion target |
| label | string | yes | List target name |
No output schema declared.
No examples provided.
How do I install the AdButler MCP server?
AdButler runs locally as an npm package, launched with npx -y @adbutler/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @adbutler/mcp-server
claude mcp add com-adbutler-mcp-server -- npx -y @adbutler/mcp-server
What is the AdButler MCP server?
AdButler is an MCP server listed in the public MCP registry as com.adbutler/mcp-server. Manage AdButler campaigns, zones, ad items, VAST, and reports from Claude, ChatGPT, and Cursor. This page covers its npm package (@adbutler/mcp-server).
Is the AdButler MCP server safe to use?
AdButler scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 10 November 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 AdButler MCP server expose?
AdButler exposes 628 tools: list_advertisers, get_advertiser, create_advertiser, update_advertiser, delete_advertiser, and 623 more. Their descriptions and schemas cost roughly 36,354 tokens of context every time the server is loaded.
Is the AdButler MCP server still maintained?
AdButler is still listed as active in the MCP registry. We last reached this channel on 10 November 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 AdButler MCP server under?
AdButler declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the AdButler MCP server?
VerifyMCP ran 16 checks on AdButler, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.