com.mcparmory/builtwith
OCI · GHCR.IO/MCPARMORY/BUILTWITH:1.0.3 · 2 COMPONENTS · SCANNED SEP 20
Detect technologies and tech stacks used on any website
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4003 tokens (~117/item across 34 items; 34 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 34 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/builtwith MCP server?
com.mcparmory/builtwith runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/builtwith:1.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/builtwith:1.0.3
claude mcp add com-mcparmory-builtwith -- docker run --rm -i ghcr.io/mcparmory/builtwith:1.0.3
{
"mcpServers": {
"com-mcparmory-builtwith": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/builtwith:1.0.3"
]
}
}
} {
"servers": {
"com-mcparmory-builtwith": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/builtwith:1.0.3"
]
}
}
} codex mcp add com-mcparmory-builtwith -- docker run --rm -i ghcr.io/mcparmory/builtwith:1.0.3
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-builtwith": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/builtwith:1.0.3"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-builtwith:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/builtwith:1.0.3"] {
"McpServers": {
"com-mcparmory-builtwith": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/builtwith:1.0.3"
]
}
}
} {
"mcpServers": {
"com-mcparmory-builtwith": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/builtwith:1.0.3"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −2
- Stability: pass → 0.83 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/builtwith:1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_domain_trust Assess Domain Trust ~151
Evaluate the trustworthiness of a website to support fraud detection and risk assessment. Analyzes trust signals including technology investment, domain history, relationships, response patterns, and keyword relevance.
| Name | Type | Req | Description |
|---|---|---|---|
| LIVE | string | – | Enable real-time website verification for more accurate results. Live lookups take longer to complete but are required when the initial assessment indicates the site needs further investigation. |
| LOOKUP | string | yes | The domain, subdomain, or specific page URL to evaluate for trustworthiness. Supports both root domains and internal page paths. |
| WORDS | string | – | Optional keywords to cross-reference against website content and metadata, provided as a comma-separated list. Helps identify relevance and potential keyword stuffing or mismatch indicators. |
No output schema declared.
No examples provided.
assess_domain_trust_xml Assess Domain Trust (XML) ~157
Evaluate the trustworthiness of a website for fraud detection purposes. Returns trust status and analysis based on technology spend, time, relationships, response, keywords, and other attributes in XML format.
| Name | Type | Req | Description |
|---|---|---|---|
| LIVE | string | – | Enable live website lookup for real-time verification. Live lookups take longer to complete but are required when the initial assessment returns a 'needLive' status to determine if the website is gen… |
| LOOKUP | string | yes | The domain, subdomain, or internal page URL to evaluate. Supports subdomains and internal pages when using the live lookup feature. |
| WORDS | string | – | Optional keywords to match against the website content and metadata. Provide as a comma-separated list to help identify relevant trust signals. |
No output schema declared.
No examples provided.
bulk_lookup_domains Bulk Lookup Domains ~135
Submit multiple root domains for technology stack analysis. Small batches return results immediately, while large batches are processed asynchronously and return a job ID for tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| liveOnly | boolean | – | Return only technologies that are currently active or deployed on the domains, filtering out historical or inactive detections. |
| lookups | array | yes | Array of root domains to analyze. Each item should be a valid domain name. Order is preserved in results. |
| noMeta | boolean | – | Exclude metadata from the response to reduce payload size and improve performance. |
| noPii | boolean | – | Strip personally identifiable information from results to ensure privacy compliance. |
No output schema declared.
No examples provided.
detect_technologies Detect Technologies ~286
Detect and retrieve technology stack information for one or more websites. Returns comprehensive details about installed technologies, metadata, and detection attributes in JSON format.
| Name | Type | Req | Description |
|---|---|---|---|
| FDRANGE | string | – | Filter technologies by first detection date range using ISO 8601 format (start_date|end_date, e.g., 2022-01-01|2023-01-01). |
| LDRANGE | string | – | Filter technologies by last detection date range using ISO 8601 format (start_date|end_date, e.g., 2022-01-01|2023-01-01). |
| LIVEONLY | string | – | Filter results to only include technologies currently active on the domain. |
| LOOKUP | string | yes | Single domain or comma-separated list of up to 16 domains to analyze (e.g., example.com or example.com,other.com,another.com). |
| NOATTR | string | – | Exclude technology attributes data to reduce response size and improve performance. |
| NOMETA | string | – | Exclude metadata such as business addresses and contact names to reduce response size and improve performance. |
| NOPII | string | – | Remove personally identifiable information including people names and email addresses (EU and California PII automatically redacted regardless). |
| TRUST | string | – | Enrich results with additional trust and security data from the Trust API (consumes extra API credits). |
No output schema declared.
No examples provided.
extract_domain_keywords Extract Domain Keywords ~91
Extract keywords found on one or more domains and return the results in XML format. Useful for SEO analysis and understanding domain content focus.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | One or more root domains to analyze for keywords. Provide a single domain (e.g., hotelscombined.com) or multiple domains in comma-separated format for batch lookup of up to 16 domains. Subdomains and… |
No output schema declared.
No examples provided.
get_bulk_domain_job_status Get Bulk Domain Job Status ~55
Retrieve the current status and results of a bulk domain lookup job. Use this to check progress and retrieve completed domain information.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The unique identifier of the bulk job, provided as a UUID. |
No output schema declared.
No examples provided.
get_domain_redirects Get Domain Redirects ~66
Retrieve live and historical redirect information for a domain, including both inbound and outbound redirects in JSON format.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | The root domain to look up (e.g., hotelscombined.com). Only root domains are supported; internal pages and subdomains are not valid. |
No output schema declared.
No examples provided.
get_domain_redirects_xml Get Domain Redirects (XML) ~77
Retrieve live and historical redirect information for a domain in XML format. Returns both inbound and outbound redirects that point to or from the specified domain.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | The root domain to look up redirects for. Only root domains are supported (e.g., builtwith.com); internal pages and subdomains are not accepted. |
No output schema declared.
No examples provided.
get_domain_technologies Get Domain Technologies ~260
Retrieve detected technologies and metadata for one or more domains in XML format. Supports filtering by detection dates, trust data inclusion, and optional data exclusion for performance optimization.
| Name | Type | Req | Description |
|---|---|---|---|
| FDRANGE | string | – | Filters technologies to include only those first detected within a specified date range. Use ISO 8601 format for date specification. |
| LDRANGE | string | – | Filters technologies to include only those last detected within a specified date range. Use ISO 8601 format for date specification. |
| LIVEONLY | string | – | When enabled, returns only technologies currently active on the domain, filtering out historical or inactive detections. |
| LOOKUP | string | yes | A single root domain or comma-separated list of up to 16 domains to analyze for technology detection. |
| NOATTR | string | – | When enabled, excludes technology attributes from the response to reduce payload size and improve response performance. |
| NOMETA | string | – | When enabled, excludes metadata from the response to reduce payload size and improve response performance. |
| NOPII | string | – | When enabled, removes personally identifiable information such as people names and email addresses from the results. |
| TRUST | string | – | When enabled, includes additional Trust API data alongside technology information for enhanced security and reputation insights. |
No output schema declared.
No examples provided.
get_domain_technologies_csv Get Domain Technologies CSV ~175
Retrieve technology stack information for one or more websites in CSV format. Supports batch lookups of up to 16 domains with optional filtering and data reduction.
| Name | Type | Req | Description |
|---|---|---|---|
| LIVEONLY | string | – | When set to 'yes', returns only technologies currently active on the domain, excluding deprecated or historical detections. |
| LOOKUP | string | yes | A single root domain or comma-separated list of up to 16 domains to analyze for technology detection. |
| NOATTR | string | – | When set to 'yes', excludes attribute data from the response to reduce payload size. |
| NOMETA | string | – | When set to 'yes', excludes metadata fields from the response to reduce payload size. |
| NOPII | string | – | When set to 'yes', removes personally identifiable information such as people names and email addresses from the results. |
No output schema declared.
No examples provided.
get_domain_technology_summary Get Domain Technology Summary ~71
Retrieve technology stack metadata for a domain, including last updated timestamp and counts of active and inactive technologies organized by group and category.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | The domain to analyze. Provide only the root domain (e.g., hotelscombined.com); subdomains will automatically resolve to their root domain. |
No output schema declared.
No examples provided.
get_domain_technology_summary_xml Get Domain Technology Summary ~63
Retrieve technology group and category metadata for a domain, including last updated timestamp and counts of active and inactive technologies.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | The domain to analyze. Only root domain results are returned; subdomains are automatically resolved to their root domain. |
No output schema declared.
No examples provided.
get_technology_recommendations Get Technology Recommendations ~87
Retrieve technology recommendations for websites based on analysis of similar technology profiles. Accepts one or more domains to identify recommended technologies used by comparable sites.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | One or more root domains to analyze, provided as a single domain or comma-separated list of up to 16 domains. Only alphanumeric characters, dots, hyphens, and commas are allowed. |
No output schema declared.
No examples provided.
get_technology_recommendations_xml Get Technology Recommendations XML ~80
Retrieve technology stack recommendations for websites based on analysis of similar technology profiles. Returns results in XML format.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | One or more root domains to analyze, provided as a single domain or comma-separated list of up to 16 domains. Only alphanumeric characters, dots, hyphens, and commas are allowed. |
No output schema declared.
No examples provided.
get_technology_trends Get Technology Trends ~104
Retrieve technology trend data in JSON format for a specified technology, optionally filtered to a specific date.
| Name | Type | Req | Description |
|---|---|---|---|
| DATE | string | – | Optional date to retrieve historical trend totals. When provided, returns the trend data closest to the specified date in ISO 8601 format (YYYY-MM-DD). |
| TECH | string | yes | The name of the technology to retrieve trends for. Use hyphens (-) instead of spaces in multi-word technology names (e.g., 'Magento'). |
No output schema declared.
No examples provided.
get_technology_trends_xml Get Technology Trends ~108
Retrieve technology trend data in XML format for a specified technology, optionally filtered to a specific date.
| Name | Type | Req | Description |
|---|---|---|---|
| DATE | string | – | Optional date to retrieve historical trend data. When provided, returns trend totals closest to the specified date in ISO 8601 format (YYYY-MM-DD). |
| TECH | string | yes | The name of the technology to retrieve trends for. Use hyphens to replace spaces in multi-word technology names (e.g., 'Shopify' or 'Node-js'). |
No output schema declared.
No examples provided.
list_domain_keywords List Domain Keywords ~86
Retrieve keywords found on one or more domains. Useful for understanding the primary topics and content focus of websites.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | One or more root domains to analyze (e.g., cnn.com). Use comma-separated values to look up multiple domains at once, up to 16 domains maximum. Only root domains are supported; subdomains and internal… |
No output schema declared.
No examples provided.
list_domains_by_attribute List Domains by Attribute ~138
Retrieve a list of domains that share a common attribute such as an IP address, Google Analytics tag, or other identifier. Optionally retrieve available attribute types for lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | The attribute to search for, specified in ATTRIBUTE-TYPE-CODE format (e.g., IP-98.158.194.127 or CA-PUB-1894893914772263). You can provide up to 16 comma-separated values to lookup multiple attribute… |
| TYPES | boolean | – | Set to true to retrieve the list of available attribute types that can be used in lookups instead of searching for domains. |
No output schema declared.
No examples provided.
list_domains_by_attribute_xml List Domains by Attribute ~139
Retrieve a list of domains that share a specific attribute such as an IP address, Google Analytics tag, or other identifier in XML format.
| Name | Type | Req | Description |
|---|---|---|---|
| LOOKUP | string | yes | The attribute to search for, specified in ATTRIBUTE-TYPE-CODE format (e.g., IP-98.158.194.127 for IP addresses or CA-PUB-1894893914772263 for Google Analytics tags). You can provide up to 16 comma-se… |
| TYPES | boolean | – | Set to true to retrieve the list of available attribute types that can be used for lookups instead of searching for domains. |
No output schema declared.
No examples provided.
list_website_relationships List Website Relationships ~108
Retrieve the network of relationships between websites, showing which sites are linked together. Results are returned in JSON format and consume 1 API credit per 500 relationships.
| Name | Type | Req | Description |
|---|---|---|---|
| IP | string | – | Optional flag to include website IP address data in the results, which significantly expands the relationship data returned. |
| LOOKUP | string | yes | One or more domains to analyze for relationships. Accepts individual domains, subdomains, or up to 16 domains as comma-separated values for batch lookups. |
No output schema declared.
No examples provided.
list_website_relationships_csv List Website Relationships as CSV ~105
Retrieve relationships between websites showing which sites are linked together in CSV format. Each request consumes 1 API credit per 500 relationships returned.
| Name | Type | Req | Description |
|---|---|---|---|
| IP | string | – | Optional flag to include IP address data for the websites in the results. Set to 'yes' to enable IP data retrieval. |
| LOOKUP | string | yes | The domain name to lookup and analyze for relationships. Specify a single domain (e.g., builtwith.com) to retrieve all linked websites. |
No output schema declared.
No examples provided.
list_website_relationships_tsv List Website Relationships as TSV ~102
Retrieve relationships between websites showing which sites link to each other in TSV format. Each API credit covers up to 500 relationships.
| Name | Type | Req | Description |
|---|---|---|---|
| IP | string | – | Optional flag to include IP address information for the websites in the results. Set to 'yes' to retrieve IP data alongside relationship data. |
| LOOKUP | string | yes | The domain or domains to analyze for relationship data. Specify one or more domains to discover their linking relationships with other websites. |
No output schema declared.
No examples provided.
list_website_relationships_xml List Website Relationships (XML) ~98
Retrieve relationships between websites showing which sites are linked together in XML format. Each request consumes 1 API credit per 500 relationships returned.
| Name | Type | Req | Description |
|---|---|---|---|
| IP | string | – | Optional flag to include IP address data for the websites in the response. |
| LOOKUP | string | yes | One or more domains to analyze for relationships. Accepts individual domains, subdomains, or up to 16 domains as comma-separated values for batch lookups. |
No output schema declared.
No examples provided.
list_websites_by_technology List Websites by Technology ~187
Retrieve a list of websites currently using a specified web technology. Optionally filter by country and include detailed metadata such as company names, contact information, and traffic rankings.
| Name | Type | Req | Description |
|---|---|---|---|
| COUNTRY | string | – | Filter results to websites with specific country domains and/or country addresses. Specify one or more countries using ISO 3166-1 alpha-2 format (e.g., 'br' for Brazil), separated by commas for multi… |
| META | string | – | Include enriched metadata with results such as company names, titles, social media links, addresses, email addresses, phone numbers, and traffic rankings. |
| TECH | string | yes | The name of the web technology to search for, with spaces replaced by dashes (e.g., 'Shopify' becomes 'Shopify'). This is the core search parameter. |
No output schema declared.
No examples provided.
list_websites_by_technology_xml List Websites by Technology (XML) ~173
Retrieve a list of websites currently using a specified web technology. Optionally filter by country and include detailed metadata such as company names, contact information, and traffic rankings.
| Name | Type | Req | Description |
|---|---|---|---|
| COUNTRY | string | – | Filter results by country using ISO 3166-1 alpha-2 country codes (e.g., 'br' for Brazil, 'uk' for United Kingdom). Specify multiple countries as comma-separated values (e.g., 'au,nz'). |
| META | string | – | Include detailed metadata with results such as company names, titles, social media links, addresses, email addresses, phone numbers, and traffic rankings. |
| TECH | string | yes | The name of the web technology to search for. Replace spaces with dashes in the technology name (e.g., 'Magento' or 'Google-Analytics'). |
No output schema declared.
No examples provided.
lookup_company_domains Lookup Company Domains ~65
Retrieve domain names and websites associated with one or more company names, ordered by relevance to help identify official web presences.
| Name | Type | Req | Description |
|---|---|---|---|
| COMPANY | string | yes | One or more company names to look up, provided as a single name or as a comma-separated list of names (URL encoded). |
No output schema declared.
No examples provided.
resolve_company_domains Resolve Company Domains ~76
Resolve domain names and websites for one or more company names. Supply a single company name or a comma-separated list of company names to retrieve associated domain information in XML format.
| Name | Type | Req | Description |
|---|---|---|---|
| COMPANY | string | yes | A single company name or comma-separated list of company names to look up. Each company name should be URL encoded if containing special characters. |
No output schema declared.
No examples provided.
retrieve_bulk_domain_job_result Retrieve Bulk Domain Job Result ~62
Retrieve the results of a completed bulk domain lookup job. Note that results are automatically deleted after the first access, so this is a one-time download operation.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The unique identifier of the bulk job, formatted as a UUID. |
No output schema declared.
No examples provided.
search_product_listings Search Product Listings ~158
Search for eCommerce products across the internet and discover which shops are selling them. Results are organized by domain/shop and support pagination for browsing large result sets.
| Name | Type | Req | Description |
|---|---|---|---|
| LIMIT | integer | – | Maximum number of shops to return in the results, ranging from 1 to 500. Defaults to 50 shops per request. |
| PAGE | integer | – | Zero-indexed page number for pagination through results. Use 0 for the first page, 1 for the second, and so on. Defaults to the first page. |
| QUERY | string | yes | Search query for products or specific domains. Use 'dom:domain.com' format to find all products available at a particular website, or enter a product name or description to search across all shops. |
No output schema declared.
No examples provided.
search_technologies Search Technologies ~107
Search for technologies and categories using natural language queries powered by vector similarity matching. Discover relevant tools and categories by describing what you're looking for.
| Name | Type | Req | Description |
|---|---|---|---|
| LIMIT | integer | – | Maximum number of results to return in the response. Must be between 1 and 100 results; defaults to 10 if not specified. |
| QUERY | string | yes | The search query describing the technologies or categories you want to find (e.g., 'react framework'). Use natural language to describe what you're looking for. |
No output schema declared.
No examples provided.
search_technologies_csv Search Technologies CSV ~109
Search for technologies and categories using natural language queries powered by vector similarity matching. Returns matching results in CSV format for easy integration and analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| LIMIT | integer | – | Maximum number of results to return in the response. Must be between 1 and 100 results; defaults to 10 if not specified. |
| QUERY | string | yes | The search query describing the technologies or categories you want to find (e.g., 'ecommerce platform'). Use natural language to describe what you're looking for. |
No output schema declared.
No examples provided.
search_technologies_xml Search Technologies XML ~101
Search for technologies and categories using natural language queries powered by vector similarity matching. Describe what you're looking for to discover relevant technologies and their categories.
| Name | Type | Req | Description |
|---|---|---|---|
| LIMIT | integer | – | Maximum number of results to return, between 1 and 100 (defaults to 10 if not specified) |
| QUERY | string | yes | The search query describing the technology or category you want to find (e.g., 'google analytics', 'web tracking', 'analytics platform') |
No output schema declared.
No examples provided.
search_websites_by_keyword Search Websites by Keyword ~119
Search for websites containing specific keywords. Returns a list of domain names that match your search criteria, useful for market research, competitor analysis, or finding relevant web properties.
| Name | Type | Req | Description |
|---|---|---|---|
| KEYWORD | string | yes | The keyword to search for. Must be at least 4 letters long, contain only alphabetical characters, and cannot be a common stop word (e.g., 'the', 'and'). |
| LIMIT | integer | – | Number of results to return, ranging from 16 to 1000 domains. Defaults to 100 results if not specified. |
No output schema declared.
No examples provided.
search_websites_by_keyword_csv Search Websites by Keyword (CSV) ~104
Search for websites containing a specific keyword and retrieve results in CSV format. Useful for finding web properties associated with particular topics or terms.
| Name | Type | Req | Description |
|---|---|---|---|
| KEYWORD | string | yes | The keyword to search for. Must be at least 4 characters long, contain only alphabetical characters, and cannot be a common stop word. |
| LIMIT | integer | – | The number of results to return, ranging from 16 to 1000 results. Defaults to 100 if not specified. |
No output schema declared.
No examples provided.
What is the com.mcparmory/builtwith MCP server?
com.mcparmory/builtwith is an MCP server listed in the public MCP registry as com.mcparmory/builtwith. Detect technologies and tech stacks used on any website. This page covers its container image (ghcr.io/mcparmory/builtwith:1.0.3).
Is the com.mcparmory/builtwith MCP server safe to use?
com.mcparmory/builtwith scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/builtwith MCP server expose?
com.mcparmory/builtwith exposes 34 tools: detect_technologies, get_domain_technologies, get_domain_technologies_csv, bulk_lookup_domains, get_bulk_domain_job_status, and 29 more. Their descriptions and schemas cost roughly 4,003 tokens of context every time the server is loaded.
Is the com.mcparmory/builtwith MCP server still maintained?
com.mcparmory/builtwith is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.