Security & Testing

malwareintel.es

MCP server for MalwareIntel that provides blog search, site metadata, and navigation for malware analysis, threat hunting, DFIR, and CTI content.

WebMCP1 endpoint3 known toolsFirst detected October 11, 2026Last detected October 11, 2026

ENDPOINT 1

https://malwareintel.es

No auth detected

Capabilities

imperative

Search MalwareIntel blog articles about malware analysis, threat hunting, DFIR, and CTI

Inferred read-only

Returns MalwareIntel site metadata and navigation

Inferred read-only

Navigate to a section of MalwareIntel

Inferred read-only

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.webmcp]
url = "https://malwareintel.es"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://malwareintel.es"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://malwareintel.es

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "webmcp": {
      "url": "https://malwareintel.es"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://malwareintel.es"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://malwareintel.es"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

BuiltWith Trust API v2 evidence for malwareintel.es was fetched 2026-10-17T04:39:22.386Z.

Trust status Trusted

malwareintel.es is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.