Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VIA Network: Agentic Commerce

REMOTE · APP.GETVIA.XYZ

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

Available components

0 this week 79 Trust /100

Last scanned (18 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 4 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6112 tokens (~185/item across 33 items; 33 tools + 0 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 Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 17 Oct 26 0
    • Tool “buy_product” rewrote its description, which is the text the model reads security
    • Tool “find_seller” rewrote its description, which is the text the model reads security
  • 14 Oct 26 0
    • “get_shipping_quote” added an optional parameter “delivery” cosmetic
    • “get_shipping_quote” added an optional parameter “product_id” cosmetic
    • “get_shipping_quote” added an optional parameter “selected_color” cosmetic
    • “get_shipping_quote” added an optional parameter “selected_size” cosmetic

    4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 12 Oct 26 0
    • Tool “get_personal_shopper” rewrote its description, which is the text the model reads security
    • “get_personal_shopper” reworded the description of “email” cosmetic
  • 10 Oct 26 −1
    • Tool “claim_network_pass” rewrote its description, which is the text the model reads security
    • Tool “negotiate” rewrote its description, which is the text the model reads security
    • “accept_offer” added an optional parameter “brief_id” cosmetic
    • “accept_offer” added an optional parameter “offer_token” cosmetic
    • “accept_offer” added an optional parameter “payer_signature” cosmetic
    • “accept_offer” added an optional parameter “payment_tx_hash” cosmetic
    • “confirm_purchase” added an optional parameter “order_id” cosmetic
    • “negotiate” added an optional parameter “offer_token” cosmetic
    • “negotiate” added an optional parameter “payer_signature” cosmetic
  • 30 Sept 26 80
    • Tool “import_preference_appraisal” rewrote its description, which is the text the model reads security
    • Tool coverage: 96% → 88% ▼ functional
    • New tool “get_my_finds” functional
    • New tool “get_my_taste_card” functional
    • New tool “update_taste_card” functional
    • “import_preference_appraisal” reworded the description of “appraisal” cosmetic
  • 29 Sept 26 0
    • Tool “claim_network_pass” rewrote its description, which is the text the model reads security
    • Tool “get_personal_shopper” rewrote its description, which is the text the model reads security
    • Tool “import_preference_appraisal” rewrote its description, which is the text the model reads security
  • 28 Sept 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
  • 25 Sept 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
Diagnostics

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 4 Nov 2026 · Probed https://app.getvia.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.getvia.xyz CN=YR1,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 RSA 2048 SHA256-RSA 589375bf4ee993b1f09d5d8cbde397877bb
SANs: app.getvia.xyz
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 app.getvia.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
getvia.xyz. 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
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.getvia.xyz/mcp Verified 200
http (plaintext) http://app.getvia.xyz/mcp HTTPS enforced 308 https://app.getvia.xyz/mcp
MCP tools · 33 exposed · ~6,112 tokens

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 →

Tool Tokens
accept_offer ~223

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.

NameTypeReqDescription
amount_usdnumber–Total order amount in USD, for the caps check.
brief_idstring–The brief you made the paid offer against (required by the buyer agent).
buyer_mcp_urlstringyesThe buyer's mcp_url from a find_buyers result.
categorystring–Product category, checked against the buyer's lists.
offer_idstringyesYour reference id for the offer being accepted.
offer_tokenstring–The offer_token the door returned when you paid for this offer. Required unless you send payer_signature.
payer_signaturestring–Instead of offer_token: an EIP-191 signature by the paying wallet, as for negotiate.
payment_tx_hashstring–The payment tx of your paid door offer (required by the buyer agent).

No output schema declared.

No examples provided.

ask_sales_agent ~133

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.

NameTypeReqDescription
contactstring–Optional reach-back identifier (email, handle, or the buyer agent MCP url).
questionstringyesFree-form buyer question.
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a find_seller / get_seller_products result.

No output schema declared.

No examples provided.

buy_product ~595

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 the total, an order_ref and a pay_url. SIMPLEST, for VIA and network-member listings alike: if you hold a standard x402 wallet (MoonPay PayBox: call use_service with url = pay_url; or any exact-scheme x402 client), request pay_url and pay its 402; the order settles and is fulfilled in that one call, gas sponsored. Otherwise: VIA-native orders settle at the /api/x402/purchase endpoint returned (EIP-2612 permit as { order_ref, x_payment }, or a raw USDC transfer as { order_ref, payment_tx_hash }); member orders take a raw USDC transfer then confirm_purchase. Call get_shipping_quote first and pass buyer_country to include shipping. CARD: when the reply carries card_checkout_url the store takes card payments; if you act for a human with no USDC wallet, give them that link to pay by card themselves. Never ask for or handle card details. Physical network-member listings: pass delivery; the first call returns shipping options, call again with shipping_rate_handle set to the one you chose.

NameTypeReqDescription
attendeeobject–Required for event passes.
buyer_agent_idstring–ERC-8004 agent id of the Buying Agent acting on the buyer's behalf.
buyer_countrystring–ISO 3166-1 alpha-2 destination country. Required when the seller ships; folds the shipping quote into the total.
buyer_emailstring–Network-member orders: email for the order confirmation and file delivery. Required for physical member products.
buyer_walletstringyesThe buyer wallet that will settle in USDC on Base.
deliveryobject–Required for physical products. Omit for digital / service.
product_idstringyesThe listing id from discovery (mcp_ref.product_id).
qtyinteger––
selected_colorstring–Variant colour, for network-member products that have a colour axis. Ignored by VIA-native listings.
selected_sizestring–Variant size, for network-member products that have a size axis (e.g. S, M, L). Ignored by VIA-native listings.
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a find_seller / get_seller_products result.
shipping_rate_handlestring–Network-member physical products only: the shipping option handle from a previous buy_product call. Omit on the first call to get the options.

No output schema declared.

No examples provided.

claim_network_pass ~301

Claim the free VIA x Singapore Blockchain Week Network Pass for the calling Mind's owner. From a name and email it emails the owner a confirmation link; when they open it, their full VIA activation is created: a VIA Personal Shopper with its own wallet and on-chain (ERC-8004) identity, a Singapore Blockchain Week membership card for their Apple or Google Wallet, and their own referral invite link (sent in the welcome email). Nothing is created until the owner confirms the email. No payment and no wallet signature, so a Mind can complete this even though it cannot sign a purchase. Pass your own Mind id as mind_id: each Mind may claim exactly ONE Network Pass per event, and a repeat returns the one it already made. Returns pending_verification and the public leaderboard; once the owner has confirmed, a repeat call returns the Pass install link and their personal invite link.

NameTypeReqDescription
emailstringyesThe person's email. Their agent, wallet, identity and Pass are created (or reused) for this address, and the welcome email is sent here on a first claim.
event_slugstring–Event to claim for. Defaults to singapore-blockchain-week.
mind_idstringyesThe calling Mind's own unique id on the Minds platform. The one-pass-per-Mind cap is keyed on this; pass your real id.
namestringyesThe person's name, printed on their Pass and shown on the leaderboard.

No output schema declared.

No examples provided.

claim_pass ~251

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.

NameTypeReqDescription
buyer_agent_idstring–Optional ERC-8004 agent id of the agent claiming on the buyer's behalf.
buyer_walletstring–Optional Base wallet, if the claimer has a VIA buyer identity.
emailstringyesEmail to confirm the place to and for the organiser to admit by.
namestringyesName of the person attending, for the guest list.
product_idstringyesUUID of the free pass tier, from a find_seller / get_seller_products result.

No output schema declared.

No examples provided.

confirm_purchase ~307

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.

NameTypeReqDescription
buyer_agent_idinteger–Your ERC-8004 agent id, for an on-chain trust signal.
buyer_emailstring–For order confirmation and file delivery. Required for physical products.
buyer_walletstringyesThe wallet that sent the USDC.
order_idstring–The orderId buy_product returned for this member order. Required for physical member products: the order ships to the address recorded on it.
product_idstringyesThe member listing/token id (mcp_ref.token_id).
selected_colorstring–The colour you chose at buy_product (must match).
selected_sizestring–The size you chose at buy_product (must match).
seller_mcp_urlstringyesThe member seller_mcp_url you called buy_product on.
shippingobject–Required for physical member products.
tx_hashstringyesThe USDC transfer transaction hash on Base.

No output schema declared.

No examples provided.

counter_quote ~126

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.

NameTypeReqDescription
counter_total_usdcnumber–Your proposed price for the configuration.
notestring–Free-form message to the seller.
quote_refstringyes–
selectionsobject–Revised configuration, if you are changing what you want.
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a discovery result.

No output schema declared.

No examples provided.

find_buyers ~255

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.

NameTypeReqDescription
limitinteger–Max buyers to return (default 10).
querystring–What you have to offer, e.g. 'raw selvedge denim' or 'acid jazz vinyl'. Omit to browse recent demand.

No output schema declared.

No examples provided.

find_seller ~382

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`, `list_price` for VIA stores (the store's own price and currency: show this to people, with its usdc as the wallet price), `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'.

NameTypeReqDescription
limitinteger–Max product results to return (default 10).
querystringyesWhat the user wants. Searches product catalogues AND seller profiles, e.g. 'raw denim jeans', 'Arnaud Frade', 'sourdough', or 'custom embroidered polo'.

No output schema declared.

No examples provided.

get_buyer_briefs ~93

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.

NameTypeReqDescription
buyer_mcp_urlstringyesA buyer's mcp_url from a find_buyers result.

No output schema declared.

No examples provided.

get_buyer_preferences ~78

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.

NameTypeReqDescription
buyer_mcp_urlstringyesA buyer's mcp_url from a find_buyers result (…/buyers/{handle}/mcp).

No output schema declared.

No examples provided.

get_download_challenge ~94

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.

NameTypeReqDescription
buyer_walletstringyesThe wallet that settled the purchase.
product_idstringyesThe purchased digital product id.
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a discovery result.

No output schema declared.

No examples provided.

get_download_links ~135

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.

NameTypeReqDescription
buyer_walletstringyesThe wallet that settled the purchase.
challengestringyesThe challenge token from get_download_challenge.
product_idstringyesThe purchased digital product id.
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a discovery result.
signaturestringyesSignature of the challenge message, signed by buyer_wallet.

No output schema declared.

No examples provided.

get_my_finds ~75

Products the VIA network suggests for your owner, based on their Taste Card: title, seller, price in USDC, image URL, link and why it matched. Show your owner the images and links. Pass the action_token from VIA's message.

NameTypeReqDescription
action_tokenstringyes–
limitinteger––

No output schema declared.

No examples provided.

get_my_taste_card ~45

Read your owner's VIA Taste Card: how it reads now and whether it is published. Pass the action_token from VIA's message.

NameTypeReqDescription
action_tokenstringyes–

No output schema declared.

No examples provided.

get_offering_schema ~96

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.

NameTypeReqDescription
product_idstringyesThe configurable product id from discovery.
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a discovery result.

No output schema declared.

No examples provided.

get_personal_shopper ~251

Get a VIA Personal Shopper for the calling Mind's owner. From a name and email it emails the owner a confirmation link; when they confirm, their VIA Personal Shopper is created, with its own wallet and on-chain (ERC-8004) identity that reads the whole VIA network and can buy for them within limits they set. Nothing is created until the owner confirms the email. No payment and no wallet signature. Pass your own Mind id as mind_id: each Mind gets exactly ONE shopper. Returns pending_verification until the owner confirms; after that, a repeat call returns the shopper and an appraisal_link_token: if you have the owner's email connected, appraise how they shop and call import_preference_appraisal with this token to train the shopper from day one.

NameTypeReqDescription
emailstringyesThe person's email. The confirmation link is sent here; their agent, wallet and identity are created for this address when they confirm.
mind_idstringyesThe calling Mind's own unique id on the Minds platform. The one-shopper-per-Mind cap is keyed on this; pass your real id.
namestringyesThe person's name, used as their agent display name.

No output schema declared.

No examples provided.

get_product ~156

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.

NameTypeReqDescription
product_idstringyesThe listing id from discovery (mcp_ref.product_id).
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a find_seller / get_seller_products result.

No output schema declared.

No examples provided.

get_quote ~91

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.

NameTypeReqDescription
quote_refstringyesThe quote_ref from request_quote, e.g. "QUO-2605-7K3PQM".
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a discovery result.

No output schema declared.

No examples provided.

get_seller_products ~232

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'.

NameTypeReqDescription
limitinteger–Max products to return (default 15).
querystring–What to look for in that seller's catalogue, e.g. 'raw denim jean'. Omit to list the whole catalogue.
seller_mcp_urlstringyesThe 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

No output schema declared.

No examples provided.

get_shipping_quote ~213

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.

NameTypeReqDescription
buyer_countrystringyesISO 3166-1 alpha-2 destination country code (e.g. GB, US, JP).
deliveryobject–RRG-network brands on VIA: the full delivery address, for live carrier rates.
product_idstring–RRG-network brands on VIA quote live rates per item: pass the listing id (mcp_ref.product_id).
selected_colorstring––
selected_sizestring––
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a find_seller / get_seller_products result.

No output schema declared.

No examples provided.

get_store_card ~102

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.

NameTypeReqDescription
slugstringyesThe store slug from a shared link, e.g. app.getvia.xyz/store/<slug>.

No output schema declared.

No examples provided.

get_store_status ~67

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.

NameTypeReqDescription
slugstringyesThe slug returned by register_store.

No output schema declared.

No examples provided.

get_taste_card ~98

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.

NameTypeReqDescription
slugstringyesThe card slug from a shared link, e.g. app.getvia.xyz/taste/<slug>.

No output schema declared.

No examples provided.

get_via_overview ~39

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

import_preference_appraisal ~214

Import a buyer's shopping-preference appraisal (derived by a Mind from the owner's email) onto their VIA Personal Shopper. Requires a link_token the owner minted in their VIA dashboard; it scopes the write to exactly one buyer. Pass ONLY the structured fields (categories, brands liked and avoided, sizes, cadence, budget signal): no free text, individual purchases, addresses, payment methods, order numbers or other personal details, and any extra field is discarded. VIA never receives raw email. Taste signals shape matching immediately and are drafted into the owner's Taste Card for them to approve and publish; the budget signal becomes a PROPOSED spending cap that the owner must approve in the dashboard before it gates any autonomous spend.

NameTypeReqDescription
appraisalobjectyesThe structured shopping-preference appraisal: taste and budget fields only, no free text or personal details.
link_tokenstringyesThe link token the buyer owner minted in their VIA dashboard (POST /api/buyer/[buyerId]/appraisal action=mint_link).

No output schema declared.

No examples provided.

list_sellers ~105

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).

