BuiltWith MCP Server

Created By
Cyreslab-AIa year ago
Overview

what is BuiltWith MCP Server?

BuiltWith MCP Server 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 to work with any AI assistant that supports the Model Context Protocol.

how to use BuiltWith MCP Server?

To use the BuiltWith MCP Server, clone the repository from GitHub, install the necessary dependencies, and run the server with your BuiltWith API key configured in the environment variables or MCP settings.

key features of BuiltWith MCP Server?

  • Domain Lookup: Retrieve detailed information about the technologies used by a specific domain.
  • Technology Categorization: View technologies grouped by categories such as Analytics, CMS, Frameworks, etc.
  • Detailed Information: Access descriptions, detection dates, and links for each technology.

use cases of BuiltWith MCP Server?

  1. Analyzing the technology stack of a competitor's website.
  2. Identifying the analytics tools used by a specific domain.
  3. Integrating with AI assistants to provide technology insights on demand.

FAQ from BuiltWith MCP Server?

  • How do I get a BuiltWith API key?

You can obtain a BuiltWith API key by signing up at the BuiltWith website.

  • Can I use this server with any AI assistant?

Yes! The server is compatible with any AI assistant that supports the Model Context Protocol.

  • What technologies can I query?

You can query any domain to find out the technologies it uses, including CMS, frameworks, and analytics tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Cyreslab-AI
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago