Aya scam check MCP server
com.autosecurelogin/aya-scam-checkautosecurelogin.comstreamable-httpv1.0.0Scanned
Screens a message or its links for scam patterns with Aya's offline rules, in English and Spanish.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Aya scam check MCP server can do
The Aya scam check MCP server is published by autosecurelogin.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: scam_check and link_check), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
link_checkExtract 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 h…2 findings
Why it is in this group
- The name "link_check" says "link": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...y suffixes, many subdomains or hyphens, credential-style paths. Nothing is fetched or reso..."
- Warn
The server marks "link_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "link_check" says "link": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
scam_checkScore 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 impersonatio…1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...les (urgency, hard-to-reverse payments, credential and code requests, government or tech-s..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.autosecurelogin.com/aya/mcp: tools/list returned 2 tools to an anonymous client, including scam_check (write), link_check (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnlink_check
The server marks "link_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "link_check" says "link": a word for a change.
- Infoscam_check
The description mentions "credential".
What this check looks forMatched text
description: "...les (urgency, hard-to-reverse payments, credential and code requests, government or tech-s..."
- Infolink_check
The description mentions "credential".
What this check looks forMatched text
description: "...y suffixes, many subdomains or hyphens, credential-style paths. Nothing is fetched or reso..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http aya-scam-check https://mcp.autosecurelogin.com/aya/mcpclaude mcp add --transport http aya-scam-check https://mcp.autosecurelogin.com/aya/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__aya-scam-check__scam_check",
"mcp__aya-scam-check__link_check"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as aya-scam-check. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.autosecurelogin/aya-scam-check/verify?hash=985ee7c1fa0d4eb7ed460b328e12829f088f0ad39b4afa4cee49509521a2b650" | jq -e '.changed == false'Pinned hash 985ee7c1fa0d, from Nov 16, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.autosecurelogin/aya-scam-check/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.autosecurelogin/aya-scam-check)Source: MCP Registry. Synced Nov 3, 2026, 08:17 UTC.
Aya scam check MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Aya scam check MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Aya scam check MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Aya scam check MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Aya scam check MCP server have?
- 2 tools: 2 write. scam_check and link_check.
Does the Aya scam check MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Aya scam check MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Aya scam check MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.