Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
RevClamp AdPulse (Google Ads Transparency MCP) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
12
tools declared
local
runs on your machine
—
downloads a day
What it does
Google Ads Transparency Center advertiser & creative intelligence MCP server by RevClamp.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user revclamp-adpulse-google-ads-transparency-mcp '--' npx -y @revclamp/google-ads-transparency-mcp-actor
# 2 — ask your agent for something these tools do
# revclamp_audit_revenue_leakage, revclamp_evaluate_ghost_usage, revclamp_stage_stripe_dispute_ce3 and 9 more
RevClamp AdPulse (Google Ads Transparency MCP) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
REAll 2 servers
revclamp2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts RevClamp AdPulse (Google Ads Transparency MCP) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user revclamp-adpulse-google-ads-transparency-mcp '--' npx -y @revclamp/google-ads-transparency-mcp-actorReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Runs a deterministic 90-day B2B revenue leakage and Visa CE 3.0 readiness audit across caller-supplied Stripe subscriptions (2025-03-31.basil item-level periods), usage events, and disputes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customers | array | no | Array of Stripe customer objects with subscriptions ({ id, subscriptions: { data, has_more } }). |
| usageEvents | array | no | Array of metered API/SaaS usage events ({ customer_id, event_name, occurred_at }). |
| disputes | array | no | Optional array of Stripe dispute objects. |
| dunningGracePeriodDays | integer | no | — |
| costPerEventCents | integer | no | — |
| demo | boolean | no | Set true only to generate a labeled sample preview when customers/usageEvents are omitted. |
Evaluates whether a metered API/SaaS usage event belongs to an entitled customer or represents post-cancellation / post-grace ghost usage under Stripe 2025-03-31.basil.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customerId | string | no | Optional Stripe customer identifier to evaluate (e.g. 'cus_9s6XKzkNRiz8i3', max 64 chars). |
| subscriptions | yes | Stripe subscriptions list envelope ({ data: [...], has_more: false }) or raw array of subscription objects. | |
| usageEvent | object | no | Optional metered usage event with customer_id, event_name, occurred_at (or occurred_at_sec). |
| subscriptionsHasMore | boolean | no | Pagination completeness flag (must be false when passing a raw subscriptions array). |
| dunningGracePeriodDays | integer | no | — |
| usageTimestampSec | integer | no | Optional Unix epoch timestamp in integer seconds when the usage event occurred. |
| occurredAtSec | integer | no | Optional alias for usageTimestampSec. |
| demo | boolean | no | — |
Evaluates Visa Compelling Evidence 3.0 (CE 3.0) 120d-365d historical footprint overlap (IP / device_id) and builds a non-destructive access_activity_log draft (<= 18,000 UTF-16 code units, submit: false).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| disputeId | string | no | — |
| customerId | string | no | — |
| disputeReason | string | no | — |
| existingAccessActivityLog | string | no | — |
| existingUncategorizedText | string | no | — |
| disputedTransaction | object | no | — |
| priorTransactions | array | no | — |
| usageEvents | array | no | — |
| demo | boolean | no | Set true only to generate a labeled sample preview when usageEvents is omitted. |
Normalizes 27 EU member states + Northern Ireland (XI) B2B VAT IDs (auto-converting Greece GR -> EL) and checks cross-border reverse-charge format eligibility locally (or simulates VIES states when demo: true).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sellerCountry | string | no | — |
| buyerVatId | string | yes | — |
| supplyType | string | no | Cross-border transaction supply category: 'GOODS' (Directive 2006/112/EC Art. 138(1) intra-Community supply, default; permitted for Northern Ireland XI under Windsor Framework) or 'SERVICES' (Directiv |
| viesMode | string | no | — |
| consultationNumber | string | no | — |
| demo | boolean | no | Required when using simulated viesMode values (VALID, INVALID, MS_UNAVAILABLE, GLOBAL_MAX_CONCURRENT_REQ) in local mode. |
Reconciles Shopify Plus B2B Net-15/30/60 wholesale invoices, upfront deposits, credit notes, and rounding tolerances using integer EUR-cent double-entry accounting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orderId | string | no | — |
| totalOrderCents | integer | no | — |
| orderTotalCents | integer | no | — |
| paidAmountCents | integer | yes | — |
| creditNoteCents | integer | no | — |
| creditNotesCents | integer | no | — |
| requiredDepositCents | integer | no | — |
| requiredDepositPercent | integer | no | — |
| paymentTermsDays | integer | no | — |
| daysElapsedSinceInvoice | integer | no | — |
| toleranceCents | integer | no | — |
| demo | boolean | no | — |
Generates and verifies raw-UTF8 HMAC-SHA256 webhook signatures for Stripe (Stripe-Signature t=,v1=), Shopify (X-Shopify-Hmac-Sha256 base64), and RevClamp (X-RevClamp-Signature) with 300s timestamp replay protection.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | no | — |
| secret | string | no | — |
| secrets | array | no | — |
| rawPayload | string | no | — |
| signatureHeader | string | no | — |
| timestampSec | integer | no | — |
| toleranceSec | integer | no | — |
| demo | boolean | no | — |
Calculates monthly and annual B2B margin savings in integer USD cents comparing 0% take-rate flat pricing against 25%-30% chargeback contingency agencies and recommends the optimal tier.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monthlyWonDisputeUsd | number | no | — |
| monthlyGhostBleedUsd | number | no | — |
| contingencyTakeRatePercent | number | no | — |
| monthlyUsageEvents | integer | no | — |
Simulates out-of-order and duplicate subscription lifecycle webhooks against a 72-hour deduplication Set and monotonic createdSec watermark vs. a naive arrival-order handler.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scenarioPreset | string | no | — |
| nowSec | integer | no | — |
| idempotencyWindowSec | integer | no | — |
| events | array | no | — |
| demo | boolean | no | — |
Lints Stripe dispute evidence[access_activity_log] payloads against the 18,000 UTF-16 code unit ceiling, non-destructive RevClamp CE 3.0 block markers, merchant note preservation, 17,922/17,920-char fixed wrapper capacity threshold (SKIP_POST_PRESERVE_DRAFT), and Visa CE 3.0 two-identifier overlap.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| preset | string | no | Scenario preset to evaluate when custom evidenceLogText / accessActivityLog is omitted (default: 'valid_ce3_non_destructive'). |
| existingMerchantNotes | string | no | Existing human AE/support notes inside evidence[access_activity_log] that must be preserved. |
| evidenceLogText | string | no | Merged or candidate Stripe dispute evidence[access_activity_log] payload evaluated against the 18,000 UTF-16 code unit ceiling and non-destructive delimiter markers. |
| accessActivityLog | string | no | Alias for evidenceLogText representing Stripe dispute evidence[access_activity_log] payload. |
| priorMatchedCount | integer | no | Number of prior undisputed Stripe charges (120d-365d old) with matching customer_id and IP/device fingerprint (Visa CE 3.0 requires >= 2). |
| hasIpMatch | boolean | no | Whether the disputed charge IPv4/IPv6 address matches the historical undisputed charges. |
| hasDeviceMatch | boolean | no | Whether the disputed charge device_id fingerprint matches the historical undisputed charges. |
| disputedTransaction | object | no | Optional disputed Stripe charge/transaction metadata evaluated against priorTransactions for Visa CE 3.0 qualification. |
| priorTransactions | array | no | Optional historical undisputed Stripe charges (120d-365d prior) evaluated for Visa CE 3.0 two-identifier overlap. |
| demo | boolean | no | Set true to lint a sample preset fixture when evidenceLogText / accessActivityLog is omitted. |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install RevClamp AdPulse (Google Ads Transparency MCP) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 1.0.5 · scanned 5 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest510042a22f21db694ff89af8229b4027e1e9914b5a3debe1dba5361b626d5c06
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (3 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_google_ads_transparency | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| resolve_google_ads_advertiser | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_google_ads_creative_detail | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest510042a22f21db69
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.5. Pin a release below and the command asks for exactly that one.
1.0.5
5 Nov 2026
latestNo release note was published with this version.
1.0.3
5 Nov 2026
No release note was published with this version.
1.0.2
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish RevClamp AdPulse (Google Ads Transparency MCP) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.