Skip to main content
Glama
pleamo

pleamo

Official
by pleamo

pleamo MCP server

Exposes pleamo's AI scam/phishing URL checks as MCP tools, so any MCP client (Claude Desktop, Cursor, your own agent) can ask pleamo "is this link safe?" before opening or recommending it.

It's a thin, authenticated proxy to the hosted pleamo API — every check goes through the same per-user and global caps that protect the service.

Tools

Tool

What it does

check_url

Judge a URL: verdict (safe/suspicious/dangerous), severity, confidence, reason

report_false_positive

Flag a wrongly-blocked domain for review

get_status

Your plan + today's AI-check usage

Related MCP server: Verdict

Setup

  1. Get a pleamo API key (a revocable key from the dashboard at https://dash.pleamo.app/keys).

  2. Point your MCP client at this server. For Claude Desktop, add to claude_desktop_config.json:

{
  "mcpServers": {
    "pleamo": {
      "command": "npx",
      "args": ["-y", "pleamo-mcp"],
      "env": {
        "PLEAMO_TOKEN": "your-api-key-here"
      }
    }
  }
}

Restart the client. You'll then be able to say things like "check this link with pleamo: https://paypa1-login.example" and the agent will call check_url.

Environment

Var

Default

Notes

PLEAMO_TOKEN

—

Required. Bearer token for the pleamo API.

PLEAMO_API_BASE

https://dash.pleamo.app

Override for local dev (e.g. http://localhost:4400).

Develop

npm install
npm run verify   # lint + format + unit tests
npm start        # runs the stdio server (expects an MCP client on stdin)

Quick stdio smoke test (lists the tools):

printf '%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"smoke","version":"0"}}}' \
  '{"jsonrpc":"2.0","method":"notifications/initialized"}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \
  | node src/server.js

Remote (hosted) alternative

If your client supports remote MCP servers, you don't need this local process at all — connect straight to the hosted endpoint:

https://dash.pleamo.app/api/mcp

It speaks JSON-RPC over HTTP (same three tools) and authenticates with a pleamo API key as a Bearer token. Create a revocable key at https://dash.pleamo.app/keys. This local stdio server is for clients that only speak stdio (e.g. current Claude Desktop).

Notes

  • Auth / tokens — get a revocable API key from the dashboard (/keys) and set it as PLEAMO_TOKEN. (A raw session token also works, but keys are the right, revocable option.)

  • Transport — this package is stdio; the hosted /api/mcp above is the remote Streamable-HTTP variant.

  • The other MCP direction — letting the extension route checks through the user's own agent (BYO-via-MCP) is tracked alongside the extension source at pleamo/pleamo-chrome-extension.

Available Tools

3 tools
check_urlCheck a URL for scams / phishingA

Ask pleamo whether visiting a URL is likely a scam or phishing site. Returns a verdict (safe/suspicious/dangerous), severity, confidence, and a plain-English reason. Use before opening or recommending an unfamiliar link.

Inputs: url (required).

get_statusGet pleamo plan + usageA

Return the signed-in account's plan and today's AI-check usage.

Inputs: no named parameters.

report_false_positiveReport a wrongly-flagged siteA

Tell pleamo a domain was flagged incorrectly, so it can be reviewed and corrected.

Inputs: domain (required), note.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: check_url analyzes a URL, report_false_positive submits a correction, and get_status returns account information. There is no meaningful overlap or ambiguity among the three.

    Naming Consistency5/5

    All tool names follow the same verb_noun pattern using snake_case: check_url, report_false_positive, get_status. This makes the tool set predictable and easy to navigate.

    Tool Count5/5

    With only three tools, the server is tightly scoped to its purpose: URL safety checking, correction feedback, and account status. Each tool earns its place and the count is appropriate for such a focused service.

    Completeness5/5

    The tool set covers the core workflow: checking URLs, reporting incorrect verdicts, and checking usage/plan status. There are no obvious dead ends or missing operations for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to check suspicious text, emails, marketplace listings, job offers, investment pitches, and links through MCP tools, returning an assessment with supporting checks and next-step guidance.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to look up domains, URLs, IPs/ASNs, email addresses, phone numbers, crypto wallets, and business records; run autonomous investigations; collect crawl artifacts; and perform evidence-backed scam checks with traceable provenance.
      MIT