accueil / serveurs / Recherche & Web / ai.nexez/commerce
ai.nexez/commerce
serveur MCP (Model Context Protocol) · nexez:platform 1.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que ai.nexez/commerce est sûr ?
Au dernier audit MCP Hub, le serveur MCP « ai.nexez/commerce » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 5 outils
- nexez_directory≈ 265 tokens
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.
Paramètres, retour & exemple (4)
Paramètresq· string · optionnel
Optional case-insensitive text filter across listing name, description, audience, and location.category· string · optionnel · all | professional | consumer
Marketplace category; defaults to all.location· string · optionnel
Optional city or region filter matched against published location and service-area information.min_readiness· number · optionnel
Minimum listing readiness score, normally 0-100; defaults to 0 (no threshold).
Exemple d'appel{"name": "nexez_directory", "arguments": {"q": "texte", "category": "all", "location": "texte", "min_readiness": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - nexez_get_page≈ 168 tokens
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.
Paramètres, retour & exemple (1)
Paramètresslug· string · requis
Exact published listing slug returned by nexez_search or nexez_directory, not a full URL.
Exemple d'appel{"name": "nexez_get_page", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - nexez_search≈ 662 tokens
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.
Paramètres, retour & exemple (14)
Paramètresq· string · requis
What the buyer is looking forlat· number · optionnel
Optional latitude context metadata. Does not filter or rerank results; use location for geographic filtering.lng· number · optionnel
Optional longitude context metadata. Does not filter or rerank results; use location for geographic filtering.limit· number · optionnel
Maximum results; defaults to 10 and is rounded down and clamped to 1-50.category· string · optionnel · all | professional | consumer
Marketplace category; omit or use all to include both professional and consumer listings.industry· string · optionnel
Case-insensitive substring filter on the published industry, for example plumbing.location· string · optionnel
Optional city/region filterverified· boolean · optionnel
Filter by seller verification signal: true requires a signal, false requires its absence; omit to include both.min_trust· integer · optionnel
Minimum marketplace trust score (0-100); omit for no trust threshold. Not a guarantee of seller performance.price_band· string · optionnel · free | under_100 | 100_500 | 500_2000 | 2000_plus | custom
Filter by the listing marketplace price band. Inspect the exact offer for its price and currency; this is not a checkout quote.min_readiness· integer · optionnel
Minimum listing readiness score (0-100); omit for no readiness threshold.supports_checkout· boolean · optionnel
Deprecated compatibility filter: any actionable offer or provider handoffnexez_checkout_ready· boolean · optionnel
Owner payout state confirms Nexez-settled checkout readinesssupports_negotiation· boolean · optionnel
Filter by negotiation availability: true for eligible listings, false for non-negotiable listings; omit to include both.
Exemple d'appel{"name": "nexez_search", "arguments": {"q": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - nexez_validate_checkout≈ 364 tokens
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.
Paramètres, retour & exemple (6)
Paramètresslug· string · requis
Exact published listing slug returned by discovery, not a full URL.offer· string · requis
Exact offer key from the listing manifest, for example services-0 or products-1. Do not invent an index.query· string · optionnel
Optional buyer contextbuyerEmail· string · optionnel
Optional buyer-provided email for checkout context. Omit when unnecessary; never invent personal details.buyerReference· string · optionnel
Optional buyer-provided reference for checkout context; omit if none was supplied.offerConfiguration· object · optionnel
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 schema.
Exemple d'appel{"name": "nexez_validate_checkout", "arguments": {"slug": "texte", "offer": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - nexez_validate_negotiation≈ 440 tokens
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.
Paramètres, retour & exemple (7)
Paramètresslug· string · requis
Exact published listing slug returned by discovery, not a full URL.offer· string · requis
Exact offer key from the listing manifest, for example services-0 or products-1.query· string · optionnel
Buyer request describing the desired work or product and relevant context.budget· string · optionnel
Buyer-proposed budget or range as text, using the offer currency, for example USD 500. Do not invent a budget.contact· string · optionnel
Optional buyer contact route.timeline· string · optionnel
Buyer-proposed delivery timing as text, for example within 4 weeks. Use requestedTerms.projectWeeks for a numeric duration rule.requestedTerms· object · optionnel
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":"Logo and brand guide","revisionCount":2,"projectWeeks":4}. Inspect the offer rules; omit unknown terms rather than inventing them.
Exemple d'appel{"name": "nexez_validate_negotiation", "arguments": {"slug": "texte", "offer": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».