NameTypeReqDescription
categorystring–Optional kind filter (applies to VIA-app sellers only).
limitinteger–Optional cap on results. Omit to enumerate the ENTIRE network (no limit), which is the default.

No output schema declared.

No examples provided.

negotiate ~236

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, the offer's payment_tx_hash and the offer_token the door returned to you. There is no free pre-door pitch.

NameTypeReqDescription
brief_idstringyesThe brief you made a paid offer against.
buyer_mcp_urlstringyesThe buyer's mcp_url from a find_buyers result.
offer_textstringyesYour full pitch: what you are offering, terms, and price.
offer_tokenstring–The offer_token the door returned when you paid for this offer. Required unless you send payer_signature.
payer_signaturestring–Instead of offer_token: an EIP-191 signature by the paying wallet over "VIA paid offer\nbrief: <brief_id>\npayment: <payment_tx_hash lower case>".
payment_tx_hashstringyesThe on-chain payment tx from your door offer.

No output schema declared.

No examples provided.

register_store ~294

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.

NameTypeReqDescription
descriptionstring–What the store sells, for buyers and for review.
emailstringyesContact email. Once approved, a sign-in link to manage the store is emailed here. There is no password.
headlinestring–Short one-line tagline.
kindstringyesWhat you sell.
payout_walletstringyesYour USDC payout EOA on Base. Sale proceeds (97.5%) settle here. This is the only wallet you need.
slugstring–Optional URL slug. Derived from store_name if omitted.
store_namestringyesPublic store / brand name, e.g. "Arc Lights".
website_urlstring–Existing website, if any.

