Atlas Data: Ads, Jobs & Trends

io.github.AtlasDataDenmarkPublished by GitHub account AtlasDataDenmarkv1.0.0Updated Nov 5, 2026

Google Trends, Google Ads Transparency, LinkedIn & TikTok ad libraries, Google Jobs via Apify.

The publisher's own server: Red Atlas Api

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Remote Apify-hosted MCP server that gives an assistant access to Google Trends, ad libraries and Google Jobs data.

What you can do
  • Retrieve Google Trends data through Apify actors.
  • Look up ads from Google Ads Transparency, LinkedIn and TikTok ad libraries.
  • Search Google Jobs listings.
  • Runs are executed on the Apify platform under the connected account.
When to use it
Useful when you want an assistant to pull search-trend signals, competitor or industry ad creatives, or job postings without building your own scrapers.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com; no local package. Authentication is required: an Apify API token sent as an Authorization header in the form Bearer token, or Apify OAuth if the client supports it. An Apify account is needed for billing.
Before you install
The Authorization header carries an Apify API token, so treat it as a secret. Runs are billed to your Apify account, so usage costs money. Queries and results pass through Apify and the underlying data sources.

Installation

In SourceWeft

  1. Open Atlas Data: Ads, Jobs & Trends in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.AtlasDataDenmark%2Fatlas-data/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "atlas-data-ads-jobs-trends": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=atlasdata/google-trends-scraper-reliable,atlasdata/google-ads-transparency-scraper-reliable,atlasdata/linkedin-ad-library-scraper-reliable,atlasdata/tiktok-ad-library-scraper-reliable,atlasdata/google-jobs-scraper-reliable"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

70% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

Other Atlas integrations