PublicWWW
Server Details
Search the source code (HTML, JavaScript, CSS) of web pages.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- publicwww-com/publicwww-mcp
- GitHub Stars
- 4
- Server Listing
- PublicWWW MCP server
- ChatGPT
- –
- Claude
- PublicWWW
TDQS
Scored across 11 tools
Each tool targets a distinct resource or action: search finds sites by code, build_signatures turns a cluster into candidate searches, extract_from_cluster pulls values, and the cluster tools split cleanly into list/get/create/rename/delete/combine. The two informational tools (account for plan/quotas, read_docs for documentation) are clearly separated, and descriptions explicitly steer between the easily-confused pair (search vs. build_signatures, like: vs. code matching).
Nine of eleven tools follow a clean verb_noun or verb_resource pattern (create_cluster, list_clusters, get_cluster, rename_cluster, delete_cluster, combine_clusters, build_signatures, extract_from_cluster, read_docs), with all cluster operations sharing a consistent noun. The two outliers, `search` and `account`, are bare verbs/nouns rather than matching the pattern, but they are unambiguous.
Eleven tools is well within the sweet spot and every one earns its place: one search primitive, a full cluster lifecycle, extraction, signature discovery, docs, and account state. There is no filler or redundancy.
Cluster CRUD plus combination, paginated domain retrieval, extraction with paging, and signature discovery give near-complete coverage of the stated domain. The only minor gap is in-place cluster editing (adding or removing domains without building a new cluster), though the description notes this workaround costs nothing.
Available Tools
11 toolsaccountAccount and quotaARead-onlyIdempotentInspect
The account behind the token: the current time (now, UTC), plan, searches used today and left, rate limit, result limits, extraction points left for today (clusters.extract_points_left). Spends nothing. In clusters, max is how many clusters the account can keep and max_size how many websites one can hold.
Inputs: no named parameters.
build_signaturesBuild signatures of a clusterARead-onlyIdempotentInspect
Find signatures that lead to more websites like the ones in a cluster: their common platform, theme, plugin, tracker, network or owner. Each result is a ready search - pass its search (the query in double quotes) to the search tool to find more such websites. Best on a cluster made by one search or of one network; a mixed cluster may give none. Sorted best first; take the one with the highest in_cluster - how many of the websites looked at have the code (coverage: "4 of 5", in_all: every one of them), websites - rough count in the whole index (null when rarer than websites_max; the search gives the exact number), technology - its name when the code belongs to a technology we know. Spends nothing.
Inputs: cluster (required).
combine_clustersCombine clustersBInspect
A new cluster from existing ones: 'and' - domains in every cluster, 'or' - in any of them, 'diff' - the first cluster minus the second (exactly two, order matters): clusters [7, 3] keeps the domains of 7 that are not in 3. Spends nothing.
Inputs: clusters (required), operation (required), name.
create_clusterCreate a clusterAInspect
Save a list of websites as a cluster, to extract data from them or combine with other clusters. From a search: pass 'query' (PublicWWW syntax, as in the search tool) - the cluster takes the results up to the plan's limit, and it costs one search. With like: that is the plan's maximum, so pass limit. From a list: pass 'domains' - names or urls; only sites in the index are kept (a www. name missing from the index is looked up without the www), nothing is spent; if none is in the index, no cluster is created. 'dropped' in the answer counts what was left out: not_a_domain, duplicate, not_in_index, over_limit. The plan caps the size of a cluster. To keep only some of a cluster's sites, make a new one from those domains: it costs nothing.
Inputs: name, limit, query, domains.
delete_clusterDelete a clusterADestructiveIdempotentInspect
Delete a cluster for good. It cannot be undone - confirm with the user first.
Inputs: cluster (required).
extract_from_clusterExtract data from a clusterAInspect
Pull values out of the page source of every website in a cluster: organization names, contacts, social profiles, addresses, languages, registration numbers, analytics and tag ids - anything a regular expression can match. Easiest: fields - name (organization name and kind of business from schema.org markup); social (social profile links, regional networks too (VK, Weibo, Naver...)); email (email addresses: mailto: links, schema.org, addresses hidden by Cloudflare); phone (phone numbers: tel: links and schema.org); messengers (messenger links: WhatsApp, Telegram, Viber, LINE, KakaoTalk, WeChat, Messenger, Signal, Zalo, Threema); address (postal address from schema.org markup and map coordinates (embedded maps, geo tags)); apps (app store links: Google Play, App Store, AppGallery, Microsoft Store, RuStore, Galaxy Store, Chrome Web Store, Firefox Add-ons); languages (languages of the pages, ISO 639 codes (html lang, hreflang)); registration (company registration and tax numbers: VAT, HRB, SIREN/SIRET, KvK, CNPJ, ABN, ИНН/ОГРН, ICP and more). Single networks by name - presets: email, phone, whatsapp, telegram, viber, line, facebook, instagram, x, linkedin, youtube, tiktok, pinterest, threads, bluesky, discord, github, google_play, app_store. Or write regex: PCRE in slashes, the first capture group is the value (with no group, the whole match), e.g. /data-site-id="([0-9]+)"/i. Up to 10 presets and expressions, one column each; fields add their columns. Works through the cluster in parts of up to 100 domains: call again with offset = next_offset until it is null. Costs extraction points: a website found in the index costs 1 point if anything was found, 0.1 if nothing; the account tool shows the daily allowance. It reads every indexed page of a website, not only the home page. Every call is paid for, a repeat of the same websites too: keep the answer and go on from next_offset. The REST API gives the same as a file (format=csv). A worked example, from a niche to contacts: the read_docs page clusters/example-contacts.
Inputs: cluster (required), limit, regex, fields, +3 more.
get_clusterDomains in a clusterCRead-onlyIdempotentInspect
A page of the domains in one cluster. Spends nothing.
Inputs: cluster (required), page, rows.
list_clustersList clustersARead-onlyIdempotentInspect
The account's clusters - saved lists of websites - newest first: id, name, number of domains, creation time. An account keeps at most 100. Spends nothing.
Inputs: no named parameters.
read_docsPublicWWW documentation and pricesARead-onlyIdempotentInspect
PublicWWW's own documentation and price list, in Markdown: query syntax and operators, websites about a topic (like:), regular expressions (snipexp:), country domains, ready-made example queries, clusters and extraction, the REST API, this MCP server, site languages, plans and prices with what each plan opens. Without page or pages - the table of contents, every page with the headings inside it. Read every page that may matter at once: several ids in pages. Use it for any question about how PublicWWW works or what it costs. Spends nothing.
Inputs: lang, page, pages.
rename_clusterRename a clusterBIdempotentInspect
Give a cluster a new name. Spends nothing.
Inputs: name (required), cluster (required).
searchSearch page sourceARead-onlyIdempotentInspect
Find websites whose page source (HTML, JavaScript, CSS) contains a string: a library name, a script url, a tracking or widget id, a meta tag, any code fragment. Results are ranked by site popularity. Look a technology up by its ready-made query on the examples pages (read_docs: the Technologies pages listed in its table of contents), not by its name. Query syntax: quote an exact phrase ("angular.min.js"); inside quotes punctuation only separates words: "jquery-ui.min.js" finds the words jquery, ui, min, js in that order; several words must all appear; a leading minus excludes a word (-wordpress); | means OR; site:de limits to a top-level domain, site:example.com lists the pages of one site, -site:com or -site:example.com leaves them out; depth:all searches inner pages too (by default only home pages, one per site) - then total counts pages, and sites counts the distinct websites among them (a lower bound when sites_exact is false; without depth: there is no sites). Websites about a topic or like a given one, most similar first instead of by popularity: like:"a few words" - websites about that topic, in any language, by meaning rather than the exact words (site:de keeps only that domain zone); like:example.com - websites about the same thing as that one (it compares home pages: when a shop or landing page has too little text there, the search finds nothing - describe the topic in words instead); with words, like: orders their results. like: is the topic of a site, not its code: websites that share code with given ones are found by build_signatures on a cluster of them. With like:, total counts everything the filters let through: read the first rows rather than total. rank is the place by popularity, 1 being the most popular, an estimate with no guarantees. More operators are in read_docs. Searches count against the account's daily allowance. At most 10 calls a minute of search and the cluster tools, shared with the REST API; account and read_docs do not count. On too_many_requests wait retry_after seconds. Ask for a small number of rows first.
Inputs: query (required), page, rows, snippets.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Source code search for every package on PyPI and npm.
Search websites by source code, technology stack, analyze domains, and download lead lists.
Web search from an independent index, with page and site facts, backlinks and stored page text.
Web search for agents: page to Markdown, screenshots, news search, metadata, sitemaps and RDAP.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables users to fetch a page's raw HTML as a real browser would, render it view-source style with line numbers and highlighted matches, and capture proof screenshots. Also returns matched line numbers and text so findings can be cited without taking a shot.2MIT

@searchcode/mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to search public web source code, identify site technologies, and investigate domains via searchcode.ai.13 npmMIT- MIT
- FlicenseNot gradedqualityDmaintenanceSemantic search over local source repositories and forum archives, exposing tools to list sources, search code, read code, and search forum discussions.-
Glama MCP Gateway
Add one secure layer between your agents and this server.