MCP.so
ログイン

BuiltWith MCP Server

@Cyreslab-AI

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

Cyreslab-AI

BuiltWith MCP Server について

概要はまだありません

BuiltWith MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "builtwith-mcp-server": {
      "command": "node",
      "args": [
        "build/index.js"
      ],
      "env": {
        "BUILTWITH_API_KEY": "your-api-key-here"
      }
    }
  }
}

BuiltWith MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is BuiltWith MCP Server?

It is a Model Context Protocol (MCP) server that provides tools for querying the BuiltWith API to obtain information about website technology stacks. It is designed for use with any AI assistant that supports the Model Context Protocol.

How to use BuiltWith MCP Server?

Clone the repository, install dependencies with npm install, and build with npm run build. The server requires a BuiltWith API key, which you provide via the BUILTWITH_API_KEY environment variable either when running directly (node build/index.js) or in your MCP client’s settings file (e.g., Claude Desktop configuration).

Key features of BuiltWith MCP Server

  • Domain lookup for technology stack information
  • Technologies grouped by category (Analytics, CMS, Frameworks, etc.)
  • Access to descriptions, detection dates, and links for each technology
  • Integration with any MCP-compatible AI assistant

Use cases of BuiltWith MCP Server

  • Determine what technologies a competitor’s website uses
  • Analyze the tech stack of any domain for market research
  • Identify analytics or frameworks used by a site during a security assessment
  • Quickly check the technologies behind a URL from within an AI chat interface

よくある質問

1

What are the runtime requirements?

Node.js 18 or higher is required.

2

How do I get a BuiltWith API key?

You can obtain one at the BuiltWith API website (builtwith.com/api).

3

How is the server invoked and authenticated?

The server communicates over stdio using the Model Context Protocol. Authentication is done by setting the `BUILTWITH_API_KEY` environment variable before starting the server.

4

Where does the data come from?

All technology stack data is retrieved from the BuiltWith API; no data is stored locally by the server.

5

What tools does it expose?

The server provides a single tool, `domain_lookup`, which accepts a `domain` (required) and an optional `detailed` boolean parameter.

コメント

「その他」の他のコンテンツ