MCPFax URL Intelligence
REMOTE · URL-INTEL.BOWLING-ANTHONY.WORKERS.DEV
Where a link really goes, what the server says about itself, and what pages a site publishes.
Available components
Last scanned (5 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 677 tokens (~135/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 28 Sept 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
- 25 Sept 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
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 0
- Server version: 1.0.0 → 1.0.1 functional
- 31 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “resolve_url” rewrote its description, which is the text the model reads security
- Tool “site_pages” rewrote its description, which is the text the model reads security
- Tool “url_headers” rewrote its description, which is the text the model reads security
- 26 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
- 25 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Aug 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 5 Nov 2026 · Probed https://url-intel.bowling-anthony.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bowling-anthony.workers.dev | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 99977672261024f133ad95ab21127b5 |
| SANs: bowling-anthony.workers.dev, *.bowling-anthony.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of url-intel.bowling-anthony.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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://url-intel.bowling-anthony.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://url-intel.bowling-anthony.workers.dev/mcp | Inconclusive | 405 |
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 →
demand_report What agents are asking for most (free) ~57
FREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | Window in days, default 30, max 90. |
No output schema declared.
No examples provided.
request_data Tell us what data you are looking for (free) ~88
FREE, no payment. Describe in your own words the data you are trying to buy — anything, not just URLs — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, only the words of the request.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | What you are looking for. |
No output schema declared.
No examples provided.
resolve_url Where does this link actually go? ~138
Follow a URL's redirect chain one hop at a time and report every step: each intermediate host and status, the final destination, whether it crossed to a different host, and a cleaned copy with tracking parameters (utm_*, fbclid, gclid and friends) stripped. Use before following or showing a shortened, tracked or unfamiliar link — a shortener cannot hide its destination from this. Stops after 10 hops, and refuses to follow a redirect into private address space. Costs $0.005 USDC per call via x402 on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to resolve, e.g. a shortened or tracked link. |
No output schema declared.
No examples provided.
site_pages What pages does this site publish? ~138
The pages a site declares in its sitemap, with last-modified dates, located via robots.txt first and the conventional /sitemap.xml second. Use to enumerate a documentation set or a blog archive before deciding what to read, instead of crawling blindly. A sitemap index is reported as such, so you know to call again for the child sitemaps. Costs $0.008 USDC per call via x402 on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Maximum entries to return. Default 200, maximum 1000. |
| url | string | yes | Site root (e.g. 'https://example.com') or a sitemap URL directly. |
No output schema declared.
No examples provided.
url_headers What a host says about itself ~109
Response status, server software, content type, caching, and which of the six standard security headers the host sets or omits. Use to check a URL is live and well-formed before relying on it, or to profile a site cheaply without downloading it. Header presence is a hygiene signal, not a safety verdict — a site can set every header and still be malicious. Costs $0.005 USDC per call via x402 on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to inspect. |
No output schema declared.
No examples provided.
How do I install the MCPFax URL Intelligence MCP server?
MCPFax URL Intelligence is a hosted endpoint at https://url-intel.bowling-anthony.workers.dev/mcp, 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 · url-intel.bowling-anthony.workers.dev
claude mcp add --transport http com-mcpscores-url-intel 'https://url-intel.bowling-anthony.workers.dev/mcp'
What is the MCPFax URL Intelligence MCP server?
MCPFax URL Intelligence is an MCP server listed in the public MCP registry as com.mcpscores/url-intel. Where a link really goes, what the server says about itself, and what pages a site publishes. This page covers its hosted endpoint (https://url-intel.bowling-anthony.workers.dev/mcp).
Is the MCPFax URL Intelligence MCP server safe to use?
MCPFax URL Intelligence scores 74 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 MCPFax URL Intelligence MCP server expose?
MCPFax URL Intelligence exposes 5 tools: request_data, demand_report, resolve_url, url_headers, site_pages. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.
Does the MCPFax URL Intelligence MCP server require authentication?
No. We connected to MCPFax URL Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCPFax URL Intelligence MCP server still maintained?
MCPFax URL Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.