Servidor MCP de Zinvyl

• Nombre en el registrocom.zinvyl/marketplaceverificado en el registro MCP

El nombre en el registro está bajo zinvyl.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-25
• Herramientas14
• El servidor se llamazinvyl-marketplace-agent-gateway
• Versión del servidor1.7.1
• Versión del protocolo2025-06-18

El 2026-10-25 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 68 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 1 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 1 hasta ahora
• Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta736 ms
• Espacio en el contexto del agente≈ 8531 tokenslas definiciones de todas sus herramientas (14), que el agente lleva en cada turno
• Definiciones de herramientasA · 90 de 100
• Resultados tipados0 de 14 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 8 de 14

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• qualify_task

  Use when a buyer's sanitized problem is not yet mapped to an offer. Returns one fixed offer ID, a broader-service route, or a scope-reduction decision; it performs no diagnosis and creates no order.

• acknowledge_purchase_offer

  Records that an agent actually received and retained one exact offer. A durable return method, operator linkage, and delegated limits are optional and recorded only when truthfully supplied. Receipt-only acknowledgement creates no order…

• preflight_agent_purchase

  Read-only transaction check. Verifies product match, credential, standing agent policy or narrower signed mandate, exact offer allowlist, price ceiling, current terms, sanitized scope, capacity, and payment-route readiness. It creates no…

• resume_agent_purchase

  Read-only durable continuation. Returns the exact observed stop and next executable action for a previously returned opaque continuation token. It creates no purchase, checkout, charge, or order.

• find_service

  Optional demand-feedback route. Describe one authorized sanitized business need once. Zinvyl returns the best fixed-scope offer and next purchase action, or records an unsupported need as privacy-minimized product telemetry. For read-only…

• list_offers

  Use when comparing Zinvyl's full eight-offer catalog. For a single sanitized need, start with read-only qualify_task. Returns price, delivery window, required inputs, exclusions, and direct intake URL; use get_acceptance_tests only after…

• get_purchase_requirements

  Use after selecting an offer. Returns the exact price, five-field buy_service contract, delegated-authority requirements, machine-payment route, capacity limits, and authoritative funding rule without creating an intent.

• buy_matching_service

  One-call path for a buyer agent that has explicit delegated authority for a stated allowlist of exact Zinvyl offers. Zinvyl matches one sanitized outcome and creates a bounded purchase intent only when the matched offer is allowlisted and…

• buy_service

  Five-field, retry-safe agent purchase path. Creates one bounded intent only when delegated authority covers the exact fee. Reusing buyer.request_id for an unchanged purchase returns the same intent. Adaptively selects Stripe-hosted…

• recover_abandoned_purchase

  Recovers the original transaction for the same authenticated buyer, authority policy, request ID, offer, sanitized scope, amount, currency, funding route, and current terms. Before funding it resumes an expired reservation; after verified…

• create_purchase_intent

  Compatibility alias for existing clients; new integrations should use buy_service. Use only after selecting one offer when the calling agent has explicit delegated authority for that exact fixed fee. Creates the governed purchase intent…

• match_or_capture_demand

  Compatibility alias for existing clients; new integrations should use qualify_task first and find_service only after consent. Returns an existing fixed offer when one matches. Otherwise records privacy-minimized product-demand telemetry…

• get_acceptance_tests

  Use after qualify_task or list_offers identifies an offer and detailed scope review is useful. Returns the exact delivery acceptance tests, exclusions, and evidence boundaries that limit what Zinvyl may claim for that offer.

• prepare_purchase_route

  Compatibility inspection alias for existing clients; new integrations should use get_purchase_requirements and buy_service. Use only after selecting an offer and confirming explicit purchasing authority. Returns the purchase-intent schema…