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 (18 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 →
resend_signature_request ~36
Resend 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.
resend_verification_code ~51
Resend the email verification code for a trial account. Use this if the user did not receive the code or it expired.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address used to create the trial account |
No output schema declared.
No examples provided.
revoke_report_schedule_historical_access ~43
Revoke historical access for a report schedule
| Name | Type | Req | Description |
|---|---|---|---|
| report_config_id | number | yes | Report configuration ID |
| schedule_id | number | yes | Schedule ID |
No output schema declared.
No examples provided.
search_adbutler_api ~155
Find AdButler API endpoints by keyword when no specific tool matches what you need. Returns matching endpoints with their HTTP method, path, and a brief summary. Use this when the user asks about a concept that is a *field* rather than a resource — e.g. 'priority', 'pacing', 'frequency cap', 'metadata', 'tracking pixel' — and you can't find a tool that handles it. Then call describe_adbutler_api on the most promising hit, then call_adbutler_api to invoke it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return (default 10, max 50). |
| query | string | yes | Keyword(s) to search for. Single word works best. |
No output schema declared.
No examples provided.
search_product_catalog_items ~48
Search for items in a product catalog
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_id | number | yes | Catalog ID |
| publisher_id | number | yes | Publisher ID |
| query | string | – | Search query string |
No output schema declared.
No examples provided.
serve_ad ~308
Request ad delivery for a zone. Returns the ad(s) that would be served, useful for verifying ad setup. Uses POST /adserve.
| Name | Type | Req | Description |
|---|---|---|---|
| ID | number | yes | Your AdButler account ID |
| _abdk_json | object | – | Data key key-value pairs for data key targeting |
| defer_signing | boolean | – | Defer beacon signing hash generation |
| ip | string | – | IPv4 address for geographic targeting (required for server-side requests) |
| kw | array | – | Keywords for keyword targeting |
| pid | number | – | Page ID for unique delivery/roadblocks (random number, same for all zones on page) |
| place | number | – | Place counter for unique delivery (0, 1, 2, etc.) |
| referrer | string | – | Page URL for URL targeting (required for server-side requests) |
| rf | number | – | Pass 1 to include is_redirectable field in response |
| setID | number | yes | Zone ID to serve an ad from |
| sh | number | – | Screen height for platform targeting |
| size | string | – | Expected ad size (e.g. "300x250") |
| spr | number | – | Screen pixel ratio for platform targeting |
| sw | number | – | Screen width for platform targeting |
| type | string | yes | Response type: "json" for most eligible ad, "jsonr" for all eligible ads ranked |
| ua | string | – | User agent string for platform targeting |
No output schema declared.
No examples provided.
setup_api_key ~49
Configure AdButler with an existing API key. Use this if the user already has an AdButler account and API key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | The AdButler API key |
No output schema declared.
No examples provided.
sync_kogan_stats ~96
Push externally-tracked Kogan stats (impressions, clicks, conversions, quantity sold, sales) into AdButler for a set of ad items over a time window. Kogan marketplace accounts only — requires the Kogan self-serve feature; other accounts receive a feature-not-enabled error.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | Per-ad-item stat rows to record |
| meta | object | yes | Time window the stat rows cover |
No output schema declared.
No examples provided.
test_sftp_connection ~69
Test an SFTP connection with the provided credentials
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | SFTP host |
| password | string | – | SFTP password |
| path | string | – | Remote path |
| port | number | – | SFTP port |
| username | string | – | SFTP username |
No output schema declared.
No examples provided.
unarchive_advertiser ~30
Restore an archived advertiser back to active status
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Archived advertiser ID |
No output schema declared.
No examples provided.
unarchive_campaign ~29
Restore an archived standard campaign back to active status
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Archived campaign ID |
No output schema declared.
No examples provided.
unarchive_channel ~28
Restore an archived channel back to active status
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Archived channel ID |
No output schema declared.
No examples provided.
unarchive_contract ~28
Unarchive a contract (restore from archive)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Archived contract ID |
No output schema declared.
No examples provided.
unarchive_email_zone ~31
Restore an archived email zone back to active status
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Archived email zone ID |
No output schema declared.
No examples provided.
unarchive_publisher ~29
Restore an archived publisher back to active status
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Archived publisher ID |
No output schema declared.
No examples provided.
unarchive_zone ~29
Restore an archived standard zone back to active status
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Archived zone ID |
No output schema declared.
No examples provided.
update_advertiser ~111
Update an existing 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 | |
| id | number | yes | Advertiser ID |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | – | Advertiser name |
| password | string | – | Password for advertiser portal (min 8 chars, must include upper, lower, number) |
No output schema declared.
No examples provided.
update_audience ~60
Update an existing audience in a user database
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | – | Attribute targets defining the audience |
| id | number | yes | Audience ID |
| name | string | – | Audience name |
| user_db_id | number | yes | User database ID |
No output schema declared.
No examples provided.
update_audio_creative ~43
Update an existing audio creative
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Creative description |
| id | number | yes | Creative ID |
| name | string | – | Creative name |
No output schema declared.
No examples provided.
update_beacon_signing_key ~42
Update an existing beacon signing key
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Beacon signing key ID |
| key_name | string | – | Beacon signing key name |
No output schema declared.
No examples provided.
update_bidder ~55
Update an existing bidder
| Name | Type | Req | Description |
|---|---|---|---|
| bid_url | string | – | Bid endpoint URL |
| id | number | yes | Bidder ID |
| name | string | – | Bidder name |
| status | string | – | Bidder status |
No output schema declared.
No examples provided.
update_campaign ~117
Update an existing standard campaign
| Name | Type | Req | Description |
|---|---|---|---|
| advertiser | number | – | Advertiser ID |
| budget | object | – | Budget limits |
| contract | number | – | Contract ID |
| id | number | yes | Campaign ID |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | – | Campaign name |
| roadblock_tags | string | – | Roadblock tag |
| scheduling_source | string | – | Scheduling level |
| targeting_source | string | – | Targeting level |
| trusted_redirect_domains | array | – | Trusted redirect domains |
No output schema declared.
No examples provided.
update_campaign_assignment ~124
Update an existing campaign assignment
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether assignment is active |
| data_key_target | number | – | Data Key Target ID |
| geo_target | number | – | Geo Target ID |
| id | number | yes | Campaign assignment ID |
| keywords | string | – | Comma-separated keywords |
| keywords_match_method | string | – | Keyword matching method |
| list_target | number | – | List Target ID |
| platform_target | number | – | Platform Target ID |
| schedule | number | – | Schedule ID |
| weight | number | – | Relative delivery weight |
No output schema declared.
No examples provided.
update_catalog_ad_item ~100
Update an existing catalog ad item
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_item_identifier | string | – | Unique identifier for the catalog item |
| id | number | yes | Ad item ID |
| location | string | – | Click-through URL |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | – | 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.
update_catalog_zone ~114
Update an existing catalog zone
| Name | Type | Req | Description |
|---|---|---|---|
| advertiser_cost_type | string | – | Billing model |
| auction_type | string | – | Auction type |
| bid_floor_cpc | number | – | CPC bid floor |
| bid_floor_cpm | number | – | CPM bid floor |
| click_cooldown_period | number | – | Click cooldown period in seconds |
| conversion_lookback_period | number | – | Conversion lookback period in seconds |
| id | number | yes | Catalog zone ID |
| name | string | – | Zone name |
No output schema declared.
No examples provided.
update_channel ~40
Update an existing channel
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Channel ID |
| name | string | – | Channel name |
| priority | string | – | Serving priority |
No output schema declared.
No examples provided.
update_contact ~50
Update an existing contact
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Contact email address | |
| id | number | yes | Contact ID |
| name | string | – | Contact name |
| notes | string | – | Additional notes |
No output schema declared.
No examples provided.
update_contract ~114
Update an existing contract
| Name | Type | Req | Description |
|---|---|---|---|
| advertiser | number | – | Advertiser ID |
| description | string | – | Contract description |
| end_at | string | – | Contract end date (YYYY-MM-DD) |
| id | number | yes | Contract ID |
| name | string | – | Contract name |
| payment_due_date | string | – | Payment due date (YYYY-MM-DD) |
| rate | number | – | Contract rate |
| start_at | string | – | Contract start date (YYYY-MM-DD) |
| status | string | – | Contract status |
No output schema declared.
No examples provided.
update_contract_document ~43
Update an existing contract document
| Name | Type | Req | Description |
|---|---|---|---|
| contract_id | number | yes | Contract ID |
| id | number | yes | Document ID |
| name | string | – | Document name |
No output schema declared.
No examples provided.
update_contract_template ~34
Update an existing contract template
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Contract template ID |
| name | string | – | Template name |
No output schema declared.
No examples provided.
update_creative ~42
Update an existing image creative
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Creative description |
| id | number | yes | Creative ID |
| name | string | – | Creative name |
No output schema declared.
No examples provided.
update_custom_html_ad_item ~172
Update an existing custom HTML ad item
| Name | Type | Req | Description |
|---|---|---|---|
| custom_html | string | – | The HTML content |
| expand_horizontal_direction | string | – | Horizontal expand direction |
| expand_vertical_direction | string | – | Vertical expand direction |
| height | number | – | Ad height in pixels |
| html_content_below | string | – | HTML content below the ad item |
| id | number | yes | Ad item ID |
| location | string | – | Click-through URL |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | – | 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 |
No output schema declared.
No examples provided.
update_custom_report ~149
Update an existing report configuration
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | – | Columns to include |
| date | object | – | Date configuration |
| 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 |
| id | number | yes | Report configuration ID |
| name | string | – | Report name |
| period | string | – | Data grouping period |
| require_channel_stats | boolean | – | Only include stats from channel-served ads |
| type | string | – | Report type |
No output schema declared.
No examples provided.
update_data_key ~46
Update an existing data key
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Data key ID |
| name | string | – | Data key name |
| type | string | – | Data key value type |
No output schema declared.
No examples provided.
update_data_key_target ~50
Update an existing data key target
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Data key target ID |
| name | string | – | Data key target name |
| target | string | – | JSON formatted target logic |
No output schema declared.
No examples provided.
update_data_list ~36
Update an existing data list
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Data list ID |
| label | string | – | Data list label/name |
No output schema declared.
No examples provided.
update_day_parting ~103
Update an existing day parting rule
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Day parting ID |
| 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 |
| use_member_timezone | boolean | – | If true, use account timezone; if false, use viewer timezone |
No output schema declared.
No examples provided.
update_demand_endpoint ~203
Update an existing demand endpoint
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_sizes | array | – | Allowed zone sizes |
| bid_floor | number | – | Default CPM bid floor |
| default_parameters | object | – | Default parameters |
| demand_source | number | – | Demand Source ID |
| filter_type | string | – | Zone filtering type |
| filtered_vast_zones | array | – | VAST zone IDs for filter list |
| filtered_zones | array | – | Zone IDs for filter list |
| geo_target | number | – | Geo target ID |
| id | number | yes | Demand endpoint ID |
| markup_percent | number | – | Markup percent |
| name | string | – | Demand endpoint name |
| native_json_encoded | boolean | – | Whether native JSON should be encoded |
| priority | string | – | Serving priority |
| revenue_share | number | – | Revenue share percentage |
| status | string | – | Whether to send bid requests |
| supported_formats | array | – | Supported ad formats |
No output schema declared.
No examples provided.
update_demand_source ~108
Update an existing demand source
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Demand source ID |
| name | string | – | Demand source name |
| 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 |
No output schema declared.
No examples provided.
update_email_zone ~119
Update an existing email zone
| Name | Type | Req | Description |
|---|---|---|---|
| auction_tie_break | string | – | Tie-breaking method |
| height | number | – | Zone height in pixels |
| id | number | yes | Email zone ID |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | – | 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 | – | Zone width in pixels |
No output schema declared.
No examples provided.
update_event_log_upload_config ~96
Update an existing 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") |
| id | number | yes | Upload configuration ID |
| name | string | – | Configuration name |
No output schema declared.
No examples provided.
update_geo_target ~85
Update an existing geo target
| Name | Type | Req | Description |
|---|---|---|---|
| areas | array | – | Array of geographic areas |
| id | number | yes | Geo target ID |
| inclusive | boolean | – | If true, target users IN these areas; if false, EXCLUDE |
| name | string | – | Geo target name |
| range | number | – | Radius range |
| unit | string | – | Distance unit |
No output schema declared.
No examples provided.
update_image_ad_item ~184
Update an existing image ad item
| Name | Type | Req | Description |
|---|---|---|---|
| creative | number | – | Image creative ID |
| creative_url | string | – | URL to image file |
| height | number | – | Ad height in pixels |
| 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 |
| id | number | yes | Ad item ID |
| location | string | – | Click-through URL |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | – | 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 |
No output schema declared.
No examples provided.
update_kogan_product_category ~90
Update the category and category slug of a Kogan marketplace product. Kogan marketplace accounts only — requires the Kogan self-serve feature; other accounts receive a feature-not-enabled error.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | New category name |
| category_slug | string | yes | New category slug |
| seller_id | string | yes | Kogan seller ID |
| sku | string | yes | Product SKU |
No output schema declared.
No examples provided.
update_list_target ~62
Update an existing list target
| Name | Type | Req | Description |
|---|---|---|---|
| data_list | number | – | Data list ID |
| id | number | yes | List target ID |
| inclusive | boolean | – | If true, inclusion; if false, exclusion |
| label | string | – | List target name |
No output schema declared.
No examples provided.
update_manager ~328
Update an existing manager
| Name | Type | Req | Description |
|---|---|---|---|
| can_assign_campaigns_directly | boolean | – | Can assign campaigns directly |
| can_manage_admin_api_access | boolean | – | Can manage API keys |
| can_manage_bidders | boolean | – | Can manage bidders |
| can_manage_billing | boolean | – | Can manage billing |
| can_manage_contracts | boolean | – | Can manage contracts |
| can_manage_data_keys | boolean | – | Can manage data keys |
| can_manage_links | boolean | – | Can manage tracking links |
| can_manage_media | boolean | – | Can manage creatives and media groups |
| can_manage_native_ad_templates | boolean | – | Can manage native templates |
| can_manage_product_db | boolean | – | Can manage product catalogs |
| can_manage_programmatic | boolean | – | Can manage programmatic |
| can_manage_self_serve | boolean | – | Can manage Self-Serve |
| can_manage_targets | boolean | – | Can manage targets |
| can_manage_tickets | boolean | – | Can manage tickets |
| can_manage_users | boolean | – | Can manage users |
| string | – | Manager email address | |
| id | number | yes | Manager ID |
| is_enabled | boolean | – | Whether the manager account is enabled |
| name | string | – | Manager name |
| notes | string | – | Notes about the manager |
| password | string | – | Login password |
| position | string | – | Manager position |
| publisher_access | string | – | Publisher access level |
| publisher_access_list | array | – | Publisher IDs for specific access |
| statistics_access | string | – | Statistics access level |
No output schema declared.
No examples provided.
update_media_group ~35
Update an existing media group
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Media group ID |
| name | string | – | Media group name |
No output schema declared.
No examples provided.
update_native_ad_item ~120
Update an existing native ad item
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Ad item ID |
| location | string | – | Click-through URL |
| metadata | object | – | Custom metadata key-value pairs |
| name | string | – | Ad item name |
| template | number | – | Native template ID |
| tracking_pixel | string | – | Third-party tracking pixel URL |
| tracking_pixels | array | – | Array of tracking pixel URLs |
| trusted_redirect_domains | array | – | Trusted redirect domains |
| variables | object | – | Template variables as key-value pairs |
No output schema declared.
No examples provided.
update_native_template ~67
Update an existing native template. Variables uses add/remove format for updates.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Native template ID |
| name | string | – | Template name |
| raw_html | string | – | HTML template content with variable placeholders |
| variables | object | – | Variables to add/remove |
No output schema declared.
No examples provided.
update_ortb_native_data_asset ~67
Update an existing data asset for an ORTB native template
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Data asset ID |
| len | number | – | Max length |
| template_id | number | yes | ORTB native template ID |
| type | number | – | Data asset type |
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.