# com.cautellus/scam-detection (remote · cautellus.com)

Scam and phishing detection for AI agents: safe/warn/danger verdicts for URLs and messages.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `cautellus.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-cautellus-scam-detection/api-mcp.md), [page](https://verifymcp.io/servers/com-cautellus-scam-detection/api-mcp)

## Channel facts

- Endpoint: `https://cautellus.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 66/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 3 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 316 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.cautellus/scam-detection MCP server?

com.cautellus/scam-detection is a hosted endpoint at https://cautellus.com/api/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-cautellus-scam-detection 'https://cautellus.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cautellus-scam-detection": {
      "url": "https://cautellus.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cautellus-scam-detection": {
      "type": "http",
      "url": "https://cautellus.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cautellus-scam-detection]
url = "https://cautellus.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cautellus-scam-detection": {
      "type": "remote",
      "url": "https://cautellus.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cautellus-scam-detection --url 'https://cautellus.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cautellus-scam-detection:
    url: "https://cautellus.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cautellus-scam-detection": {
      "Transport": "http",
      "Url": "https://cautellus.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cautellus-scam-detection -t streamable-http -u 'https://cautellus.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cautellus-scam-detection": {
      "type": "http",
      "url": "https://cautellus.com/api/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-10-02 (score 80, +1)

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

### 2026-09-29 (score 79, +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-28 (score 78, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 78, +1)

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

### 2026-09-25 (score 77, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 76, +1)

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

### 2026-09-21 (score 75, +1)

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

### 2026-09-19 (score 74, +1)

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

## MCP tools (3)

### `scan_url` (~103 tokens)

Check a URL or domain for phishing and scam risk before visiting, clicking, or transacting with it. Returns a verdict (safe | warn | danger), a 0-100 risk score, a plain-English summary, and specific findings (brand impersonation, typosquatting, community scam reports, threat-feed hits). Costs 1 scan credit.

Input parameters:

- `url` (string, required): The URL or bare domain to analyze, e.g. "paypal-verify-login.xyz"

### `scan_message` (~88 tokens)

Analyze a message, email, or text for scam indicators before acting on it (payment requests, verification codes, urgency pressure, impersonation). Returns a verdict (safe | warn | danger), a 0-100 risk score, a summary, and specific findings. Costs 1 scan credit.

Input parameters:

- `message` (string, required): The full message text to analyze (up to 25,000 characters)

### `get_usage` (~32 tokens)

Check the API key’s remaining prepaid scan credits, monthly plan usage, and credit expiry. Free — consumes no credits.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cautellus-scam-detection/api-mcp#diagnostics

## Score history

- 2026-10-02: 80
- 2026-10-01: 79
- 2026-09-30: 79
- 2026-09-29: 79
- 2026-09-28: 78
- 2026-09-27: 78
- 2026-09-26: 77
- 2026-09-25: 77
- 2026-09-24: 76
- 2026-09-23: 76
- 2026-09-22: 75
- 2026-09-21: 75
- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 70
- 2026-09-10: 70
- 2026-09-09: 69
- 2026-09-08: 69
- 2026-09-07: 68
- 2026-09-06: 68

## Common questions

### What is the com.cautellus/scam-detection MCP server?

com.cautellus/scam-detection is an MCP server listed in the public MCP registry as com.cautellus/scam-detection. Scam and phishing detection for AI agents: safe/warn/danger verdicts for URLs and messages. This page covers its hosted endpoint (https://cautellus.com/api/mcp).

### Is the com.cautellus/scam-detection MCP server safe to use?

com.cautellus/scam-detection scores 80 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 com.cautellus/scam-detection MCP server expose?

com.cautellus/scam-detection exposes 3 tools: scan_url, scan_message, get_usage. Their descriptions and schemas cost roughly 223 tokens of context every time the server is loaded.

### Does the com.cautellus/scam-detection MCP server require authentication?

No. We connected to com.cautellus/scam-detection without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.cautellus/scam-detection MCP server still maintained?

com.cautellus/scam-detection is still listed as active in the MCP registry. We last reached this channel on 2 October 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://cautellus.com/api/mcp
- Website: https://cautellus.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-cautellus-scam-detection/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cautellus-scam-detection/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-cautellus-scam-detection/api-mcp