Nexez Agentic Commerce
REMOTE · NEXEZ.APP · SCANNED SEP 20
Find Nexez sellers, inspect offers, and validate checkout or negotiation before buyer approval.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1159 tokens (~144/item across 8 items; 5 tools + 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 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
How do I install the Nexez Agentic Commerce MCP server?
Nexez Agentic Commerce is a hosted endpoint at https://nexez.app/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 · nexez.app
claude mcp add --transport http ai-nexez-commerce 'https://nexez.app/mcp'
{
"mcpServers": {
"ai-nexez-commerce": {
"url": "https://nexez.app/mcp"
}
}
} {
"servers": {
"ai-nexez-commerce": {
"type": "http",
"url": "https://nexez.app/mcp"
}
}
} [mcp_servers.ai-nexez-commerce] url = "https://nexez.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-nexez-commerce": {
"type": "remote",
"url": "https://nexez.app/mcp",
"enabled": true
}
}
} openclaw mcp add ai-nexez-commerce --url 'https://nexez.app/mcp' --transport streamable-http
mcp_servers:
ai-nexez-commerce:
url: "https://nexez.app/mcp" {
"McpServers": {
"ai-nexez-commerce": {
"Transport": "http",
"Url": "https://nexez.app/mcp"
}
}
} assistant mcp add ai-nexez-commerce -t streamable-http -u 'https://nexez.app/mcp'
{
"mcpServers": {
"ai-nexez-commerce": {
"type": "http",
"url": "https://nexez.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 9 Sept 26 +2
- Tool “nexez_directory” rewrote its description, which is the text the model reads security
- Tool “nexez_get_page” rewrote its description, which is the text the model reads security
- Tool “nexez_search” rewrote its description, which is the text the model reads security
- Tool “nexez_validate_checkout” rewrote its description, which is the text the model reads security
- Tool “nexez_validate_negotiation” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 34% → 100% ▲ functional
- Schema quality: fair → good functional
- “nexez_directory” reworded the description of “category” cosmetic
- “nexez_directory” reworded the description of “location” cosmetic
- “nexez_directory” reworded the description of “min_readiness” cosmetic
- “nexez_directory” reworded the description of “q” cosmetic
- “nexez_get_page” reworded the description of “slug” cosmetic
- “nexez_search” reworded the description of “category” cosmetic
- “nexez_search” reworded the description of “industry” cosmetic
- “nexez_search” reworded the description of “lat” cosmetic
- “nexez_search” reworded the description of “limit” cosmetic
- “nexez_search” reworded the description of “lng” cosmetic
- “nexez_search” reworded the description of “min_readiness” cosmetic
- “nexez_search” reworded the description of “min_trust” cosmetic
- “nexez_search” reworded the description of “price_band” cosmetic
- “nexez_search” reworded the description of “supports_negotiation” cosmetic
- “nexez_search” reworded the description of “verified” cosmetic
- “nexez_validate_checkout” reworded the description of “buyerEmail” cosmetic
- “nexez_validate_checkout” reworded the description of “buyerReference” cosmetic
- “nexez_validate_checkout” reworded the description of “offer” cosmetic
- “nexez_validate_checkout” reworded the description of “offerConfiguration” cosmetic
- “nexez_validate_checkout” reworded the description of “slug” cosmetic
- “nexez_validate_negotiation” reworded the description of “budget” cosmetic
- “nexez_validate_negotiation” reworded the description of “offer” cosmetic
- “nexez_validate_negotiation” reworded the description of “query” cosmetic
- “nexez_validate_negotiation” reworded the description of “requestedTerms” cosmetic
- “nexez_validate_negotiation” reworded the description of “slug” cosmetic
- “nexez_validate_negotiation” reworded the description of “timeline” cosmetic
- 2 Sept 26 +7
- Authorization: unverified → partial ▲ security
- Tool “nexez_directory” changed its title: Browse the Nexez directory cosmetic
- Tool “nexez_get_page” changed its title: Inspect a Nexez listing cosmetic
- Tool “nexez_search” changed its title: Search Nexez offers cosmetic
- Tool “nexez_validate_checkout” changed its title: Validate Nexez checkout cosmetic
- Tool “nexez_validate_negotiation” changed its title: Validate Nexez negotiation cosmetic
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +5
- Stability: 0.97 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 61 → 68 ▼ functional
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2024-11-05 → 2026-07-28 functional
- Server version: 1.0.0 → 1.1.0 functional
- “nexez_validate_negotiation” added an optional parameter “contact” cosmetic
- “nexez_validate_negotiation” added an optional parameter “requestedTerms” cosmetic
- 23 Aug 26 +1
- Tool “nexez_validate_checkout” rewrote its description, which is the text the model reads security
- Tool coverage: 24% → 30% ▲ functional
- Schema quality: good → fair functional
- “nexez_search” added an optional parameter “nexez_checkout_ready” cosmetic
- “nexez_search” reworded the description of “supports_checkout” cosmetic
- 21 Aug 26 0
- “nexez_validate_checkout” added an optional parameter “buyerEmail” cosmetic
- “nexez_validate_checkout” added an optional parameter “buyerReference” cosmetic
- “nexez_validate_checkout” added an optional parameter “offerConfiguration” cosmetic
3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 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
- 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
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://nexez.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nexez.app | CN=YR1,O=Let's Encrypt,C=US | 10 Aug 2026 | 8 Nov 2026 | RSA 2048 | SHA256-RSA | 53afae541ea52e4711ae21f26ded5128854 |
| SANs: nexez.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nexez.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| nexez.app. | 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=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nexez.app/mcp | Verified | 200 | |
| http (plaintext) | http://nexez.app/mcp | HTTPS enforced | 308 | https://nexez.app/mcp |
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 →
nexez_directory Browse the Nexez directory ~134
Browse published Nexez listings without requiring a buyer query. All filters are optional. Returns directory JSON text with listing summaries and readiness information. Use nexez_search when you need ranked matches for a specific buyer request.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Marketplace category; defaults to all. |
| location | string | – | Optional city or region filter matched against published location and service-area information. |
| min_readiness | number | – | Minimum listing readiness score, normally 0-100; defaults to 0 (no threshold). |
| q | string | – | Optional case-insensitive text filter across listing name, description, audience, and location. |
No output schema declared.
No examples provided.
nexez_get_page Inspect a Nexez listing ~77
Fetch one listing's structured agent manifest as JSON text, including seller profile, offers, configuration requirements, and published actions. Use a slug returned by search or directory; inspect exact offer identifiers and requirements before validation.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Exact published listing slug returned by nexez_search or nexez_directory, not a full URL. |
No output schema declared.
No examples provided.
nexez_search Search Nexez offers ~390
Find services or products for a specific buyer request. Returns JSON text with ranked results, structured offers, listing slugs, agent.json URLs, and applied filters. Use nexez_directory for broad browsing, then nexez_get_page to inspect an exact offer before a dry run.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Marketplace category; omit or use all to include both professional and consumer listings. |
| industry | string | – | Case-insensitive substring filter on the published industry, for example plumbing. |
| lat | number | – | Optional latitude context metadata. Does not filter or rerank results; use location for geographic filtering. |
| limit | number | – | Maximum results; defaults to 10 and is rounded down and clamped to 1-50. |
| lng | number | – | Optional longitude context metadata. Does not filter or rerank results; use location for geographic filtering. |
| location | string | – | Optional city/region filter |
| min_readiness | integer | – | Minimum listing readiness score (0-100); omit for no readiness threshold. |
| min_trust | integer | – | Minimum marketplace trust score (0-100); omit for no trust threshold. Not a guarantee of seller performance. |
| nexez_checkout_ready | boolean | – | Owner payout state confirms Nexez-settled checkout readiness |
| price_band | string | – | Filter by the listing marketplace price band. Inspect the exact offer for its price and currency; this is not a checkout quote. |
| q | string | yes | What the buyer is looking for |
| supports_checkout | boolean | – | Deprecated compatibility filter: any actionable offer or provider handoff |
| supports_negotiation | boolean | – | Filter by negotiation availability: true for eligible listings, false for non-negotiable listings; omit to include both. |
| verified | boolean | – | Filter by seller verification signal: true requires a signal, false requires its absence; omit to include both. |
No output schema declared.
No examples provided.
nexez_validate_checkout Validate Nexez checkout ~209
Dry-run checkout for an exact published offer. Returns validation JSON text with offer readiness or errors and missing requirements. Inspect the offer with nexez_get_page first. Never charges or creates an order; a successful check is not a completed purchase.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerEmail | string | – | Optional buyer-provided email for checkout context. Omit when unnecessary; never invent personal details. |
| buyerReference | string | – | Optional buyer-provided reference for checkout context; omit if none was supplied. |
| offer | string | yes | Exact offer key from the listing manifest, for example services-0 or products-1. Do not invent an index. |
| offerConfiguration | object | – | Buyer-selected configuration values keyed exactly as defined by the target offer configuration schema from nexez_get_page. Supply required fields for that offer; do not invent values or use a generic… |
| query | string | – | Optional buyer context |
| slug | string | yes | Exact published listing slug returned by discovery, not a full URL. |
No output schema declared.
No examples provided.
nexez_validate_negotiation Validate Nexez negotiation ~283
Evaluate proposed terms against an exact offer and the seller's published rules in a forced dry run. Returns rules-evaluation JSON text or validation errors. Inspect the offer first and supply its required terms. Never submits a proposal, contacts a seller, or writes a negotiation.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | Buyer-proposed budget or range as text, using the offer currency, for example USD 500. Do not invent a budget. |
| contact | string | – | Optional buyer contact route. |
| offer | string | yes | Exact offer key from the listing manifest, for example services-0 or products-1. |
| query | string | – | Buyer request describing the desired work or product and relevant context. |
| requestedTerms | object | – | Structured buyer proposal. Published seller rules may require scope (text or list of deliverables), revisionCount (whole number 0-1000), and projectWeeks (whole number 1-1000). Example: {"scope":"Log… |
| slug | string | yes | Exact published listing slug returned by discovery, not a full URL. |
| timeline | string | – | Buyer-proposed delivery timing as text, for example within 4 weeks. Use requestedTerms.projectWeeks for a numeric duration rule. |
No output schema declared.
No examples provided.
What is the Nexez Agentic Commerce MCP server?
Nexez Agentic Commerce is an MCP server listed in the public MCP registry as ai.nexez/commerce. Find Nexez sellers, inspect offers, and validate checkout or negotiation before buyer approval. This page covers its hosted endpoint (https://nexez.app/mcp).
Is the Nexez Agentic Commerce MCP server safe to use?
Nexez Agentic Commerce scores 88 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 Nexez Agentic Commerce MCP server expose?
Nexez Agentic Commerce exposes 5 tools: nexez_search, nexez_directory, nexez_get_page, nexez_validate_checkout, nexez_validate_negotiation. Their descriptions and schemas cost roughly 1,093 tokens of context every time the server is loaded.
Does the Nexez Agentic Commerce MCP server require authentication?
No. We connected to Nexez Agentic Commerce without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nexez Agentic Commerce MCP server still maintained?
Nexez Agentic Commerce 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.