Web Intel
REMOTE · API.TIMZININ.COM · SCANNED SEP 20
8 pay-per-call web intel tools over MCP. Free discovery, calls settle in USDC on Base (x402).
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1608 tokens (~160/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Web Intel MCP server?
Web Intel is a hosted endpoint at https://api.timzinin.com/mcp/web-intel, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.timzinin.com
claude mcp add --transport http com-timzinin-api-web-intel 'https://api.timzinin.com/mcp/web-intel'
{
"mcpServers": {
"com-timzinin-api-web-intel": {
"url": "https://api.timzinin.com/mcp/web-intel"
}
}
} {
"servers": {
"com-timzinin-api-web-intel": {
"type": "http",
"url": "https://api.timzinin.com/mcp/web-intel"
}
}
} [mcp_servers.com-timzinin-api-web-intel] url = "https://api.timzinin.com/mcp/web-intel"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-timzinin-api-web-intel": {
"type": "remote",
"url": "https://api.timzinin.com/mcp/web-intel",
"enabled": true
}
}
} openclaw mcp add com-timzinin-api-web-intel --url 'https://api.timzinin.com/mcp/web-intel' --transport streamable-http
mcp_servers:
com-timzinin-api-web-intel:
url: "https://api.timzinin.com/mcp/web-intel" {
"McpServers": {
"com-timzinin-api-web-intel": {
"Transport": "http",
"Url": "https://api.timzinin.com/mcp/web-intel"
}
}
} assistant mcp add com-timzinin-api-web-intel -t streamable-http -u 'https://api.timzinin.com/mcp/web-intel'
{
"mcpServers": {
"com-timzinin-api-web-intel": {
"type": "http",
"url": "https://api.timzinin.com/mcp/web-intel"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Aug 26 0
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 142 → 160 ▼ functional
- Tool “domain-health-checker” changed its title: Domain Health Checker cosmetic
- Tool “pricing_info” changed its title: Pricing — Web & Content Intelligence cosmetic
- Tool “shopify-price-change-monitor” changed its title: Shopify Price Change Monitor cosmetic
- Tool “shopify-store-intelligence” changed its title: Shopify Store Intelligence cosmetic
- Tool “sitemap-to-knowledge” changed its title: RAG Dataset Builder cosmetic
- Tool “structured-extract” changed its title: Structured Data Extractor cosmetic
- Tool “tech-stack-change-detector” changed its title: Tech Stack Change Detector cosmetic
- Tool “tech-stack-detector” changed its title: Website Tech Stack Detector cosmetic
- Tool “url-to-markdown” changed its title: URL to Markdown Converter cosmetic
- Tool “zid-store-products” changed its title: Zid Store Products Scraper cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- The server changed its declared name: zinin-corp-apify-hub-web-intel → zinin-m2m-hub-web-intel security
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.timzinin.com/mcp/web-intel
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.timzinin.com | CN=YE1,O=Let's Encrypt,C=US | 27 Jul 2026 | 25 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5ef393ac3b7ccb852f589ba8f412cb7232f |
| SANs: api.timzinin.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.timzinin.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| timzinin.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.timzinin.com/mcp/web-intel | Verified | 200 | |
| http (plaintext) | http://api.timzinin.com/mcp/web-intel | HTTPS enforced | 301 | https://api.timzinin.com/mcp/web-intel |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
domain-health-checker Domain Health Checker ~103
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 | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | List of domains to audit (e.g. `example.com`). |
| maxConcurrency | integer | – | How many domains to check in parallel. |
No output schema declared.
No examples provided.
pricing_info Pricing — Web & Content Intelligence ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
shopify-price-change-monitor Shopify Price Change Monitor ~259
Watches a Shopify store's catalogue and returns only the products whose price or availability changed since the previous check. The first run creates the baseline and says so. — $0.05/call, x402 (USDC on base).
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_key | string | – | A name for THIS watch, so you can run several independent store watches from one Actor (e.g. "dtc-competitors", "my-portfolio") without one overwriting another's memory of what's already been seen. E… |
| max_items | integer | – | Caps how many new-store / changed-store rows a single run will deliver and charge for, even if more were found. |
| websites | array | yes | Shopify (or possibly-Shopify) store URLs to watch, e.g. "allbirds.com". Every scheduled run re-checks these same sites and reports ONLY what changed since a previous run of this watch: a store newly… |
No output schema declared.
No examples provided.
shopify-store-intelligence Shopify Store Intelligence ~116
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 | Type | Req | Description |
|---|---|---|---|
| maxConcurrency | integer | – | How many websites to check in parallel. |
| websites | array | yes | List of websites to check (e.g. `allbirds.com` or `https://example.com`). One row per site. |
No output schema declared.
No examples provided.
sitemap-to-knowledge RAG Dataset Builder ~132
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 | Type | Req | Description |
|---|---|---|---|
| items | array | yes | List of domains or website URLs to crawl via their sitemap. One entry per site. |
| maxConcurrency | integer | – | How many SITES to process in parallel (each site already fetches up to 25 pages internally). |
No output schema declared.
No examples provided.
structured-extract Structured Data Extractor ~159
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 | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Optional subset of fields to return: title, description, image, siteName, canonical, jsonLd, headings, links, emails, prices. Leave empty to extract all of them. |
| maxConcurrency | integer | – | How many URLs to process in parallel. |
| urls | array | yes | List of URLs to extract structured data from. One row per URL. |
No output schema declared.
No examples provided.
tech-stack-change-detector Tech Stack Change Detector ~169
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 | Type | Req | Description |
|---|---|---|---|
| items | array | 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… |
| maxConcurrency | integer | – | How many domains to check in parallel. |
No output schema declared.
No examples provided.
tech-stack-detector Website Tech Stack Detector ~128
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 | Type | Req | Description |
|---|---|---|---|
| maxConcurrency | integer | – | How many websites to fingerprint in parallel. |
| websites | array | yes | List of websites to fingerprint (e.g. `shopify.com` or `https://example.com`). One row per site. |
No output schema declared.
No examples provided.
url-to-markdown URL to Markdown Converter ~152
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 | Type | Req | Description |
|---|---|---|---|
| includeLinks | boolean | – | Convert <a href> tags to Markdown links. Turn off to strip links and keep only their text. |
| maxConcurrency | integer | – | How many URLs to fetch and convert in parallel. |
| urls | array | yes | List of URLs to fetch and convert to Markdown. One row per URL. |
No output schema declared.
No examples provided.
zid-store-products Zid Store Products Scraper ~163
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 | Type | Req | Description |
|---|---|---|---|
| items | array | 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… |
| maxConcurrency | integer | – | How many shops to scan in parallel. |
No output schema declared.
No examples provided.
What is the Web Intel MCP server?
Web Intel is an MCP server listed in the public MCP registry as com.timzinin.api/web-intel. 8 pay-per-call web intel tools over MCP. Free discovery, calls settle in USDC on Base (x402). This page covers its hosted endpoint (https://api.timzinin.com/mcp/web-intel).
Is the Web Intel MCP server safe to use?
Web Intel scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Web Intel MCP server expose?
Web Intel exposes 10 tools: pricing_info, domain-health-checker, shopify-price-change-monitor, shopify-store-intelligence, sitemap-to-knowledge, and 5 more. Their descriptions and schemas cost roughly 1,425 tokens of context every time the server is loaded.
Does the Web Intel MCP server require authentication?
No. We connected to Web Intel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Web Intel MCP server still maintained?
Web Intel is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.