Skip to main content
Glama
stanfrbd

Cyberbro MCP Server

by stanfrbd

get_engines

Retrieve the list of available Cyberbro engines. Use this to see which engines are usable for IoC reputation checks.

Instructions

List available Cyberbro engines. This is the first tool to be called to get the usable engines. Returns: The list of engines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The get_engines async function that executes the tool logic. It returns a dict with the ENGINES list, providing all available Cyberbro engines and their supported observable types.
    async def get_engines() -> Any:
        """
        List available Cyberbro engines.
        This is the first tool to be called to get the usable engines.
        Returns:
            The list of engines.
        """
        return {"engines": ENGINES}
  • The ENGINES constant defining all available engines with their names, supported observable types, and descriptions. This is the data returned by the get_engines tool.
    ENGINES = [
        {
            "name": "misp_feedback",
            "supports": ["IP", "domain", "hash"],
            "description": "Checks MISP-Feedback warninglists for IP, domain, and hashes to identify false positives. API key optional, self-hosted server URL required.",
        },
        {
            "name": "ransomware_live",
            "supports": ["domain", "URL"],
            "description": "Checks the Ransomware.Live Pro API to determine whether a domain has appeared as a ransomware victim on a data leak site (DLS). Free API key required.",
        },
        {
            "name": "reverse_dns",
            "supports": ["domain", "IP", "abuse"],
            "description": "Performs a reverse DNS lookup (local DNS) for IP, domain, URL (on the Cyberbro machine)",
        },
        {
            "name": "dfir_iris",
            "supports": ["domain", "URL", "IP", "hash"],
            "description": "Searches DFIR-IRIS globally across all cases for indicators, free, API key required.",
        },
        {
            "name": "rdap",
            "supports": ["abuse", "domain"],
            "description": "Checks RDAP (ex Whois) record for domain, URL",
        },
        {
            "name": "ipquery",
            "supports": ["IP", "risk", "VPN", "proxy", "geoloc"],
            "description": "Checks IPquery for IP, reversed obtained IP for a given domain/URL",
        },
        {
            "name": "abuseipdb",
            "supports": ["risk", "IP"],
            "description": "Checks AbuseIPDB for IP, reversed obtained IP for a given domain/URL",
        },
        {
            "name": "ipapi",
            "supports": ["IP", "risk", "geoloc", "VPN", "proxy"],
            "description": "Checks IPAPI for IP, reversed obtained IP for a given domain/URL",
        },
        {
            "name": "ipinfo",
            "supports": ["IP", "geoloc"],
            "description": "Checks IPinfo for IP, reversed obtained IP for a given domain/URL",
        },
        {
            "name": "virustotal",
            "supports": ["hash", "risk", "IP", "domain", "URL"],
            "description": "Checks VirusTotal for IP, domain, URL, hash",
        },
        {
            "name": "spur",
            "supports": ["VPN", "proxy", "IP"],
            "description": "Checks Spur.us for IP, reversed obtained IP for a given domain/URL",
        },
        {
            "name": "mde",
            "supports": ["hash", "IP", "domain", "URL"],
            "description": "Checks Microsoft Defender for Endpoint EDR API for IP, domain, URL, hash",
        },
        {
            "name": "crowdstrike",
            "supports": ["hash", "IP", "domain", "URL"],
            "description": "Checks CrowdStrike EDR for IP, domain, URL, hash using Falcon API",
        },
        {
            "name": "google_safe_browsing",
            "supports": ["risk", "domain", "IP", "URL"],
            "description": "Checks Google Safe Browsing for IP, domain, URL",
        },
        {
            "name": "shodan",
            "supports": ["ports", "IP"],
            "description": "Checks Shodan, reversed obtained IP for a given domain/URL",
        },
        {
            "name": "phishtank",
            "supports": ["risk", "domain", "URL"],
            "description": "Checks Phishtank for domains, URL",
        },
        {
            "name": "threatfox",
            "supports": ["IP", "domain", "URL"],
            "description": "Checks ThreatFox by Abuse.ch for IP, domains, URL",
        },
        {
            "name": "urlscan",
            "supports": ["domain", "URL", "IP", "hash"],
            "description": "Checks URLscan for all types of observable",
        },
        {
            "name": "google",
            "supports": ["domain", "URL", "IP", "hash", "chrome_extension_id", "edge_extension_id"],
            "description": "Checks Google search results for all types of observable",
        },
        {
            "name": "github",
            "supports": ["domain", "URL", "IP", "hash", "chrome_extension_id", "edge_extension_id"],
            "description": "Get Github grep.app API search results for all types of observable",
        },
        {
            "name": "ioc_one_html",
            "supports": ["domain", "URL", "IP", "hash", "chrome_extension_id", "edge_extension_id"],
            "description": "Scraps (can be long) Ioc.One HTML search results for all types of observable",
        },
        {
            "name": "ioc_one_pdf",
            "supports": ["domain", "URL", "IP", "hash", "chrome_extension_id", "edge_extension_id"],
            "description": "Scraps (can be long) Ioc.One PDF search results for all types of observable",
        },
        {
            "name": "opencti",
            "supports": ["domain", "URL", "IP", "hash"],
            "description": "Searches OpenCTI results for all types of observable",
        },
        {
            "name": "abusix",
            "supports": ["abuse", "IP"],
            "description": "Checks abuse contact with Abusix for IP, reversed obtained IP for a given domain/URL",
        },
        {
            "name": "hudsonrock",
            "supports": ["domain", "URL", "email", "infostealers", "malware"],
            "description": "Searches Hudson Rock results for domains, URL, Email",
        },
        {
            "name": "webscout",
            "supports": ["IP", "risk", "geoloc", "VPN", "proxy"],
            "description": "Checks WebScout for IP, reversed obtained IP for a given domain / URL",
        },
        {
            "name": "criminalip",
            "supports": ["IP", "risk", "VPN", "proxy"],
            "description": "Checks CriminalIP for IP, reversed obtained IP for a given domain / URL",
        },
        {
            "name": "alienvault",
            "supports": ["IP", "domain", "URL", "hash", "risk"],
            "description": "Checks Alienvault for IP, domain, URL, hash",
        },
        {
            "name": "misp",
            "supports": ["IP", "domain", "URL", "hash"],
            "description": "Checks MISP for IP, domain, URL, hash",
        },
        {
            "name": "google_dns",
            "supports": ["IP", "domain", "URL"],
            "description": "Checks Google common DNS records (A, AAAA, CNAME, NS, MX, TXT, PTR) for IP, domain, URL",
        },
        {
            "name": "crtsh",
            "supports": ["domain", "URL"],
            "description": "Checks crt.sh for domain, URL",
        },
        {
            "name": "rl_analyze",
            "supports": ["domain", "URL", "IP", "hash"],
            "description": "Looks up observables in the Reversing Labs Spectra Analyze service",
        },
        {
            "name": "bad_asn",
            "supports": ["IP", "risk"],
            "description": "Malicious ASN detection (free). Checks if IP's ASN is listed in Spamhaus ASNDROP or Brianhama Bad ASN databases. Requires ipapi, ipinfo to be selected to get the ASN. Free, no API key",
        },
        {
            "name": "rosti",
            "supports": ["domain", "URL", "IP", "email", "hash", "risk"],
            "description": "IOC search and enrichment. Searches Rosti IOC data for domains, URLs, IPs, emails, and hashes (MD5, SHA1, SHA256), API key required",
        },
    ]
  • The register_engine_tools function that registers get_engines as an MCP tool via the @mcp.tool() decorator.
    def register_engine_tools(mcp: FastMCP) -> None:
        @mcp.tool()
        async def get_engines() -> Any:
            """
            List available Cyberbro engines.
            This is the first tool to be called to get the usable engines.
            Returns:
                The list of engines.
            """
            return {"engines": ENGINES}
  • Where register_engine_tools is called during server creation in create_server(), passing the mcp instance to register the tool.
    register_analysis_tools(mcp, config)
    register_engine_tools(mcp)
    register_web_tools(mcp, config)
Behavior2/5

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

With no annotations, the description carries the full burden. It only states that the tool lists engines, lacking details on side effects, caching, or any constraints. The return info is minimal.

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

Conciseness3/5

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

The description is short but contains redundancy (the returns line repeats the purpose). It could be more concise by merging the last sentence.

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

Completeness4/5

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

Given zero parameters and no output schema, the description adequately covers the tool's purpose and usage order. It is sufficient for such a simple tool.

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?

Input schema has no parameters (0 params), so description compensation is unnecessary. Baseline for zero parameters is 4, and no additional param info is needed.

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 lists available Cyberbro engines and positions it as the first tool to call. It distinguishes from siblings like analyze_observable, but does not explicitly contrast them.

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

Usage Guidelines3/5

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

The description provides a clear usage hint (call this first), but does not specify when not to use it or offer alternatives. Usage context is implied rather than explicit.

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

Install Server

Other Tools

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/stanfrbd/mcp-cyberbro'

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