Skip to main content
Glama
smijo-geek

ScamCheck MCP Server

by smijo-geek
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

ScamCheck MCP Server

Scan suspicious messages, URLs, and text for scams inside any AI assistant that supports MCP (Claude Desktop, Claude Code, Cursor, and more). No signup or API key needed — works out of the box on the free anonymous tier.

Quick start (no API key)

Add to your Claude Desktop / Cursor config:

{
  "mcpServers": {
    "scamcheck": {
      "command": "npx",
      "args": ["scamcheck-mcp-server"]
    }
  }
}

That's it. Ask your assistant "is this message a scam?" and paste the message.

Related MCP server: scamshield

Higher limits (optional API key)

The anonymous tier is rate-limited per IP. For higher limits, grab a free key at scamcheck.tech/dashboard/developer and add it:

{
  "mcpServers": {
    "scamcheck": {
      "command": "npx",
      "args": ["scamcheck-mcp-server"],
      "env": {
        "SCAMCHECK_API_KEY": "sk-live-your-key-here"
      }
    }
  }
}

Tool: scan_message

Parameter

Type

Required

Description

input

string

✓

The message, URL, or text to scan

source

text | url | screenshot

—

Content type (default: text)

Example response

🔴 Likely Scam — Risk Score: 89/100
Category: phishing · Confidence: 92%

Summary: This message impersonates a bank to steal credentials.

Why this was flagged:
• Creates false urgency with account suspension threat
• Uses a URL that does not match the official bank domain
• Requests sensitive personal information via link

What to do:
✓ Do not click any links in this message
✓ Contact your bank directly using the number on your card
✓ Report to your bank's fraud department

Full report: https://www.scamcheck.tech/result/abc123

Rate limits

  • Anonymous (no key): IP rate-limited

  • Free API key: 100 scans/month

  • Pro/Business: Unlimited

Available Tools

1 tool
scan_messageAInspect

Scan a suspicious message, URL, or text for scam indicators using ScamCheck AI. Returns a verdict (Likely Scam / Suspicious / Likely Safe), risk score (0-100), category, confidence, reasons flagged, and recommended actions. Use this whenever a user shares a message they received and wants to know if it's a scam.

ParametersJSON Schema
NameRequiredDescriptionDefault
inputYesThe message, URL, or text to scan. Minimum 8 characters. Can be SMS, email, WhatsApp message, job offer, or any suspicious content.
sourceNoThe type of content: 'text' for messages/emails, 'url' for links, 'screenshot' for OCR-extracted text. Default: text.text

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description details that the tool returns a verdict, risk score, category, confidence, reasons flagged, and recommended actions. This goes beyond the tool name, and no annotations are provided, so the description carries the full burden. No contradictory or missing behavioral info.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise and front-loaded with the primary action. Every sentence adds value without redundancy. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given only two parameters and no nested objects or output schema, the description fully covers purpose, usage, parameters, and expected output. No gaps or missing information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds context by explaining that input can be SMS, email, etc., and clarifies source types. It also mentions minimum 8 characters, which is not in the schema's 'description' field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool scans a suspicious message, URL, or text for scam indicators using ScamCheck AI, with specific verb 'scan' and resource 'suspicious content'. It distinguishes the tool's purpose well even without sibling context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this whenever a user shares a message they received and wants to know if it's a scam.' Provides clear context for when to use, though no exclusions or alternatives are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.1.1
    • First observedscan_message
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no ambiguity. The tool's purpose is clearly distinct as it targets a single action: scanning messages for scams.

Naming Consistency5/5

The single tool name 'scan_message' follows a clear verb_noun pattern, which is consistent and predictable.

Tool Count4/5

One tool is appropriate for a narrow, single-purpose server like ScamCheck. It slightly underrepresents potential additional features but is reasonable given the focused scope.

Completeness4/5

The tool covers the core functionality of scanning messages for scams. Minor gaps exist (e.g., no history or configuration), but the primary use case is fully addressed.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • scamshield

    vadapallimouli
    F
    license
    Not graded
    quality
    C
    maintenance
    MCP server for detecting and analyzing scams using various heuristics and data sources.
    -
  • Kaidn-mcp by Kaidn-io

    Kaidn-mcpofficial

    Kaidn-io
    A
    license
    A
    quality
    B
    maintenance
    Investigate fraud directly from Claude, Cursor, or any MCP-compatible client. Analyze suspicious activity with clear, evidence-backed verdicts. Pivot from a single signup to every account sharing the same device, IP address, or email inbox. Check entities against a cross-operator abuse network, review linked accounts, and efficiently process your fraud review queue. Read-only by default, with no r
    10
    230
    MIT

  • pathguard-mcp

    Utee
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables MCP-compatible AI agents to scan crypto transactions for scam addresses, clipboard-hijack patterns, and typos, as well as report scam addresses and check usage, directly in conversation.
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smijo-geek/scamcheck-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server