# 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.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `url-intel.bowling-anthony.workers.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-mcpscores-url-intel/url-intel.md), [page](https://verifymcp.io/servers/com-mcpscores-url-intel/url-intel)

## Channel facts

- Endpoint: `https://url-intel.bowling-anthony.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-mcpscores-url-intel 'https://url-intel.bowling-anthony.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mcpscores-url-intel": {
      "url": "https://url-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mcpscores-url-intel": {
      "type": "http",
      "url": "https://url-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mcpscores-url-intel]
url = "https://url-intel.bowling-anthony.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcpscores-url-intel": {
      "type": "remote",
      "url": "https://url-intel.bowling-anthony.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mcpscores-url-intel --url 'https://url-intel.bowling-anthony.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mcpscores-url-intel:
    url: "https://url-intel.bowling-anthony.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mcpscores-url-intel": {
      "Transport": "http",
      "Url": "https://url-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mcpscores-url-intel -t streamable-http -u 'https://url-intel.bowling-anthony.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mcpscores-url-intel": {
      "type": "http",
      "url": "https://url-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 66, +1)

- [functional] Server version: 1.0.0 → 1.0.1

## MCP tools (5)

### `request_data` (~88 tokens)

Tell us what data you are looking for (free)

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.

Input parameters:

- `need` (string, required): What you are looking for.

### `demand_report` (~57 tokens)

What agents are asking for most (free)

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.

Input parameters:

- `days` (string): Window in days, default 30, max 90.

### `resolve_url` (~138 tokens)

Where does this link actually go?

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.

Input parameters:

- `url` (string, required): The URL to resolve, e.g. a shortened or tracked link.

### `url_headers` (~109 tokens)

What a host says about itself

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.

Input parameters:

- `url` (string, required): The URL to inspect.

### `site_pages` (~138 tokens)

What pages does this site publish?

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.

Input parameters:

- `limit` (string): Maximum entries to return. Default 200, maximum 1000.
- `url` (string, required): Site root (e.g. 'https://example.com') or a sitemap URL directly.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mcpscores-url-intel/url-intel#diagnostics

## Score history

- 2026-09-20: 73
- 2026-09-19: 72
- 2026-09-18: 72
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 70
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 67
- 2026-09-07: 67
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 65
- 2026-09-03: 65
- 2026-09-02: 64
- 2026-09-01: 64
- 2026-08-31: 63
- 2026-08-30: 63
- 2026-08-29: 63
- 2026-08-28: 62
- 2026-08-27: 62
- 2026-08-26: 61
- 2026-08-25: 59
- 2026-08-24: 59

## Common questions

### 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 73 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://url-intel.bowling-anthony.workers.dev/mcp
- Website: https://mcpscores.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-mcpscores-url-intel/url-intel.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mcpscores-url-intel/url-intel.json
- HTML version of this page: https://verifymcp.io/servers/com-mcpscores-url-intel/url-intel