Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Aevum Security

REMOTE · AGENTS.AEVUMSECURITY.COM.SG · SCANNED SEP 24

Browse Aevum Security's Singapore cybersecurity services and submit a business enquiry.

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 198 tokens (~66/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Aevum Security MCP server?

Aevum Security is a hosted endpoint at https://agents.aevumsecurity.com.sg/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agents.aevumsecurity.com.sg

# add to Claude Code
claude mcp add --transport http sg-com-aevumsecurity-agent-surface 'https://agents.aevumsecurity.com.sg/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "sg-com-aevumsecurity-agent-surface": {
      "url": "https://agents.aevumsecurity.com.sg/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sg-com-aevumsecurity-agent-surface": {
      "type": "http",
      "url": "https://agents.aevumsecurity.com.sg/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.sg-com-aevumsecurity-agent-surface]
url = "https://agents.aevumsecurity.com.sg/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sg-com-aevumsecurity-agent-surface": {
      "type": "remote",
      "url": "https://agents.aevumsecurity.com.sg/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sg-com-aevumsecurity-agent-surface --url 'https://agents.aevumsecurity.com.sg/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  sg-com-aevumsecurity-agent-surface:
    url: "https://agents.aevumsecurity.com.sg/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sg-com-aevumsecurity-agent-surface": {
      "Transport": "http",
      "Url": "https://agents.aevumsecurity.com.sg/mcp"
    }
  }
}
# add to Vellum
assistant mcp add sg-com-aevumsecurity-agent-surface -t streamable-http -u 'https://agents.aevumsecurity.com.sg/mcp'
// mcp.json
{
  "mcpServers": {
    "sg-com-aevumsecurity-agent-surface": {
      "type": "http",
      "url": "https://agents.aevumsecurity.com.sg/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 29 Aug 26 0
    • Stability: 0.97 → pass security
  • 28 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 78
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Aug 26 0
    • Tool “list_services” rewrote its description, which is the text the model reads security
    • Tool “submit_enquiry” rewrote its description, which is the text the model reads security
    • Server version: 20260801T132622Z-6edf1e1d → 20260802T143212Z-f343cd12 functional
  • 2 Aug 26 0
    • Server version: 20260730T013936Z-9562c5db → 20260801T132622Z-6edf1e1d functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Probed https://agents.aevumsecurity.com.sg/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aevumsecurity.com.sg CN=WE1,O=Google Trust Services,C=US 10 Sept 2026 9 Dec 2026 ECDSA 256 ECDSA-SHA256 963498eef14da7370ebe79a49b1772a8
SANs: aevumsecurity.com.sg, agents.aevumsecurity.com.sg, *.agents.aevumsecurity.com.sg
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agents.aevumsecurity.com.sg. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
sg. present 26329 8 Verified
com.sg. present 61916 8 Verified
aevumsecurity.com.sg. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
content-security-policy default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agents.aevumsecurity.com.sg/mcp Verified 200
http (plaintext) http://agents.aevumsecurity.com.sg/mcp HTTPS enforced 301 https://agents.aevumsecurity.com.sg/mcp
MCP tools · 3 exposed · ~198 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_service_details ~32

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

NameTypeReqDescription
servicestringyes

No output schema declared.

No examples provided.

list_services ~41

Aevum Security's cybersecurity services: slug, name and a one-line summary. The slug is the service identifier accepted by get_service_details and submit_enquiry.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_enquiry ~125

Submits a business enquiry to Aevum Security on behalf of the caller's principal. Creates a real enquiry that a person reads and replies to within 1 business day; it cannot be withdrawn once submitted. Returns the enquiry id as proof of receipt. [MUTATING: requires an agent key passed as Authorization: Bearer on the HTTP connection]

NameTypeReqDescription
emailstringyesReply-to email address
messagestringyesThe enquiry itself
namestringyesContact person's name
serviceyesService slug from list_services, or 'general'

No output schema declared.

No examples provided.

Common questions

What is the Aevum Security MCP server?

Aevum Security is an MCP server listed in the public MCP registry as sg.com.aevumsecurity/agent-surface. Browse Aevum Security's Singapore cybersecurity services and submit a business enquiry. This page covers its hosted endpoint (https://agents.aevumsecurity.com.sg/mcp).

Is the Aevum Security MCP server safe to use?

Aevum Security scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Aevum Security MCP server expose?

Aevum Security exposes 3 tools: list_services, get_service_details, submit_enquiry. Their descriptions and schemas cost roughly 198 tokens of context every time the server is loaded.

Does the Aevum Security MCP server require authentication?

No. We connected to Aevum Security without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Aevum Security MCP server still maintained?

Aevum Security is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.