builtwith
Registry code: 2e016538ff46341c
BuiltWith supports keyless Stripe MPP card payments: start with mpp-catalog, buy credits using mpp-purchase, and use mpp-data with the returned temporary access_token. No signup or existing API key is required. $0.50 buys 10 lookups; tokens last 24 hours by default (up to 720 hours if requested before payment). Lists require a plan. Existing API-key and x402 tools remain available.
- endpoint
- https://api.builtwith.com/mcp
- door code
- 1457330734d87270
- protocol
- HTTP+JSON ·0.3
- authentication
- http
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 10 · newcomer
- Is builtwith live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is builtwith free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does builtwith have?
- 8 tools: Keywords and recommendations, Technology change tracking, Accountless x402 USDC access, Domain technology profile, Website relationships, Technology lists and trends, Company and firmographics, Natural-language site discovery.
- Is builtwith safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99%· all time 99.2%
last good check
of 8 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- look up a website's technology stack
- find websites using a technology
- find domains for a company
- get related websites
- takes → gives
- text → data
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-10
no flags
Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
keywords-and-recommendations auth-required never probed
Retrieve the keywords a website ranks for, search websites by keyword, and get technology recommendations for a domain.
technology-changes auth-required never probed
Report technologies added, dropped, or changed on a website over time, and the redirects associated with a domain.
x402-usdc-access auth-required never probed
Run fixed-price BuiltWith lookups without an account or API key. Pay each /agent/* HTTP request with x402 v2, or buy reusable MCP lookup units with Base USDC and use the returned creditKey.
domain-technology-profile auth-required never probed
Look up the full technology stack detected on a website, including current and historical technologies, first/last detected dates, categories, and metadata.
website-relationships auth-required never probed
Discover relationships between websites — shared analytics, advertising, hosting, and tracking identifiers that link domains to the same owner or network.
technology-lists-and-trends auth-required never probed
List and rank the websites using a specific technology, with adoption trends over time, market share, and tag-based segmentation.
company-and-firmographics auth-required never probed
Resolve a company name to its primary website, and retrieve firmographic, financial, social, traffic, and trust signals for a domain.
natural-language-site-discovery auth-required never probed
Answer free-form questions that find and rank lists of websites by technology, concept, or attribute, returning structured results.
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id2e016538ff46341c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2e016538ff46341c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2e016538ff46341c?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.