Nerdydata

io.github.nerdydataPublished by GitHub account nerdydatav1.0.8Updated Oct 24, 2026

Search websites by source code, technology stack, analyze domains, and download lead lists.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

NerdyData MCP lets an assistant search websites by their source code and technology stack, analyze domains, and download lead lists.

What you can do
Search websites by the source code and technologies they use, such as frameworks and analytics tags. Analyze domains to see what a site is built with. Download lead lists built from those searches. The server is reached either as a hosted endpoint or as a local npm package over stdio.
When to use it
Useful for sales, marketing or research work that needs to find sites using a particular technology or code snippet, or to build prospect lists from those results.
Requirements
A NerdyData account and API key, supplied as the NERDYDATA_API_KEY environment variable. Authentication is OAuth-based. Can run as a remote endpoint or as a local process via the npm package, which needs Node.js. Network access to NerdyData.
Before you install
The API key is a secret and grants access to your NerdyData account, which may be billed or quota-limited. Searches and lead-list downloads send your queries to NerdyData's servers. Downloaded lead lists contain third-party contact data, so handle them according to applicable privacy rules.

Installation

In SourceWeft

  1. Open Nerdydata 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.nerdydata%2Fmcp/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": {
    "nerdydata": {
      "type": "http",
      "url": "https://mcp.nerdydata.com/mcp"
    }
  }
}

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.8LatestSep 16, 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.