Website Technology Lookup

What it does

Website Technology Lookup takes ONE domain, makes one https request for its home page, and reads the response headers and the page source with detection rules we wrote ourselves. It answers with the technologies the page showed, in groups: site builder or CMS, shop platform, analytics, tag manager, payments, framework, hosting or CDN, web server, engagement tools, and agent-readable files the page points to (llms.txt, MCP or agent-card links, a markdown copy, an API description). Each item says how sure we are: strong (two independent signs, or one that sites rarely show by accident) or possible (one weak sign). Every answer is dated and signed with our key, so you can keep it as proof of what the page showed that day, and anyone can check the signature at the stamp page. It never crawls (it follows at most 3 redirects of the home page), never fetches the files a page mentions, never runs scripts, never sends cookies and keeps no copy of results. No model, no list mode.

Who it is for

Agents and people who need a quick, checkable read on what a site runs on before they act: sizing up a vendor or competitor, vetting a shop, deciding how to integrate, or checking that a site is ready for agents.

Price

Free, no sign-up: 100 lookups a day per caller. Paid calls are not offered.

Limits

One domain per call, no lists. One https request for the home page only; no other page and no file the page mentions is fetched (an llms.txt or MCP link is reported as linked, not checked). Public web sites only. A technology is listed only if the page or its headers showed it: sites can hide, rename or fake these signs, and our rule table is short and incomplete, so a missing technology is not proof it is absent. If the site answers with an error or a non-page, only its headers are read and the answer says so. Cookie values are never read into the answer. At most 30 lookups of one domain an hour across all callers. We keep no copy of results, only short-lived counters in memory.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"website_tech_lookup","arguments":{"domain":"example.com"}}}
-> technologies (id, name, category, confidence, where it was seen), summary by category, facts (server header, generator, redirect), signed observation, receipt, stamp link

For agents

Tool website_tech_lookup on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:ksb62otgxg5x2cql43pwbfttja): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): br98OSkNmhzY2Xm0dN8N/XTurux3fQgng5PXRBntUWY=

This tool exists to be found by agents that search MCP registries for technology lookup, tech stack detection and site analysis (road: MCP registries, through the Campus gateway: MCP, Agent2Agent and REST). It gives one signed, checkable answer per call; keep the signed observation with your work so a person can see what was seen and when. How a stamp is checked: https://llpro.ai/stamp

Next

• Connect your agent: Use this and the other LLPRO tools from your own agent.
• Get your agent: No agent yet? Get one that asks first.
• Hand the whole job to the Hub: One site is one part. Tell the Hub the job (compare vendors, vet a shop, make a site agent-ready); it routes you to the right check.

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card