# Aya scam check (remote · mcp.autosecurelogin.com)

Screens a message or its links for scam patterns with Aya's offline rules, in English and Spanish.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.autosecurelogin.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-autosecurelogin-aya-scam-check/aya-mcp.md), [page](https://verifymcp.io/servers/com-autosecurelogin-aya-scam-check/aya-mcp)

## Channel facts

- Endpoint: `https://mcp.autosecurelogin.com/aya/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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 341 tokens (~170/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Aya scam check MCP server?

Aya scam check is a hosted endpoint at https://mcp.autosecurelogin.com/aya/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-autosecurelogin-aya-scam-check 'https://mcp.autosecurelogin.com/aya/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-autosecurelogin-aya-scam-check": {
      "url": "https://mcp.autosecurelogin.com/aya/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-autosecurelogin-aya-scam-check": {
      "type": "http",
      "url": "https://mcp.autosecurelogin.com/aya/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-autosecurelogin-aya-scam-check]
url = "https://mcp.autosecurelogin.com/aya/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-autosecurelogin-aya-scam-check --url 'https://mcp.autosecurelogin.com/aya/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-autosecurelogin-aya-scam-check:
    url: "https://mcp.autosecurelogin.com/aya/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-autosecurelogin-aya-scam-check": {
      "Transport": "http",
      "Url": "https://mcp.autosecurelogin.com/aya/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-autosecurelogin-aya-scam-check -t streamable-http -u 'https://mcp.autosecurelogin.com/aya/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-autosecurelogin-aya-scam-check": {
      "type": "http",
      "url": "https://mcp.autosecurelogin.com/aya/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-11-04 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 73)

First indexed and scored.

## MCP tools (2)

### `scam_check` (~157 tokens)

Screen a message for scam patterns

Score a text, email, chat or voicemail transcript against Aya's scam rules (urgency, hard-to-reverse payments, credential and code requests, government or tech-support impersonation, prizes, family emergencies, deposits to unlock earnings, disguised links) in English or Spanish. Returns the risk level and score, the reasons, what to do now and what to do if the person already acted. Runs locally; the message is not stored or sent anywhere.

Input parameters:

- `message` (string, required): The message text as received (links may be written as hxxp or with [.]).
- `repeatedContact` (boolean): True when the sender has contacted the person repeatedly.
- `unknownSender` (boolean): True when the sender is not a saved contact.

### `link_check` (~76 tokens)

Inspect links without visiting them

Extract up to 8 links from a text and judge each by its shape alone: brand lookalikes, raw IP hosts, shorteners, encoded international domains, risky suffixes, many subdomains or hyphens, credential-style paths. Nothing is fetched or resolved.

Input parameters:

- `text` (string, required): Text containing one or more links.

## Diagnostics

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

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73

## Common questions

### What is the Aya scam check MCP server?

Aya scam check is an MCP server listed in the public MCP registry as com.autosecurelogin/aya-scam-check. Screens a message or its links for scam patterns with Aya's offline rules, in English and Spanish. This page covers its hosted endpoint (https://mcp.autosecurelogin.com/aya/mcp).

### Is the Aya scam check MCP server safe to use?

Aya scam check 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 Aya scam check MCP server expose?

Aya scam check exposes 2 tools: scam_check, link_check. Their descriptions and schemas cost roughly 233 tokens of context every time the server is loaded.

### Does the Aya scam check MCP server require authentication?

No. We connected to Aya scam check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Aya scam check MCP server still maintained?

Aya scam check 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.

### What did VerifyMCP test on the Aya scam check MCP server?

VerifyMCP ran 13 checks on Aya scam check, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.autosecurelogin.com/aya/mcp
- Website: https://aya.autosecurelogin.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-autosecurelogin-aya-scam-check/aya-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-autosecurelogin-aya-scam-check/aya-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-autosecurelogin-aya-scam-check/aya-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-autosecurelogin-aya-scam-check/aya-mcp