pleamo
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pleamo Check this URL for scam: https://example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| Judge a URL: verdict (safe/suspicious/dangerous), severity, confidence, reason |
| Flag a wrongly-blocked domain for review |
| Your plan + today's AI-check usage |
Related MCP server: Verdict
Setup
Get a pleamo API key (a revocable key from the dashboard at
https://dash.pleamo.app/keys).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 |
| — | Required. Bearer token for the pleamo API. |
|
| Override for local dev (e.g. |
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.jsRemote (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/mcpIt 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 asPLEAMO_TOKEN. (A raw session token also works, but keys are the right, revocable option.)Transport — this package is stdio; the hosted
/api/mcpabove 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 toolscheck_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
Scored across 3 tools
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.
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.
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.
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
Related MCP Connectors
PhishTank MCP — wraps PhishTank API (checkurl.phishtank.com)
Scam and phishing detection for AI agents: safe/warn/danger verdicts for URLs and messages.
URLhaus MCP — wraps abuse.ch URLhaus malware URL database (free, no auth)
URL risk evidence with scoped OAuth/API keys, capped prepaid costs and up to ten URLs per batch.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables checking suspicious URLs for risk without opening them, providing full checkups and lookalike detection.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to scan a URL, receive Markdown or JSON launch-page grades, retrieve ranked fixes, and inspect the full weighted checklist.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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