mcpField
W
website-intelligence

website-intelligence

Local
github.com/asheeranBrowser Automation0Updated 2w ago

About website-intelligence

website-intelligence is an MCP server offering ten website and domain research tools through the Sitesy API. It covers page content, metadata, DNS, sitemaps, links, and site checks, with each call paid in USDC on Base from the operator's wallet.

Key features

  1. 01Domain intelligence reports
  2. 02Page text and metadata extraction
  3. 03DNS and domain profiles
  4. 04Feed and sitemap reading
  5. 05Link maps and redirect traces
  6. 06Per-call USDC payments

Use cases

  1. 01Review a domain's public technical and security details
  2. 02Extract readable content and metadata from a page
  3. 03Inspect DNS records, feeds, sitemaps, or links

MCP support

It exposes ten website and domain tools to MCP clients. Calls use the Sitesy API and are paid per request in USDC on Base from a wallet configured by the server operator.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"asheeran-website-intelligence": {
"command": "npx",
"args": [
"-y",
"@getsitesy/website-intelligence"
],
"env": {
"PAYER_PRIVATE_KEY": "<PAYER_PRIVATE_KEY>",
"API_URL": "<API_URL>"
}
}
}
}
Run commandnpx -y @getsitesy/website-intelligence
Environment variables to set
PAYER_PRIVATE_KEYSecretPrivate key of the wallet that pays for each call. Fund it with a small amount of USDC on Base and a little ETH for network costs if the wallet sends its own transactions.
API_URLOptional override for the API base address. Defaults to https://api.sitesy.ca.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@getsitesy/website-intelligence1.0.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Sitesy Website Intelligence for MCP

Ten website and domain tools for AI agents, served by the Sitesy API at api.sitesy.ca and paid per call in USDC on Base through the x402 protocol. There is no account, no API key, and no subscription. Whoever runs this server pays for each call from their own wallet, which the server reads from an environment variable and never stores anywhere else.

The tools

ToolWhat it returnsPrice per call
website_intelligenceA full report for one domain: public contact details, tech stack clues, transport security, response headers, DNS records, certificate basics, and hygiene findings with severities0.01 USDC
page_readerClean readable text and metadata extracted from one web page0.01 USDC
domain_profileRegistration basics, a DNS summary, and subdomains drawn from public certificate logs0.01 USDC
feed_readerAn RSS, Atom, or RDF feed normalized into dated items with summaries0.005 USDC
dns_lookupThe full DNS record set for one domain: A, AAAA, CNAME, MX, NS, TXT, SOA, CAA0.002 USDC
page_metadataTitle, description, canonical, Open Graph and Twitter card tags, icons, and structured data types from one web page0.002 USDC
sitemapThe sitemaps a domain declares and the page addresses inside them0.002 USDC
page_linksThe links on one web page, split into internal and external, with anchor text0.002 USDC
site_checkA quick check: HTTPS reachability, HTTP behaviour, certificate days remaining, and security header presence0.001 USDC
redirect_traceEvery hop a web address takes, with each status and destination0.001 USDC

Quick start

Add the server to your MCP client configuration:

{
  "mcpServers": {
    "sitesy-website-intelligence": {
      "command": "npx",
      "args": ["-y", "@getsitesy/website-intelligence"],
      "env": {
        "PAYER_PRIVATE_KEY": "0xYOUR_WALLET_PRIVATE_KEY"
      }
    }
  }
}

Environment variables

PAYER_PRIVATE_KEY is required. It is the private key of the wallet that pays for calls. Use a wallet that holds only a small working balance of USDC on Base. Treat it the way you would treat any wallet key: keep it out of source control and out of shared configuration files.

API_URL is optional. It overrides the API base address and defaults to https://api.sitesy.ca.

How payment works

Each tool call asks the API for its result. The API answers with an x402 payment request, this server signs a payment of the listed price from the configured wallet, and the API returns the result as the payment settles on Base. Prices are per call and there are no other charges from the API side.

Safety notes

The tools read only what a normal visitor to a site receives, plus public DNS records, public registration data, and public certificate logs. The reader refuses addresses that resolve to private or local networks.

License

MIT. See LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.