Skip to content
Zinvyl logo

Zinvyl MCP server

Which MCP servers are Zinvyl's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to Zinvyl

Whose server it is
  • Registry namecom.zinvyl/marketplaceverified in the MCP registry

The registry name sits under zinvyl.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools14
  • Server calls itselfzinvyl-marketplace-agent-gateway
  • Server version1.7.1
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 68 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • create_purchase_intent change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 8 of 14 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer736 ms
  • Space in an agent's context≈ 8,531 tokensthe definitions of all its tools (14), which an agent carries on every turn
  • Tool definitionsA · 90 of 100
  • Typed results0 of 14 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 8 of 14

What an agent can do with it

  • not sure · diagnose and repair a stalled project
  • not sure · build a promising idea into a working system
  • not sure · automate a fixed-scope business process

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_purchase_intent

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers14 tools · read 2026-10-25
  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "marketplace": {
      "type": "http",
      "url": "https://zinvyl.com/marketplace/agent-mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http zinvyl https://zinvyl.com/marketplace/agent-mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://zinvyl.com/marketplace/agent-mcp as a custom connector in the settings.

OpenAPI spec

7 paths, read 2026-10-25. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.