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.

Omega x402 Security, Biomed & Escrow Intelligence MCP

REMOTE · AGY-X402-GATEWAY.OMEGA-X402-EDGE.WORKERS.DEV

7 x402 v2 pay-per-call MCP tools for FDA/ChEMBL, token rug scan, Base escrow & wallet forensics.

+3 this week 64 Trust /100

Last scanned (13 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 Security46
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 862 tokens (~123/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 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
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 13 Nov 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.

  • 11 Nov 26 +1

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

  • 9 Nov 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.

  • 7 Nov 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.

  • 6 Nov 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
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 21 Nov 2026 · Probed https://agy-x402-gateway.omega-x402-edge.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=omega-x402-edge.workers.dev CN=YE1,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA384 6c9a4b74ada72168de3fd4694a6bac5efa2
SANs: *.omega-x402-edge.workers.dev, omega-x402-edge.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agy-x402-gateway.omega-x402-edge.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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://agy-x402-gateway.omega-x402-edge.workers.dev/mcp Verified 200
http (plaintext) http://agy-x402-gateway.omega-x402-edge.workers.dev/mcp Served over HTTP 200
MCP tools · 7 exposed · ~862 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
base_escrow_audit ~123

Live Base Mainnet RPC contract & escrow solvency check: bytecode size, Circle USDC balance, EIP-1967/1167 proxy detection, pause/blacklist selector scan, numeric risk score (0-100), and safe/caution/avoid verdict. (Paid x402 endpoint: $0.02 USDC at GET https://agy-x402-gateway.omega-x402-edge.workers.dev/api/v1/base-escrow-audit)

NameTypeReqDescription
addressstring–Base Mainnet 0x contract or wallet address

No output schema declared.

No examples provided.

biomed_intel ~139

Live biomedical compound intelligence combining openFDA FAERS adverse-event counts & label warnings, ClinicalTrials.gov API v2 trial pipelines, and ChEMBL molecule properties in one structured JSON call. (Paid x402 endpoint: $0.03 USDC at GET https://agy-x402-gateway.omega-x402-edge.workers.dev/api/v1/biomed-intel)

NameTypeReqDescription
conditionstring–Optional condition filter (e.g. obesity)
drugstring–Drug or compound generic/brand name (e.g. semaglutide)
limitstring–Max results (1-10, default 5)

No output schema declared.

No examples provided.

bounty_feed ~96

Live on-chain Base escrow vault solvency telemetry (TaskMarket Diamond, Synmerco Escrow) fused with live open GitHub USDC/crypto bounty discovery. (Paid x402 endpoint: $0.03 USDC at GET https://agy-x402-gateway.omega-x402-edge.workers.dev/api/v1/bounty-feed)

NameTypeReqDescription
limitstring–Max items to return (1-25, default 10)

No output schema declared.

No examples provided.

token_rug_scan ~143

Live on-chain token rug-pull scanner for Base (EVM mint/pause/blacklist/fee-trap & proxy inspection) and Solana SPL/Token-2022 (mintAuthority, freezeAuthority, top-5 whale concentration) fused with DexScreener LP & FDV metrics. (Paid x402 endpoint: $0.02 USDC at GET https://agy-x402-gateway.omega-x402-edge.workers.dev/api/v1/token-rug-scan)

NameTypeReqDescription
addressstring–Base 0x... or Solana Base58 mint address
chainstring–Optional chain override: base or solana

No output schema declared.

No examples provided.

wallet_forensics ~116

One-call multi-chain wallet & counterparty forensics across Base, Ethereum, Arbitrum, Polygon, and Solana: native + USDC balances, transaction nonce activity, contract vs EOA detection, and burner/Sybil risk scoring. (Paid x402 endpoint: $0.01 USDC at GET https://agy-x402-gateway.omega-x402-edge.workers.dev/api/v1/wallet-forensics)

NameTypeReqDescription
addressstring–EVM 0x... address or Solana Base58 wallet address

No output schema declared.

No examples provided.

web_extract_intel ~138

Fetches any public HTTPS webpage into clean LLM-ready Markdown + OpenGraph metadata while simultaneously auditing live Cloudflare DoH DNS (A, MX, SPF, DMARC) records to score domain authenticity and phishing risk. (Paid x402 endpoint: $0.01 USDC at GET https://agy-x402-gateway.omega-x402-edge.workers.dev/api/v1/web-extract-intel)

NameTypeReqDescription
max_charsstring–Max Markdown characters to return (500-15000, default 6000)
urlstring–Public HTTPS URL to extract and inspect (e.g. https://x402.org)

No output schema declared.

No examples provided.

x402_lint ~107

Probes any x402 HTTP 402 endpoint to verify PAYMENT-REQUIRED header size, v1/v2 accepts[] schema, Base/Solana asset & payTo validity, facilitator reachability, and Bazaar outputSchema readiness. (Paid x402 endpoint: $0.01 USDC at GET https://agy-x402-gateway.omega-x402-edge.workers.dev/api/v1/x402-lint)

NameTypeReqDescription
urlstring–Target HTTPS x402 endpoint URL to inspect

No output schema declared.

No examples provided.

Install

How do I install the Omega x402 Security, Biomed & Escrow Intelligence MCP server?

Omega x402 Security, Biomed & Escrow Intelligence MCP is a hosted endpoint at https://agy-x402-gateway.omega-x402-edge.workers.dev/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 · agy-x402-gateway.omega-x402-edge.workers.dev

# add to Claude Code
claude mcp add --transport http chusmias258-dev-omega-x402-mcp 'https://agy-x402-gateway.omega-x402-edge.workers.dev/mcp'
Common questions

What is the Omega x402 Security, Biomed & Escrow Intelligence MCP server?

Omega x402 Security, Biomed & Escrow Intelligence MCP is listed in the public MCP registry as io.github.chusmias258-dev/omega-x402-mcp. 7 x402 v2 pay-per-call MCP tools for FDA/ChEMBL, token rug scan, Base escrow & wallet forensics. This page covers its hosted endpoint (https://agy-x402-gateway.omega-x402-edge.workers.dev/mcp).

Is the Omega x402 Security, Biomed & Escrow Intelligence MCP server safe to use?

Omega x402 Security, Biomed & Escrow Intelligence MCP scores 64 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 Omega x402 Security, Biomed & Escrow Intelligence MCP server expose?

Omega x402 Security, Biomed & Escrow Intelligence MCP exposes 7 tools: biomed_intel, token_rug_scan, base_escrow_audit, bounty_feed, x402_lint, and 2 more. Their descriptions and schemas cost roughly 862 tokens of context every time the server is loaded.

Does the Omega x402 Security, Biomed & Escrow Intelligence MCP server require authentication?

No. We connected to Omega x402 Security, Biomed & Escrow Intelligence MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Omega x402 Security, Biomed & Escrow Intelligence MCP server still maintained?

Omega x402 Security, Biomed & Escrow Intelligence MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Omega x402 Security, Biomed & Escrow Intelligence MCP server?

VerifyMCP ran 12 checks on Omega x402 Security, Biomed & Escrow Intelligence MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Omega x402 Security, Biomed & Escrow Intelligence MCP: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.