Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

74 Trust /100

Last scanned (1 hour ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 4 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 73

    First indexed and scored.

Diagnostics

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://mcp.autosecurelogin.com/aya/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.autosecurelogin.com CN=YE1,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 55fbecac6de1201486d2f7d1f79b0d2f5ea
SANs: mcp.autosecurelogin.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 mcp.autosecurelogin.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
autosecurelogin.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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.autosecurelogin.com/aya/mcp Verified 200
http (plaintext) http://mcp.autosecurelogin.com/aya/mcp HTTPS enforced 301 https://mcp.autosecurelogin.com/aya/mcp
MCP tools · 2 exposed · ~233 tokens

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 →

Tool Tokens
link_check ~76

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.

NameTypeReqDescription
textstringyesText containing one or more links.

No output schema declared.

No examples provided.

scam_check ~157

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.

NameTypeReqDescription
messagestringyesThe message text as received (links may be written as hxxp or with [.]).
repeatedContactboolean–True when the sender has contacted the person repeatedly.
unknownSenderboolean–True when the sender is not a saved contact.

No output schema declared.

No examples provided.

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.

remote · mcp.autosecurelogin.com

# add to Claude Code
claude mcp add --transport http com-autosecurelogin-aya-scam-check 'https://mcp.autosecurelogin.com/aya/mcp'
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.