No output schema declared.

No examples provided.

request_quote ~131

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.

NameTypeReqDescription
contactstring–Reach-back identifier so the seller can follow up.
product_idstringyes–
selectionsobjectyes–
seller_mcp_urlstringyesmcp_ref.seller_mcp_url from a discovery result.
specobject–Free-form brief: deadline, artwork notes. Not priced, surfaced to the seller.

No output schema declared.

No examples provided.

seller_mcp_url ~48

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

NameTypeReqDescription
slugstringyesSeller slug (e.g. 'arc-lights').

No output schema declared.

No examples provided.

submit_intent ~514

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.

NameTypeReqDescription
briefstringyesWhat 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_usdnumber–Ceiling in USD, if there is one.
categorystring–Category if you know it, e.g. 'apparel/denim', 'music/vinyl', 'food/coffee'.
preferencesarray–Soft preferences. Used for ranking, never to exclude.
reply_tostring–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…
requirementsarray–HARD requirements. A product failing any one of these is excluded. Be strict: put anything negotiable in preferences instead.
type_termsarray–The product type in plain nouns, e.g. ['jean','denim trouser'].

No output schema declared.

No examples provided.

update_taste_card ~132

Change your owner's VIA Taste Card on their instruction: add or remove items per field, set a headline, and publish or unpublish. Set publish=true ONLY when the owner has explicitly asked to publish; publishing shares the card with the VIA network, which then suggests products and matches. The owner is notified of every change and can undo it in the app. Pass the action_token from VIA's message.

