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.

xOmniMarket

REMOTE · XOMNIMARKET.COM · SCANNED SEP 20

Search AI capabilities across AWS Marketplace and the Official MCP Registry.

Available components

+3 this week 70 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 Security46
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 280 tokens (~40/item across 7 items; 7 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the xOmniMarket MCP server?

xOmniMarket is a hosted endpoint at https://xomnimarket.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 · xomnimarket.com

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

  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 8 Sept 26 +1

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

  • 5 Sept 26 +1

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

  • 3 Sept 26 0
    • Schema quality: 34 → 40 functional
    • Server version: 0.1.1 → 0.2.0 functional
    • New tool “build_decision_report” functional
    • New tool “compare_market_items” functional
    • New tool “find_alternatives” functional
    • New tool “get_market_item” functional
    • New tool “market_category_summary” 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 20 Sept 2026 · Probed https://xomnimarket.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=xomnimarket.com CN=WE1,O=Google Trust Services,C=US 4 Jul 2026 2 Oct 2026 ECDSA 256 ECDSA-SHA256 f193868af0aba0000e536a1ee31b344c
SANs: xomnimarket.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 xomnimarket.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
xomnimarket.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://xomnimarket.com/mcp Verified 200
http (plaintext) http://xomnimarket.com/mcp Inconclusive 405
MCP tools · 7 exposed · ~280 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
build_decision_report ~37

Build a source-backed decision report for one to eight catalog items, including market presence and evidence gaps.

NameTypeReqDescription
idsarrayyes

No output schema declared.

No examples provided.

compare_market_items ~35

Compare two to eight rich xOmniMarket records without inventing cross-source score equivalence.

NameTypeReqDescription
idsarrayyes

No output schema declared.

No examples provided.

find_alternatives ~46

Find evidence-backed similarity alternatives to a rich catalog item. Similarity does not imply product identity or interchangeability.

NameTypeReqDescription
idstringyes
limitinteger

No output schema declared.

No examples provided.

get_market_item ~39

Return the rich source-backed xOmniMarket record for one market entity id, including confirmed AWS/MCP presence.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

market_category_summary ~55

Summarize the current bounded xOmniMarket search results for a category or capability query. This is a search-result summary, not an exhaustive market census.

NameTypeReqDescription
sourcestring
textstringyes

No output schema declared.

No examples provided.

market_status ~19

Return xOmniMarket source population and freshness status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_market ~49

Search qualifying AI capabilities across AWS Marketplace and the Official MCP Registry. Returns both sources by default.

NameTypeReqDescription
perSourceinteger
sourcestring
textstringyes

No output schema declared.

No examples provided.

Common questions

What is the xOmniMarket MCP server?

xOmniMarket is an MCP server listed in the public MCP registry as io.github.wjabrac/xomni-market. Search AI capabilities across AWS Marketplace and the Official MCP Registry. This page covers its hosted endpoint (https://xomnimarket.com/mcp).

Is the xOmniMarket MCP server safe to use?

xOmniMarket scores 70 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 xOmniMarket MCP server expose?

xOmniMarket exposes 7 tools: search_market, market_status, get_market_item, compare_market_items, find_alternatives, and 2 more. Their descriptions and schemas cost roughly 280 tokens of context every time the server is loaded.

Does the xOmniMarket MCP server require authentication?

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

Is the xOmniMarket MCP server still maintained?

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