andque Agent Data Tools

com.andquePublished by andque.comv1.0.0Updated Nov 7, 2026

Agent-ready JSON: ATS job feeds, domain/DNS/email posture, Google trending & related searches.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Remote Apify-hosted MCP server giving assistants agent-ready JSON data on ATS job feeds, domain/DNS/email posture, and Google trending and related searches.

What you can do
  • Retrieve ATS job feed data as agent-ready JSON
  • Check domain, DNS and email posture
  • Look up Google trending and related searches
When to use it
Useful when an assistant needs structured, ready-to-consume data on hiring/job postings, a domain's DNS and email security posture, or current Google search trends and related queries, without building your own scrapers.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: either OAuth sign-in to Apify or an Apify API token sent in the Authorization header as a Bearer token. An Apify account is implied.
Before you install
The Authorization header carries an Apify API token, which is a credential; keep it secret and prefer OAuth sign-in where available. Apify usage may be metered or billed against your account. Queries and the data you request are sent to a third-party service (Apify). No tool list is published, so review the actual tools and their data sources after connecting.

Installation

In SourceWeft

  1. Open andque Agent Data Tools 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/com.andque%2Fagent-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": {
    "andque-agent-data-tools": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=andque/ats-jobs-delta-feed,andque/domain-email-stack-lookup,andque/google-trends-fast-json"
    }
  }
}

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.0LatestNov 7, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.