Web Intel
Server Details
8 pay-per-call web intel tools over MCP. Free discovery, calls settle in USDC on Base (x402).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 9 of 9 tools scored.
Most tools have distinct purposes (e.g., domain health, Shopify intelligence, content extraction). However, tech-stack-detector and tech-stack-change-detector overlap significantly; the latter adds diffing but shares the same base detection, which could cause confusion.
All tools use descriptive hyphenated names except 'pricing_info' which uses an underscore. This minor inconsistency prevents a perfect score, but the overall pattern is clear and readable.
With 9 tools covering domain health, e-commerce (Shopify, Zid), tech stack, and content extraction, the count feels well-scoped for a web intelligence server. Each tool adds a distinct capability without bloat.
The tool set covers core web intel needs: domain validation, e-commerce store data, tech stack detection, and content extraction (sitemap, URL-to-markdown, structured JSON). Minor gaps include lack of WHOIS, historical data, or broader crawling, but the set is functional.
Available Tools
9 toolsdomain-health-checkerInspect
Bulk-audit domains: DNS records, SSL certificate expiry, SPF & DMARC email authentication. Find domains that cannot receive email, are easy to spoof, or have expiring certificates — before your clients do. — $0.01/call, x402 (USDC on base).
| Name | Required | Description | Default |
|---|---|---|---|
| domains | Yes | List of domains to audit (e.g. `example.com`). | |
| maxConcurrency | No | How many domains to check in parallel. |
pricing_infoInspect
Free — list every paid tool in the 'web-intel' bundle with its price, payTo address and network. Call this first if you don't have a wallet ready yet.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
shopify-store-intelligenceInspect
Confirm a site runs on Shopify and pull store intelligence from its public feeds — product count, price range, top vendors/categories, newest listing and a rough revenue-band heuristic. No login, no Shopify API key. — $0.01/call, x402 (USDC on base).
| Name | Required | Description | Default |
|---|---|---|---|
| websites | Yes | List of websites to check (e.g. `allbirds.com` or `https://example.com`). One row per site. | |
| maxConcurrency | No | How many websites to check in parallel. |
sitemap-to-knowledgeInspect
Give it a domain. It reads the sitemap, fetches the pages, strips them to clean text and splits everything into ~1000-char chunks — one dataset row per chunk, ready to embed into a vector store. No browser, no LLM, no API key. — $0.02/call, x402 (USDC on base).
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | List of domains or website URLs to crawl via their sitemap. One entry per site. | |
| maxConcurrency | No | How many SITES to process in parallel (each site already fetches up to 25 pages internally). |
structured-extractInspect
Turn any URL into clean structured JSON — title, description, image, JSON-LD, headings, links, emails and prices — extracted deterministically via regex. Zero LLM calls, zero API keys. Built for AI agents that need one page turned into typed data, cheaply. — $0.01/call, x402 (USDC on base).
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | List of URLs to extract structured data from. One row per URL. | |
| fields | No | Optional subset of fields to return: title, description, image, siteName, canonical, jsonLd, headings, links, emails, prices. Leave empty to extract all of them. | |
| maxConcurrency | No | How many URLs to process in parallel. |
tech-stack-change-detectorInspect
Detect a website's current technologies (CMS, ecommerce, analytics, marketing/CRM, framework, hosting/CDN, chat, payments) and diff it against a previously-seen stack you supply, so you get exactly what was added or removed. No browser, no proxies, no login. — $0.01/call, x402 (USDC on base).
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | One entry per domain. Bare form: "example.com" (just detects the current stack). Diff form: "example.com|Tech1,Tech2,Tech3" — everything after the pipe is the stack you last saw for this domain; the Actor returns what was added/removed vs. right now. | |
| maxConcurrency | No | How many domains to check in parallel. |
tech-stack-detectorInspect
Detect the technologies a website runs — CMS, ecommerce platform, analytics, marketing/CRM, JS framework, hosting/CDN, chat and payments — straight from its public HTML and HTTP headers. No browser, no proxies, no login. Built for sales targeting and competitive research. — $0.01/call, x402 (USDC on base).
| Name | Required | Description | Default |
|---|---|---|---|
| websites | Yes | List of websites to fingerprint (e.g. `shopify.com` or `https://example.com`). One row per site. | |
| maxConcurrency | No | How many websites to fingerprint in parallel. |
url-to-markdownInspect
Fetch any URL and convert it into clean, LLM-ready Markdown — headings, links, lists and emphasis preserved, scripts/nav/ads stripped. No browser, no LLM calls, no API key. Built for RAG pipelines and AI agents that need one page turned into readable text, cheaply. — $0.01/call, x402 (USDC on base).
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | List of URLs to fetch and convert to Markdown. One row per URL. | |
| includeLinks | No | Convert <a href> tags to Markdown links. Turn off to strip links and keep only their text. | |
| maxConcurrency | No | How many URLs to fetch and convert in parallel. |
zid-store-productsInspect
Pull live product catalogs (name, price, sale price, category, image) straight from Zid storefronts — a common Saudi/Gulf e-commerce SaaS — via their own public JSON feed. No login, no browser, no proxies. — $0.02/call, x402 (USDC on base).
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | One entry per Zid storefront — the shop's subdomain (e.g. `furniture`) or full host (`furniture.zid.store`). Find the subdomain in the store's own zid.store URL, or via its custom domain's storefront (Zid stores usually keep the *.zid.store host reachable even with a custom domain attached). | |
| maxConcurrency | No | How many shops to scan in parallel. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!