MCP servers › io.github.builtwith › builtwith
MCP server · registry snapshot 2026-11-12 · last tested 2026-11-12
builtwith MCP server
Registry name io.github.builtwith/builtwith
by builtwith · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗
Official BuiltWith tools for website technologies, company research, relationships, and trends. — the publisher's description
Summary
io.github.builtwith/builtwith is a remote MCP server listed in the official MCP registry at version 2.1.0, under the namespace of the GitHub account builtwith. Its linked repository, github.com/builtwith/builtwith-mcp, belongs to the same GitHub account. On 2026-11-12 ProtocolProbe connected to it in read-only mode and read its inventory: 51 tools, 2 resources and 6 prompts.
Record checks
4 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- #1,500 of 28,859 repositories by GitHub stars, tied with 12 others
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 51
- Last tested
- 2026-11-12
Tool list size
11,416 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (51 tools). Counted with Anthropic's token counter on 2026-11-12, from the tool list we read on 2026-11-12. Median across 28,560 counted servers: 2,657 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-12 (api.builtwith.com), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (2.1.0).
Observed fact
This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (mpp-purchase, payment-purchase, x402-credit-purchase, x402-list-pass-purchase). That is our reading of the names; we did not call them. Source: our connection, 2026-11-12.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-12
- Mode
- read-only (no tool calls)
- Latest version
- 2.1.0, published 2026-11-10 (registry, as of the 2026-11-12 snapshot)
- First listed version
- 2026-11-10 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-12
- Package and repository
- checked 2026-11-12
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-11-09, listed on 2026-11-12 with version 2.1.0 (published 2026-11-10).
Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12.
What it is
What does this server offer?
Observed inventoryNone of its 51 tools are described as changing anything. For 51 the reading was uncertain, so no mark is shown.
- mpp-catalog
“Discover Stripe card MPP payments without an existing BuiltWith account or API key.”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
- mpp-purchase
“Buy API lookup credits or a one-off plan with Stripe MPP card payment.”
Publisher declares: read-only no · destructive yes · open-world yes
5 inputs, 2 required
productstringrequiredcreditsintegertokenHoursintegeridempotencyKeystringrequiredpaymentCredentialstring“Full Authorization: Payment ...”
- mpp-data
“Use the temporary access_token returned by mpp-purchase without configuring an API key.”
Publisher declares: read-only no · destructive no · open-world no
9 inputs, 2 required
accessTokenstringrequired“Secret access_token returned after successful Stripe MPP payment”operationstringrequireddomainstringsincestringliveOnlybooleantechnologystringcountrystringminimumMonthlySpendnumberoffsetstring
- domain-lookupon 2 other servers
“Returns the live web technologies used on the root domain name.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 1 required
domainstringrequiredliveOnlyboolean
- domain-api
“Domain API JSON lookup for technology and metadata by domain.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired
- domain-api-json
“Raw Domain API JSON lookup for technology and metadata by domain.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired
- change-api
“Change API JSON lookup for technology additions and removals by domain.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 1 required
lookupstringrequired“Domain name, or comma-separated domain names, to check for technology changes”sincestring“Optional natural language date range such as 'last month'; defaults to 3 months”
- relationships-api
“Relationships API JSON lookup for related websites by domain.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired
- free-api
“Free API JSON lookup for category/group counts by domain.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired
- company-to-url
“Company to URL API JSON lookup for domains from a company name.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
companystringrequired
- tags-api
“Tags API JSON lookup for related domains from IP or attributes.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired
- recommendations-api
“Recommendations API JSON lookup for technology recommendations by domain.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired
Show 39 more tools
- redirects-api
“Redirects API JSON lookup for live and historical redirects by domain.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired
- keywords-api
“Keywords API JSON lookup for keyword data by domain.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired
- keywords-search-api
“Keyword Search API — find websites containing a specific keyword.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 1 required
keywordstringrequired“The keyword to search for (e.g.”limitinteger“Results per request (16–1000, default 100)”offsetstring“Domain name from the previous response's NextOffset for pagination”
- trends-api
“Trends API JSON lookup for technology trend data.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
techstringrequired
- product-api
“Product API JSON lookup for ecommerce product searches.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
querystringrequired
- trust-api
“Trust API JSON lookup for trust scoring by domain.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired
- vat-api
“VAT API JSON lookup for VAT, GST, CNPJ, ABN, and other publicly displayed company registration numbers associated with websites.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
lookupstringrequired“One to 16 domain names, separated by commas”
- vat-types-api
“List every company registration type that the VAT API may return, including its code, friendly name, and description.”
Publisher declares: read-only no · destructive no · open-world no
Takes no inputs.
- whoami-api
“WhoAmI API JSON lookup for account limits, credit costs, privacy flags, max batch sizes, and endpoint inventory.”
Publisher declares: read-only no · destructive no · open-world no
Takes no inputs.
- usage-api
“Usage API JSON lookup for current credit balance (used, purchased, remaining).”
Publisher declares: read-only no · destructive no · open-world no
Takes no inputs.
- mcp-list-api
“Search and browse remote MCP servers in the BuiltWith MCP registry (v2).”
Publisher declares: read-only no · destructive no · open-world no
3 inputs
searchstring“Keyword matched against MCP server domains and descriptions; required when category is omitted”categorystring“MCP registry category slug; required when search is omitted”offsetinteger“Zero-based pagination offset (default 0; page size is 100)”
- mcp-list-categories
“List valid BuiltWith MCP registry category slugs, labels, and entry counts (v2).”
Publisher declares: read-only no · destructive no · open-world no
Takes no inputs.
- list-api
“List API JSON lookup for websites using a primary technology.”
Publisher declares: read-only no · destructive no · open-world no
23 inputs, 1 required
techstringrequired“Primary technology name, such as Shopify”otherTechsstring“Optional comma-separated subordinate technology filters; these do not consume additional report slots”metabooleancountrystringoffsetstringsincestringallbooleanspendstringrevenuestringskustringfollowersstringemployeesstringsitemapstringpageRankstringbwRankstringtrancostringmajesticstringbwsstringecommerceCategorystringaiMaturitystringaiOpennessstringaiReadinessstringaiVisibilitystring
- payment-balance
“Check an existing account's API-credit balance through the saved-Stripe-method top-up service.”
Publisher declares: read-only no · destructive no · open-world no
1 input
billingKeystring“Separately scoped Agent Billing Key; optional when the MCP request uses a compatible credential”
- payment-config
“Retrieve saved-Stripe-method account top-up limits, UTC monthly period, purchase increment, and idempotency rules.”
Publisher declares: read-only no · destructive no · open-world no
1 input
billingKeystring“Separately scoped Agent Billing Key; optional when the MCP request uses a compatible credential”
- payment-purchase
“Charge an existing account's saved Stripe payment method and add account API credits.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 3 required
creditsintegerrequired“Number of account API credits to purchase in fixed increments of 2,000”billingKeystringrequired“Separately scoped Agent Billing Key from payments.builtwith.com/agent-payment-api-config”idempotencyKeystringrequired“Unique operation identifier; reuse only when retrying the identical purchase”
- vector-api
“Search BuiltWith technologies and categories by text query using vector similarity.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 1 required
querystringrequired“Text to search for (e.g.”limitinteger“Max results to return (default 10, max 100)”
- ask-api
“Ask API lookup for natural language website list queries.”
Publisher declares: read-only no · destructive no · open-world no
4 inputs, 1 required
querystringrequired“The natural language query (e.g.”commitboolean“Ignored for OpenAI/ChatGPT requests; preview mode is always used there”nextOffsetstring“Pagination offset from the previous response's NextOffset”metaboolean“Set to true to include metadata in the results”
- ask-api-json
“Raw Ask API JSON lookup for app/internal use.”
Publisher declares: read-only no · destructive no · open-world no
4 inputs, 1 required
querystringrequired“The natural language query (e.g.”commitboolean“Set to true to run a full report returning up to 1000 results”nextOffsetstring“Pagination offset from the previous response's NextOffset”metaboolean“Set to true to include metadata in the results”
- x402-pricing
“Show prepaid batch-credit pricing, x402 configuration, and List pass tiers.”
Publisher declares: read-only no · destructive no · open-world no
1 input
creditsinteger
- x402-credit-purchase
“Purchase a batch of at least 2,000 non-expiring BuiltWith API credits with one x402 payment.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 2 required
creditsintegerrequiredpayerstringrequired“Base wallet address that will sign the x402 payment”creditKeystring“Reusable prepaid key returned by x402-credit-purchase”
- x402-credit-balance
“Check purchased, used, pending, and available credits for a reusable prepaid key.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
creditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-domain-lookup
“Returns live web technologies for one domain using one prepaid credit.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 2 required
domainstringrequiredliveOnlybooleancreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-domain-api
“Domain API technology and metadata lookup for one domain using one prepaid credit.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
lookupstringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-domain-api-json
“Raw Domain API JSON lookup for one or more comma-separated domains.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
lookupstringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-change-api
“Technology additions and removals for one or more comma-separated domains.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 2 required
lookupstringrequiredsincestringcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-relationships-api
“Related websites for a domain.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
lookupstringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-company-to-url
“Domains associated with a company name.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
companystringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-tags-api
“Related domains from an IP address or attributes.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
lookupstringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-recommendations-api
“Technology recommendations for a domain.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
lookupstringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-redirects-api
“Live and historical redirects for a domain.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
lookupstringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-keywords-api
“Keyword data for a domain.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
lookupstringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-trust-api
“Trust score for a domain.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
lookupstringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-vat-api
“Public company registration identifiers for one to sixteen domains.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
lookupstringrequiredcreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-vector-api
“Vector similarity search across BuiltWith technologies and categories.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 2 required
querystringrequiredlimitintegercreditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”
- x402-list-pass-purchase
“Purchase a 30-day Basic ($295, 2 technology and 2 keyword reports) or Pro ($495, 50 and 50) List API pass with Base USDC.”
Publisher declares: read-only no · destructive yes · open-world yes
2 inputs, 2 required
tierstringrequiredpayerstringrequired“Base wallet address that will sign the x402 payment”
- x402-list-api
“List websites using a primary technology with a valid x402 List pass.”
Publisher declares: read-only no · destructive no · open-world no
25 inputs, 3 required
techstringrequired“Primary technology name, such as Shopify”otherTechsstring“Optional comma-separated subordinate technology filters; these do not consume additional report slots”metabooleancountrystringoffsetstringsincestringallbooleanspendstringrevenuestringskustringfollowersstringemployeesstringsitemapstringpageRankstringbwRankstringtrancostringmajesticstringbwsstringecommerceCategorystringaiMaturitystringaiOpennessstringaiReadinessstringaiVisibilitystringpayerstringrequired“Base wallet address that will sign the x402 payment”passTokenstringrequired“Opaque token returned by x402-list-pass-purchase”
- x402-keywords-search-api
“Search websites containing a keyword with a valid x402 List pass.”
Publisher declares: read-only no · destructive no · open-world no
5 inputs, 3 required
keywordstringrequiredlimitintegeroffsetstringpayerstringrequired“Base wallet address that will sign the x402 payment”passTokenstringrequired“Opaque token returned by x402-list-pass-purchase”
- x402-ask-api
“Natural-language website query using one prepaid credit.”
Publisher declares: read-only no · destructive no · open-world no
7 inputs, 3 required
querystringrequiredcommitbooleannextOffsetstringmetabooleanpayerstringrequired“Base wallet address that will sign the x402 payment”creditKeystringrequired“Reusable prepaid key returned by x402-credit-purchase”passTokenstring“Opaque token returned by x402-list-pass-purchase”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-12.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 36% of 148
- Tools with a description
- 100% of 51
- Typical description length
- 135 characters
The tool set
Counted from the listing
- Tools
- 51
- Size of the list
- about 9,049 tokens for an agent to load (characters ÷ 4)
- Naming
- 51 of 51 names use kebab-case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 51 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-12 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://api.builtwith.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"builtwith": {
"url": "https://api.builtwith.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"builtwith": {
"type": "http",
"url": "https://api.builtwith.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"builtwith","type":"http","url":"https://api.builtwith.com/mcp"}'Claude Code
claude mcp add --transport http builtwith https://api.builtwith.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"builtwith": {
"type": "streamableHttp",
"url": "https://api.builtwith.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"builtwith": {
"httpUrl": "https://api.builtwith.com/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.builtwith] url = "https://api.builtwith.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"builtwith": {
"url": "https://api.builtwith.com/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.builtwith.com/mcp --transport http
- Optional settings the entry also lists (left out above): Authorization.
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
- Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.
Own host
- security.txt. security.txt found at https://api.builtwith.com/.well-known/security.txt (Contact given; expires 2035-08-26). Source: api.builtwith.com/.well-known/security.txt · read 2026-11-12.
- A2A agent card. An A2A agent card is published at https://api.builtwith.com/.well-known/agent-card.json (name, skills, url). Source: api.builtwith.com/.well-known/agent-card.json · read 2026-11-12.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint api.builtwith.com/mcp | Session opened | matches | our test · 2026-11-12 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-12 |
| Repository github.com/builtwith/builtwith-mcp | Opens publicly | matches | api.github.com · 2026-11-12 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.builtwith
- GitHub owner
- a personal account (builtwith)
- Repository
- github.com/builtwith/builtwith-mcp
- Stars
- 43
- Repository age
- over a year
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-12; security policy read from GitHub · 2026-11-12.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- #1,500 of 28,859 repositories by GitHub stars, tied with 12 others
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-12 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.builtwith/builtwith
Answered from the data aboveWho publishes io.github.builtwith/builtwith?
The registry ties the namespace io.github.builtwith to the GitHub account builtwith; only its owner can publish under it. Its linked repository, github.com/builtwith/builtwith-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.builtwith/builtwith safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.github.builtwith/builtwith need an API key or sign-in?
It opened a session without any credential on 2026-11-12. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.builtwith/builtwith been security tested?
Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
Does io.github.builtwith/builtwith publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of io.github.builtwith/builtwith?
In github.com/builtwith/builtwith-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: exercised
- Fake assistant turns: exercised
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
5 exercised11 not run (reason given)2 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 12Hidden content
audience-hidingChecks resources that hide content from the user.exercised - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-11-12, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 2,185 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 51 tools, 2 resources, 6 prompts.
- 11,988 msFinished: 5 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.builtwith/builtwith: MCP server record.” Data checked 2026-11-12. https://protocolprobe.com/mcp/servers/io.github.builtwith/builtwith
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.builtwith/builtwith)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology