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.

Oxaide — Singapore company research for AI agents

REMOTE · OXAIDE.COM · SCANNED OCT 7

Agent-buys cited Singapore company research: ACRA/URA/GeBIZ packs, S$49/390/1500 per job.

Available components

+4 this week 78 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 Security74
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 783 tokens (~97/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 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 Oxaide — Singapore company research for AI agents MCP server?

Oxaide — Singapore company research for AI agents is a hosted endpoint at https://oxaide.com/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 · oxaide.com

# add to Claude Code
claude mcp add --transport http leewenjie-oxaide 'https://oxaide.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "leewenjie-oxaide": {
      "url": "https://oxaide.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "leewenjie-oxaide": {
      "type": "http",
      "url": "https://oxaide.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.leewenjie-oxaide]
url = "https://oxaide.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "leewenjie-oxaide": {
      "type": "remote",
      "url": "https://oxaide.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add leewenjie-oxaide --url 'https://oxaide.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  leewenjie-oxaide:
    url: "https://oxaide.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "leewenjie-oxaide": {
      "Transport": "http",
      "Url": "https://oxaide.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add leewenjie-oxaide -t streamable-http -u 'https://oxaide.com/mcp'
// mcp.json
{
  "mcpServers": {
    "leewenjie-oxaide": {
      "type": "http",
      "url": "https://oxaide.com/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.

  • 7 Oct 26 +1

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

  • 6 Oct 26 +1
    • Schema quality: 549 → 783 ▼ functional
  • 3 Oct 26 +1

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

  • 1 Oct 26 +1
    • Tool “ping_check” rewrote its description, which is the text the model reads security
    • “create_audit” reworded the description of “email” cosmetic
    • “ping_check” reworded the description of “email” cosmetic
  • 29 Sept 26 +1

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

  • 28 Sept 26 +4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

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

  • 26 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
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 7 Oct 2026 · Probed https://oxaide.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=oxaide.com CN=WE1,O=Google Trust Services,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA256 9dc729a8f38847670e2ce12f58ad02f8
SANs: oxaide.com, www.oxaide.com, *.www.oxaide.com
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 oxaide.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
oxaide.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://oxaide.com/mcp Verified 200
http (plaintext) http://oxaide.com/mcp HTTPS enforced 301 https://oxaide.com/mcp
MCP tools · 8 exposed · ~783 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
create_audit ~139

Create a private research job (Oxaide). Returns a job id immediately; the AI quote (S$49 Quick check / S$390 Pack / S$1500 Board pack) is emailed within ~15m. Pay with pay_audit before any work starts.

NameTypeReqDescription
briefstringyesThe research question, in plain language (SG corporate/wealth topics: ACRA/URA/GeBIZ/CPF/REIT etc).
emailstringyesDelivery email. Quote, files, and refunds go here. Required: delivery is email-first.
sourcestring–Optional caller tag, default "mcp".

No output schema declared.

No examples provided.

get_audit ~50

Get one job: status, quoted tier/price, payment state, delivery state. Poll after create_audit.

NameTypeReqDescription
idstringyesJob id returned by create_audit (brief_xxx).

No output schema declared.

No examples provided.

get_audit_result ~40

Get the delivered answer/pack for a job (markdown summary; files arrive by email + status page).

NameTypeReqDescription
idstringyesJob id.

No output schema declared.

No examples provided.

list_audits ~67

Admin only: list recent jobs. Requires admin_token matching the server MCP_ADMIN_TOKEN (disabled when unset). Never open to the public.

NameTypeReqDescription
admin_tokenstring–Admin token (MCP_ADMIN_TOKEN).
limitnumber–1-50, default 10.

No output schema declared.

No examples provided.

lookup_ownership ~86

Free instant lookup: registered name, status, entity type, and registration date for a UEN from the monthly register snapshot. Officers and shareholders are NOT in the free snapshot — for the ownership chain, open a cited screen with create_audit ("Ownership of <name> (<uen>)").

NameTypeReqDescription
uenstringyesUEN, e.g. 201806463W.

No output schema declared.

No examples provided.

pay_audit ~114

Pay a quoted job. method=stripe returns a Stripe Checkout URL (cards + PayNow). method=x402 (default) returns x402 v2 payment requirements (USDC on Base); pay, then call again with the PAYMENT-SIGNATURE header or _meta["x402/payment"] to settle. Work starts only after payment is verified AND settled.

NameTypeReqDescription
idstringyesQuoted job id.
methodstring–stripe = hosted checkout; x402 = agentic USDC on Base (default).

No output schema declared.

No examples provided.

ping_check ~139

Run one prepaid registry ping (Quick check, ~5 min, result by email + status page). Needs a pack_id from a ping-pack purchase (100 pings S$150, 90d). The delivery email must match the purchase email (+tags ok). No pack? POST /api/brief/ping-pack first (see https://oxaide.com/pricing#pings).

NameTypeReqDescription
emailstringyesDelivery email. Result goes here.
pack_idstringyesPing-pack id from the purchase email (pp_xxx). Possession authorizes the redeem.
targetstringyesUEN or entity name to check.

No output schema declared.

No examples provided.

subscribe_watch ~148

Start a prepaid 12-month Watchtower watch: UEN S$490, business-name S$290, IPOS-filing S$790, supplier S$990, portfolio S$2490, grant-call S$490, award-intel S$990. Returns a Stripe checkout URL (cards + PayNow); the watch activates on payment. Needs the target + delivery email.

NameTypeReqDescription
emailstringyesDelivery email. Alerts + digest go here.
planstringyesWatch plan: uen, trademark, ipos-watch, supplier, portfolio, grant-call, award-intel.
targetstringyesWatch target: UEN, entity name, or mark.

No output schema declared.

No examples provided.

Common questions

What is the Oxaide — Singapore company research for AI agents MCP server?

Oxaide — Singapore company research for AI agents is an MCP server listed in the public MCP registry as io.github.leewenjie/oxaide. Agent-buys cited Singapore company research: ACRA/URA/GeBIZ packs, S$49/390/1500 per job. This page covers its hosted endpoint (https://oxaide.com/mcp).

Is the Oxaide — Singapore company research for AI agents MCP server safe to use?

Oxaide — Singapore company research for AI agents scores 78 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 Oxaide — Singapore company research for AI agents MCP server expose?

Oxaide — Singapore company research for AI agents exposes 8 tools: create_audit, ping_check, get_audit, pay_audit, get_audit_result, and 3 more. Their descriptions and schemas cost roughly 783 tokens of context every time the server is loaded.

Does the Oxaide — Singapore company research for AI agents MCP server require authentication?

No. We connected to Oxaide — Singapore company research for AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Oxaide — Singapore company research for AI agents MCP server still maintained?

Oxaide — Singapore company research for AI agents is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.