Skip to main content
Glama
BACH-AI-Tools

Malicious Scanner MCP Server

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Malicious Scanner MCP Server

English | 简体中文 | 繁體中文

用于访问 Malicious Scanner API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-malicious_scanner）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: unphurl-mcp

简介

这是一个 MCP 服务器，用于访问 Malicious Scanner API。

  • PyPI 包名: bach-malicious_scanner

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-malicious_scanner

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-malicious_scanner bach_malicious_scanner

# 或指定版本
uvx --from bach-malicious_scanner@latest bach_malicious_scanner

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-malicious_scanner

# 运行（命令名使用下划线）
bach_malicious_scanner

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-malicious_scanner": {
      "command": "uvx",
      "args": ["--from", "bach-malicious_scanner", "bach_malicious_scanner"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-malicious_scanner": {
      "command": "uvx",
      "args": ["--from", "bach-malicious_scanner", "bach_malicious_scanner"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

scan_url

Real time, Fully Scan one URL for any malicious content, including Spam/Gray classification and additional flags like domain age, and more

端点: GET /rapid/url

参数:

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

1 tool
scan_urlC

Real time, Fully Scan one URL for any malicious content, including Spam/Gray classification and additional flags like domain age, and more

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesExample value: https://vryjm.page.link/jS6a

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'real time' (implying speed) and 'fully scan' (suggesting comprehensiveness), but lacks details on permissions, rate limits, error handling, or what 'malicious content' entails. This leaves significant gaps in understanding the tool's behavior.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads key actions ('scan', 'classify') and details. It avoids redundancy but could be slightly more structured by separating core functionality from additional features for clarity.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It lacks information on return values (e.g., scan results format), error cases, or operational constraints like rate limits. For a security scanning tool, this omission is significant and reduces usability.

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

Parameters3/5

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

The input schema has 100% description coverage, with the 'url' parameter documented in the schema. The description adds no additional parameter semantics beyond implying the URL is scanned for threats, which the schema's example already suggests. This meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the tool's purpose: scanning a URL for malicious content with specific categories (Spam/Gray classification) and additional flags (domain age). It uses specific verbs ('scan', 'classify') and identifies the resource (URL), but lacks sibling tools for differentiation, preventing a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It mentions 'real time' and 'fully scan' but does not specify scenarios where this tool is appropriate or inappropriate, leaving usage decisions unclear.

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.0.0
    • First observedscan_url
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'scan_url' has a clearly defined and distinct purpose, making it impossible for an agent to misselect between multiple options.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'scan_url' follows a clear verb_noun pattern, and there are no other tools to compare it against, so no inconsistencies can arise.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. For a malicious scanner, one tool might suffice for basic scanning, but it lacks coverage for related operations like batch scanning, result management, or configuration adjustments.

Completeness2/5

The tool surface is severely incomplete for a malicious scanner domain. While 'scan_url' covers the core scanning function, there are obvious gaps such as scanning multiple URLs, retrieving scan history, managing whitelists/blacklists, or configuring scan parameters, which could lead to agent failures in more complex tasks.

Maintenance

ActivityInactive
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

  • Malicious URLs MCP Server

    BACH-AI-Tools
    A
    license
    C
    quality
    D
    maintenance
    Provides access to a malicious URL database API, enabling users to search, list, and retrieve information about potentially dangerous URLs for security analysis and threat detection.
    3
    MIT

  • unphurl-mcp

    123Ergo
    A
    license
    A
    quality
    D
    maintenance
    URL intelligence for AI agents. One URL in, structured security and data quality signals out across 7 dimensions. 13 tools, risk score 0-100 with 23 configurable weights.
    16
    110
    1
    MIT

  • web-doctor

    Baneado98
    A
    license
    A
    quality
    B
    maintenance
    Enables live website health checks including TLS, HTTPS, and security headers, returning an A-F grade with specific fixes.
    2
    MIT

  • mcp-phishtank

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables checking URLs against the PhishTank phishing database to identify malicious sites.
    15
    MIT

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/BACH-AI-Tools/bachai-malicious-scanner'

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