Security & Testing

aevumsecurity.com.sg

Provides access to Aevum Security's cybersecurity services, including service details and enquiry submission.

1 endpoint3 known toolsFirst detected July 31, 2026Last detected August 31, 2026

ENDPOINT 1

https://agents.aevumsecurity.com.sg/mcp

No auth detected

Capabilities

tools

Aevum Security's cybersecurity services: slug, name and a one-line summary.

Inferred read-only

Full details of one Aevum Security service, by slug from list_services.

Inferred read-only

Submits a business enquiry to Aevum Security on behalf of the caller's principal.

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.b2a-aevum]
url = "https://agents.aevumsecurity.com.sg/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "b2a-aevum": {
      "type": "http",
      "url": "https://agents.aevumsecurity.com.sg/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: b2a-aevum
Remote MCP URL: https://agents.aevumsecurity.com.sg/mcp

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": {
    "b2a-aevum": {
      "url": "https://agents.aevumsecurity.com.sg/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "b2a-aevum": {
      "type": "http",
      "url": "https://agents.aevumsecurity.com.sg/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "b2a-aevum",
  "transport": "streamable-http",
  "url": "https://agents.aevumsecurity.com.sg/mcp"
}

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 aevumsecurity.com.sg was fetched 2026-08-01T08:12:29.662Z and is being refreshed.

Trust status Neutral

aevumsecurity.com.sg is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

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