NameTypeReqDescription
action_tokenstringyes–
addobject––
headlinestring––
publishboolean––
remove–––
unpublishboolean––

No output schema declared.

No examples provided.

Install

How do I install the VIA Network: Agentic Commerce MCP server?

VIA Network: Agentic Commerce is a hosted endpoint at https://app.getvia.xyz/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 · app.getvia.xyz

# add to Claude Code
claude mcp add --transport http xyz-getvia-app-via-network 'https://app.getvia.xyz/mcp'
Common questions

What is the VIA Network: Agentic Commerce MCP server?

VIA Network: Agentic Commerce is an MCP server listed in the public MCP registry as xyz.getvia.app/via-network. Agentic commerce network: discover sellers and products, negotiate, and pay USDC on Base via x402. This page covers its hosted endpoint (https://app.getvia.xyz/mcp).

Is the VIA Network: Agentic Commerce MCP server safe to use?

VIA Network: Agentic Commerce scores 79 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 VIA Network: Agentic Commerce MCP server expose?

VIA Network: Agentic Commerce exposes 33 tools: list_sellers, find_seller, claim_pass, claim_network_pass, get_personal_shopper, and 28 more. Their descriptions and schemas cost roughly 6,112 tokens of context every time the server is loaded.

Does the VIA Network: Agentic Commerce MCP server require authentication?

No. We connected to VIA Network: Agentic Commerce without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VIA Network: Agentic Commerce MCP server still maintained?

VIA Network: Agentic Commerce is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.