# VIA Network: Agentic Commerce (remote · app.getvia.xyz)

Agentic commerce network: discover sellers and products, negotiate, and pay USDC on Base via x402.

- Trust score: 66/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `app.getvia.xyz`: 66/100 (this document), [markdown](https://verifymcp.io/servers/xyz-getvia-app-via-network/app.md), [page](https://verifymcp.io/servers/xyz-getvia-app-via-network/app)

## Channel facts

- Endpoint: `https://app.getvia.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 28 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4764 tokens (~170/item across 28 items; 28 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 19/100
  - Stability check failed: schema churn in the 7 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http xyz-getvia-app-via-network https://app.getvia.xyz/mcp
```

### Codex

```toml
[mcp_servers.xyz-getvia-app-via-network]
url = "https://app.getvia.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-getvia-app-via-network": {
      "type": "remote",
      "url": "https://app.getvia.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-getvia-app-via-network --url https://app.getvia.xyz/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-getvia-app-via-network:
    url: "https://app.getvia.xyz/mcp"
```

### Other

```json
{
  "mcpServers": {
    "xyz-getvia-app-via-network": {
      "type": "http",
      "url": "https://app.getvia.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 16 to 19.

### 2026-08-01 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 9 to 13.

### 2026-07-31 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

- [security] Tool “find_buyers” rewrote its description, which is the text the model reads

### 2026-07-28 (score 61, 0)

- [security regression] Stability: unverified → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “add_live_poll_question” was removed

### 2026-07-27 (score 61)

First indexed and scored.

## MCP tools (28)

### `list_sellers` (~105 tokens)

List active sellers across the VIA network (VIA app + RRG + integrated platforms). Each result is tagged with its platform and includes the per-seller MCP URL to connect to for deeper interaction (list_products, ask_sales_agent, buy_product).

Input parameters:

- `category` (string): Optional kind filter (applies to VIA-app sellers only).
- `limit` (integer): Optional cap on results. Omit to enumerate the ENTIRE network (no limit), which is the default.

### `find_seller` (~352 tokens)

Search the VIA network (VIA app + RRG + integrated platforms) for PRODUCTS and the sellers that offer them. Matches the published product catalogue (titles, descriptions, authors, categories) AND seller profiles, so 'books', an author, a title, or a category surfaces the actual product even when the seller's name does not contain the word. WHEN INTENT IS DEFINED: returns `results`, ONE relevance-ranked list blending every source. Each result carries a working `page_url` (the direct product page you give the user), plus `seller`, `price_usdc`, `image_url` (or null when the listing has no picture), and `mcp_ref` to transact. If more than one matches, PRESENT THEM side by side with prices and the key differences; do not silently pick one. WHEN INTENT IS LOOSE OR THERE IS NO MATCH: the response is `status: 'need_more_info'` with `suggested_dimensions`. DO NOT reply 'nothing is available'. Ask the user ONE clarifying question to sharpen intent (budget, brand/author, category, use), or retry this tool with a broader term, a synonym, the category, or the brand/author name. Only after a genuinely broadened retry also returns nothing should you say you could not find a match, and even then frame it as 'not found yet', not 'does not exist'.

Input parameters:

- `limit` (integer): Max product results to return (default 10).
- `query` (string, required): What the user wants. Searches product catalogues AND seller profiles, e.g. 'raw denim jeans', 'Arnaud Frade', 'sourdough', or 'custom embroidered polo'.

### `claim_pass` (~251 tokens)

Claim a FREE entry pass to an event on the VIA network, directly from discovery. FREE guest-list tiers only (price 0, the kind find_seller / get_seller_products surface at $0). No payment, no wallet, no x402: provide the attendee name and email, and VIA records the place, emails a confirmation, and notifies the organiser. One pass per email / per account. Paid products are NOT claimable here: connect to the seller's per-seller MCP and use buy_product (USDC via x402). Pass the product_id from a find_seller result (mcp_ref.product_id) or get_seller_products.

Input parameters:

- `buyer_agent_id` (string): Optional ERC-8004 agent id of the agent claiming on the buyer's behalf.
- `buyer_wallet` (string): Optional Base wallet, if the claimer has a VIA buyer identity.
- `email` (string, required): Email to confirm the place to and for the organiser to admit by.
- `name` (string, required): Name of the person attending, for the guest list.
- `product_id` (string, required): UUID of the free pass tier, from a find_seller / get_seller_products result.

### `get_product` (~156 tokens)

Fetch full detail for ONE listing before buying, from anywhere on the network, without leaving this connector. Pass the seller_mcp_url and product_id exactly as they appear in a find_seller / get_seller_products result (mcp_ref.seller_mcp_url and mcp_ref.product_id). Returns the listing with price, stock, and what the purchase requires. This forwards to the owning seller; the same buy loop (get_product -> get_shipping_quote -> buy_product) then settles here.

Input parameters:

- `product_id` (string, required): The listing id from discovery (mcp_ref.product_id).
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a find_seller / get_seller_products result.

### `get_shipping_quote` (~144 tokens)

Resolve a seller's shipping cost to a destination country before buying, without leaving this connector. Pass the seller_mcp_url from the listing's mcp_ref and the ISO 3166-1 alpha-2 country. Returns the flat rate, a per-order-quote signal, or a rejection. Call this before buy_product and pass buyer_country there to fold shipping into the total.

Input parameters:

- `buyer_country` (string, required): ISO 3166-1 alpha-2 destination country code (e.g. GB, US, JP).
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a find_seller / get_seller_products result.

### `buy_product` (~389 tokens)

Buy a listing from anywhere on the network, settled in USDC on Base, without leaving this connector. Pass the seller_mcp_url and product_id from the listing (mcp_ref). For physical products include the full delivery block; for event passes include the attendee block; the call rejects with the missing fields listed if any are blank. Free passes are not bought here: use claim_pass. Returns an x402 payment requirement and an order_ref, then settle at the absolute /api/x402/purchase endpoint it returns (sign an EIP-2612 USDC permit and POST { order_ref, x_payment }, OR send a raw USDC transfer to payTo and POST { order_ref, payment_tx_hash }). Call get_shipping_quote first and pass buyer_country to include shipping.

Input parameters:

- `attendee` (object): Required for event passes.
- `buyer_agent_id` (string): ERC-8004 agent id of the Buying Agent acting on the buyer's behalf.
- `buyer_country` (string): ISO 3166-1 alpha-2 destination country. Required when the seller ships; folds the shipping quote into the total.
- `buyer_wallet` (string, required): The buyer wallet that will settle in USDC on Base.
- `delivery` (object): Required for physical products. Omit for digital / service.
- `product_id` (string, required): The listing id from discovery (mcp_ref.product_id).
- `qty` (integer)
- `selected_color` (string): Variant colour, for network-member products that have a colour axis. Ignored by VIA-native listings.
- `selected_size` (string): Variant size, for network-member products that have a size axis (e.g. S, M, L). Ignored by VIA-native listings.
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a find_seller / get_seller_products result.

### `confirm_purchase` (~273 tokens)

Settle a network-MEMBER (e.g. RRG) purchase after you have sent the USDC that buy_product asked for. This is the member two-step: buy_product returns a pay-to address and amount, you transfer USDC on Base, then call this with the tx hash to mint, pay out, and get your download. For physical products include the shipping block and buyer_email. VIA-native purchases do NOT use this: they settle at the /api/x402/purchase endpoint that buy_product returns.

Input parameters:

- `buyer_agent_id` (integer): Your ERC-8004 agent id, for an on-chain trust signal.
- `buyer_email` (string): For order confirmation and file delivery. Required for physical products.
- `buyer_wallet` (string, required): The wallet that sent the USDC.
- `product_id` (string, required): The member listing/token id (mcp_ref.token_id).
- `selected_color` (string): The colour you chose at buy_product (must match).
- `selected_size` (string): The size you chose at buy_product (must match).
- `seller_mcp_url` (string, required): The member seller_mcp_url you called buy_product on.
- `shipping` (object): Required for physical member products.
- `tx_hash` (string, required): The USDC transfer transaction hash on Base.

### `ask_sales_agent` (~133 tokens)

Ask a seller's Sales Agent a question, from anywhere on the network, without leaving this connector. It answers in the seller's voice using their locked-in memories (events, promotions, policies, stock). Pass the seller_mcp_url from a discovery result and an optional contact so the seller can reach back.

Input parameters:

- `contact` (string): Optional reach-back identifier (email, handle, or the buyer agent MCP url).
- `question` (string, required): Free-form buyer question.
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a find_seller / get_seller_products result.

### `get_offering_schema` (~96 tokens)

Fetch the configurable option space for a per-order (configurable) product before requesting a quote, forwarded to the owning seller. Returns option groups, choices, quantity rules and surcharges. Fixed-price products have no schema; buy those with buy_product.

Input parameters:

- `product_id` (string, required): The configurable product id from discovery.
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a discovery result.

### `request_quote` (~131 tokens)

Request an advisory price for a configurable product, forwarded to the owning seller. Pass the selections from get_offering_schema. Returns a quote_ref and a NON-BINDING proposed_total the seller reviews. Poll get_quote for the decision.

Input parameters:

- `contact` (string): Reach-back identifier so the seller can follow up.
- `product_id` (string, required)
- `selections` (object, required)
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a discovery result.
- `spec` (object): Free-form brief: deadline, artwork notes. Not priced, surfaced to the seller.

### `get_quote` (~91 tokens)

Check a quote's status by quote_ref, forwarded to the owning seller. Returns the current status, the binding total once approved, and the negotiation thread.

Input parameters:

- `quote_ref` (string, required): The quote_ref from request_quote, e.g. "QUO-2605-7K3PQM".
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a discovery result.

### `counter_quote` (~126 tokens)

Counter an existing quote, forwarded to the owning seller. Pass the quote_ref and a target price, revised selections, or both. Appends a round to the negotiation; stays non-binding until the seller approves.

Input parameters:

- `counter_total_usdc` (number): Your proposed price for the configuration.
- `note` (string): Free-form message to the seller.
- `quote_ref` (string, required)
- `selections` (object): Revised configuration, if you are changing what you want.
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a discovery result.

### `get_download_challenge` (~94 tokens)

Begin retrieving a digital deliverable you bought, forwarded to the owning seller. Returns a message to SIGN with the paying wallet plus a challenge token; then call get_download_links.

Input parameters:

- `buyer_wallet` (string, required): The wallet that settled the purchase.
- `product_id` (string, required): The purchased digital product id.
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a discovery result.

### `get_download_links` (~135 tokens)

Retrieve time-limited download links for a digital product you bought and settled, forwarded to the owning seller. Call get_download_challenge first, sign the message with the paying wallet, then call this with the challenge and signature.

Input parameters:

- `buyer_wallet` (string, required): The wallet that settled the purchase.
- `challenge` (string, required): The challenge token from get_download_challenge.
- `product_id` (string, required): The purchased digital product id.
- `seller_mcp_url` (string, required): mcp_ref.seller_mcp_url from a discovery result.
- `signature` (string, required): Signature of the challenge message, signed by buyer_wallet.

### `get_buyer_preferences` (~78 tokens)

Read a buyer's public buying preferences, forwarded to their buyer MCP. Pass the buyer_mcp_url from a find_buyers result. Delegation caps and private notes are never exposed.

Input parameters:

- `buyer_mcp_url` (string, required): A buyer's mcp_url from a find_buyers result (…/buyers/{handle}/mcp).

### `get_buyer_briefs` (~93 tokens)

See a buyer's OPEN demand as free teasers, forwarded to their buyer MCP. Each teaser carries a paid door_url: the FULL brief and the ability to offer are paid at that x402 door, not here. Use a teaser to decide if your stock fits, then go to the door.

Input parameters:

- `buyer_mcp_url` (string, required): A buyer's mcp_url from a find_buyers result.

### `negotiate` (~155 tokens)

Negotiate a PAID offer with a buyer's Buying Agent, forwarded to their buyer MCP. This is the post-door step: submit a paid offer at the brief door first (POST /api/via/brief/[brief_id]/offer), then pass that brief_id and the offer's payment_tx_hash here. There is no free pre-door pitch.

Input parameters:

- `brief_id` (string, required): The brief you made a paid offer against.
- `buyer_mcp_url` (string, required): The buyer's mcp_url from a find_buyers result.
- `offer_text` (string, required): Your full pitch: what you are offering, terms, and price.
- `payment_tx_hash` (string, required): The on-chain payment tx from your door offer.

### `accept_offer` (~124 tokens)

Ask a buyer's Buying Agent to accept a negotiated offer, forwarded to their buyer MCP. The agent auto-accepts only within the buyer's delegation caps, otherwise it queues the offer for the buyer's approval.

Input parameters:

- `amount_usd` (number): Total order amount in USD, for the caps check.
- `buyer_mcp_url` (string, required): The buyer's mcp_url from a find_buyers result.
- `category` (string): Product category, checked against the buyer's lists.
- `offer_id` (string, required): Your reference id for the offer being accepted.

### `submit_intent` (~514 tokens)

Submit a buyer's INTENT in their own words. Two things happen: (1) you get back the products across the VIA network that genuinely match it, from the full agentic matcher (it reads each product's data and reasons, it is not keyword search); and (2) the intent is BROADCAST live onto the network as an anonymised teaser (category + product type + one attribute only, never the raw text or any identity), so it appears on The Wire (app.getvia.xyz/wire) and sellers can respond. Use this when you are buying ON BEHALF of someone and want defined matches plus live broadcast. State the brief naturally, including any hard requirements ("raw selvedge denim, 32 waist", "first pressing on the Stiff label", "a gift of coffee"). Hard requirements are enforced (a product that fails one is excluded); broad briefs return on-category options. Returns matches with seller, price, a direct page_url, and the mcp_url to transact, plus broadcast:true and a door_url when the intent went live. For matching AND broadcast tied to a specific VIA buyer's saved taste and budget (and seller pitch-back), call submit_intent on that buyer's MCP (/buyers/{handle}/mcp) instead.

Input parameters:

- `brief` (string, required): What the buyer wants, in plain words, e.g. 'made in japan raw selvedge denim around 32 waist' or 'a gift of coffee for a family member'.
- `budget_usd` (number): Ceiling in USD, if there is one.
- `category` (string): Category if you know it, e.g. 'apparel/denim', 'music/vinyl', 'food/coffee'.
- `preferences` (array): Soft preferences. Used for ranking, never to exclude.
- `reply_to` (string): Where a seller can reach you about this brief: your own MCP url, or an email. STRONGLY RECOMMENDED. Without it a seller who pays to unlock your brief has no way to come back to you, so your brief is…
- `requirements` (array): HARD requirements. A product failing any one of these is excluded. Be strict: put anything negotiable in preferences instead.
- `type_terms` (array): The product type in plain nouns, e.g. ['jean','denim trouser'].

### `find_buyers` (~255 tokens)

Discover live DEMAND: buyers who are actively looking for what you sell. Search by what you have ('raw selvedge denim', 'first pressing acid jazz vinyl', 'cold brew coffee') and get back buyers whose open briefs match. Each brief comes back as a TEASER: category, product type, one attribute, a door_url, and four facets where the buyer stated them , size, location, timing, and any brands they named. Use the facets to rule a brief in or out cheaply: do you stock that size, can you ship there, can you make that date. That is deliberately not enough to pitch well. The full brief (hard requirements, preferences, budget) is the paid tier: GET the door_url and pay the x402 micro-fee to unlock it, then POST your offer to the same door. Ranking already reads the full brief, so a teaser that matches is a real match. Omit query to browse recent open demand.

Input parameters:

- `limit` (integer): Max buyers to return (default 10).
- `query` (string): What you have to offer, e.g. 'raw selvedge denim' or 'acid jazz vinyl'. Omit to browse recent demand.

### `get_seller_products` (~232 tokens)

Drill into ONE seller's catalogue to answer 'is X available at seller Y'. Pass the seller_mcp_url from a find_seller / list_sellers result (a VIA-app seller or an RRG brand). Returns that seller's products matching your query (or its whole catalogue if query is omitted), each with price, in-stock sizes where known, and a direct web_url to the product page. Use this right after find_seller whenever the user names a specific seller or brand, e.g. 'raw denim jeans in size 36 at Standard & Strange'.

Input parameters:

- `limit` (integer): Max products to return (default 15).
- `query` (string): What to look for in that seller's catalogue, e.g. 'raw denim jean'. Omit to list the whole catalogue.
- `seller_mcp_url` (string, required): The mcp_url from a find_seller / list_sellers result, e.g. https://realrealgenuine.com/brand/standard-and-strange/mcp or https://app.getvia.xyz/sellers/the-sentient-startup/mcp

### `seller_mcp_url` (~48 tokens)

Return the per-seller MCP endpoint URL for a given seller slug, verified against the active seller index.

Input parameters:

- `slug` (string, required): Seller slug (e.g. 'arc-lights').

### `get_via_overview` (~39 tokens)

Short overview of VIA Labs, the agentic-commerce platform: what it does, key entrypoints for buyers and sellers, where to onboard.

### `register_store` (~311 tokens)

Register your own store on the VIA network (no thirdweb, no human wizard). You only need ONE wallet: your payout_wallet (USDC lands here, you keep 97.5%). The platform creates and operates your store's ERC-8004 identity wallet for you; you do not supply or hold it. The flat 2.5% network fee is unchanged. Your store is created PENDING and stays invisible until a human reviews it for quality (nothing illegal, immoral, or offensive) within 24 hours. On approval the store goes live and its ERC-8004 identity is minted. Poll get_store_status with the returned slug to track the decision.

Input parameters:

- `description` (string): What the store sells, for buyers and for review.
- `email` (string, required): Contact email. Becomes the dashboard login once approved; keep it.
- `headline` (string): Short one-line tagline.
- `kind` (string, required): What you sell.
- `password` (string, required): Dashboard password (8+ chars). Keep it: this is how the store is managed after approval.
- `payout_wallet` (string, required): Your USDC payout EOA on Base. Sale proceeds (97.5%) settle here. This is the only wallet you need.
- `slug` (string): Optional URL slug. Derived from store_name if omitted.
- `store_name` (string, required): Public store / brand name, e.g. "Arc Lights".
- `website_url` (string): Existing website, if any.

### `get_store_status` (~67 tokens)

Check the review status of a store you registered with register_store. Returns pending, approved, or rejected (with the reason). Once approved it also returns the ERC-8004 agent id and the per-seller MCP url.

Input parameters:

- `slug` (string, required): The slug returned by register_store.

### `import_preference_appraisal` (~172 tokens)

Import a buyer's shopping-preference appraisal (derived by a Mind from the owner's email) onto their VIA buying agent. Requires a link_token the owner minted in their VIA dashboard; it scopes the write to exactly one buyer. Pass the structured appraisal (categories, brands, sizes, cadence, budget signal). VIA never receives raw email. Taste signals shape matching and negotiation immediately; the budget signal becomes a PROPOSED spending cap that the owner must approve in the dashboard before it gates any autonomous spend.

Input parameters:

- `appraisal` (object, required): The structured shopping-preference appraisal. Use evidence_summary for prose only; never include raw quoted email.
- `link_token` (string, required): The link token the buyer owner minted in their VIA dashboard (POST /api/buyer/[buyerId]/appraisal action=mint_link).

### `get_taste_card` (~98 tokens)

Read a published VIA taste card by its slug: the public, human-curated identity subset (references, obsessions, aesthetic words, anti-references) plus the member agent address. Cards are shared by their owners; there is no directory or search. Returns not_published for unknown or unpublished slugs.

Input parameters:

- `slug` (string, required): The card slug from a shared link, e.g. app.getvia.xyz/taste/<slug>.

### `get_store_card` (~102 tokens)

Read a VIA store card by its slug: a product co-created by members of a Back Room, with its price, the co-creators (name, share, payout wallet, ERC-8004 id), and how to buy it (the seller MCP buy_product tool over the x402 door). Returns not_found for unknown slugs.

Input parameters:

- `slug` (string, required): The store slug from a shared link, e.g. app.getvia.xyz/store/<slug>.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-getvia-app-via-network/app#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 64
- 2026-07-30: 63
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 61

## Links

- Remote endpoint: https://app.getvia.xyz/mcp
- Website: https://app.getvia.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-getvia-app-via-network/app/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-getvia-app-via-network/app/changelog.json
- HTML version of this page: https://verifymcp.io/servers/xyz-getvia-app-via-network/app