DomainDNA: Tech Stack Detector, WHOIS & Domain Age API

io.github.shawmena-dotcomPublished by GitHub account shawmena-dotcomv1.0.2Updated Oct 24, 2026

DomainDNA: a domain's tech stack, email security (MX/SPF/DMARC), TLS expiry and age in one record.

The publisher's own server: Tech.eu Funding Explorer

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Remote Apify MCP server that returns a domain's tech stack, email security records, TLS expiry and domain age in one record.

What you can do
Look up a domain's detected technology stack from a single query. Retrieve email security records such as MX, SPF and DMARC for a domain. Check TLS certificate expiry and the domain's age. Combine these signals into one consolidated domain record for assessment.
When to use it
Useful when you need a quick profile of a website or company domain, for example during vendor due diligence, security triage, or lead research where tech stack, email authentication and certificate status matter.
Requirements
A remote MCP endpoint at mcp.apify.com, reachable over the network. An Apify account and an Apify API token sent in the Authorization header as a Bearer token; OAuth is declared as required.
Before you install
The Authorization header carries your Apify API token, a secret that should not be exposed. Runs are billed per result to your Apify account, so repeated lookups cost money. Queries send the target domain to Apify's hosted service.

Installation

In SourceWeft

  1. Open DomainDNA: Tech Stack Detector, WHOIS & Domain Age API 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.shawmena-dotcom%2Fdomain-intel/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": {
    "domaindna-tech-stack-detector-whois-doma": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=cybermax/domain-intel"
    }
  }
}

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

2
  1. v1.0.2LatestSep 24, 2026
  2. v1.0.1Sep 23, 2026

Score

60% 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

    Declare a license in the repository or the registry entry.

Other Tech integrations