VIA Network: Agentic Commerce MCP server
xyz.getvia.app/via-networkapp.getvia.xyzstreamable-httpv1.0.1Scanned
Agentic commerce network: discover sellers and products, negotiate, and pay USDC on Base via x402.
33 tools: 1 do something that can't be undone, 12 change things and 20 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the VIA Network: Agentic Commerce MCP server can do
The VIA Network: Agentic Commerce MCP server is published by app.getvia.xyz, a domain the MCP Registry verified. It has 33 tools. It can do things that cannot be undone, such as sending, paying or publishing (confirm_purchase) and create or change data (12 tools: claim_pass, claim_network_pass, buy_product, ask_sales_agent and 8 more), but cannot delete data. 20 tools only read.
3 tools bring in text other people can write (seller_mcp_url, get_store_status and get_my_finds); 2 tools can send data out of your system (buy_product and confirm_purchase).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
33 tools
Can't be undone 1Claude Code: ask
confirm_purchaseSettle a network-MEMBER (e.g.Can send data outNo findings
Why it is in this group
- The name "confirm_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.shipping.phone): what the tool writes goes there.
Description, as the server wrote it 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.
Changes things 12Claude Code: ask
accept_offerAsk a buyer's Buying Agent to accept a negotiated offer, forwarded to their buyer MCP.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
ask_sales_agentAsk a seller's Sales Agent a question, from anywhere on the network, without leaving this connector.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
buy_productBuy a listing from anywhere on the network, settled in USDC on Base, without leaving this connector.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a destination (input.delivery.phone): what the tool writes goes there.
Description, as the server wrote it 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.
claim_network_passClaim the free VIA x Singapore Blockchain Week Network Pass for the calling Mind's owner.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
claim_passClaim a FREE entry pass to an event on the VIA network, directly from discovery.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
counter_quoteCounter an existing quote, forwarded to the owning seller.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
import_preference_appraisalImport a buyer's shopping-preference appraisal (derived by a Mind from the owner's email) onto their VIA Personal Shopper.No findings
Why it is in this group
- The name "import_preference_appraisal" says "import": a word for a change.
Description, as the server wrote it 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.
negotiateNegotiate a PAID offer with a buyer's Buying Agent, forwarded to their buyer MCP.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
register_storeRegister your own store on the VIA network (no thirdweb, no human wizard).No findings
Why it is in this group
- The name "register_store" says "store": a word for a change.
Description, as the server wrote it 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.
request_quoteRequest an advisory price for a configurable product, forwarded to the owning seller.No findings
Why it is in this group
- The name "request_quote" says "request": a word for a change.
Description, as the server wrote it 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.
submit_intentSubmit a buyer's INTENT in their own words.No findings
Why it is in this group
- The name "submit_intent" says "submit": a word for a change.
Description, as the server wrote it 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.
update_taste_cardChange your owner's VIA Taste Card on their instruction: add or remove items per field, set a headline, and publish or unpublish.No findings
Why it is in this group
- The name "update_taste_card" says "update": a word for a change.
Description, as the server wrote it 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.
Only reads 20Show 20 read-only tools
find_buyersDiscover live DEMAND: buyers who are actively looking for what you sell.No findings
Why it is in this group
- The name "find_buyers" says "find": a word for reading.
Description, as the server wrote it 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.
find_sellerSearch the VIA network (VIA app + RRG + integrated platforms) for PRODUCTS and the sellers that offer them.No findings
Why it is in this group
- The name "find_seller" says "find": a word for reading.
Description, as the server wrote it 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'.
get_buyer_briefsSee a buyer's OPEN demand as free teasers, forwarded to their buyer MCP.No findings
Why it is in this group
- The name "get_buyer_briefs" says "get": a word for reading.
Description, as the server wrote it 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.
get_buyer_preferencesRead a buyer's public buying preferences, forwarded to their buyer MCP.No findings
Why it is in this group
- The name "get_buyer_preferences" says "get": a word for reading.
Description, as the server wrote it 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.
get_download_challengeBegin retrieving a digital deliverable you bought, forwarded to the owning seller.No findings
Why it is in this group
- The name "get_download_challenge" says "get": a word for reading.
Description, as the server wrote it 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.
get_download_linksRetrieve time-limited download links for a digital product you bought and settled, forwarded to the owning seller.No findings
Why it is in this group
- The name "get_download_links" says "get": a word for reading.
Description, as the server wrote it 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.
get_my_findsProducts the VIA network suggests for your owner, based on their Taste Card: title, seller, price in USDC, image URL, link and why it matched.Reads text others writeNo findings
Why it is in this group
- The name "get_my_finds" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
get_my_taste_cardRead your owner's VIA Taste Card: how it reads now and whether it is published.No findings
Why it is in this group
- The name "get_my_taste_card" says "get": a word for reading.
Description, as the server wrote it Read your owner's VIA Taste Card: how it reads now and whether it is published. Pass the action_token from VIA's message.
get_offering_schemaFetch the configurable option space for a per-order (configurable) product before requesting a quote, forwarded to the owning seller.No findings
Why it is in this group
- The name "get_offering_schema" says "get": a word for reading.
Description, as the server wrote it 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.
get_personal_shopperGet a VIA Personal Shopper for the calling Mind's owner.No findings
Why it is in this group
- The name "get_personal_shopper" says "get": a word for reading.
Description, as the server wrote it 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.
get_productFetch full detail for ONE listing before buying, from anywhere on the network, without leaving this connector.No findings
Why it is in this group
- The name "get_product" says "get": a word for reading.
Description, as the server wrote it 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.
get_quoteCheck a quote's status by quote_ref, forwarded to the owning seller.No findings
Why it is in this group
- The name "get_quote" says "get": a word for reading.
Description, as the server wrote it 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.
get_seller_productsDrill into ONE seller's catalogue to answer 'is X available at seller Y'.No findings
Why it is in this group
- The name "get_seller_products" says "get": a word for reading.
Description, as the server wrote it 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'.
get_shipping_quoteResolve a seller's shipping cost to a destination country before buying, without leaving this connector.No findings
Why it is in this group
- The name "get_shipping_quote" says "get": a word for reading.
Description, as the server wrote it 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.
get_store_cardRead 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…No findings
Why it is in this group
- The name "get_store_card" says "get": a word for reading.
Description, as the server wrote it 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.
get_store_statusCheck the review status of a store you registered with register_store.Reads text others writeNo findings
Why it is in this group
- The name "get_store_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it 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.
get_taste_cardRead 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.No findings
Why it is in this group
- The name "get_taste_card" says "get": a word for reading.
Description, as the server wrote it 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.
get_via_overviewShort overview of VIA Labs, the agentic-commerce platform: what it does, key entrypoints for buyers and sellers, where to onboard.No findings
Why it is in this group
- The name "get_via_overview" says "get": a word for reading.
Description, as the server wrote it Short overview of VIA Labs, the agentic-commerce platform: what it does, key entrypoints for buyers and sellers, where to onboard.
list_sellersList active sellers across the VIA network (VIA app + RRG + integrated platforms).No findings
Why it is in this group
- The name "list_sellers" says "list": a word for reading.
Description, as the server wrote it 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).
seller_mcp_urlReturn the per-seller MCP endpoint URL for a given seller slug, verified against the active seller index.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe name "seller_mcp_url" says "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Return the per-seller MCP endpoint URL for a given seller slug, verified against the active seller index.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 13
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://app.getvia.xyz/.well-known/oauth-protected-resource
- Authorization servers
- https://app.getvia.xyz
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 13 tools that change things (1 irreversible, 12 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.getvia.xyz/mcp: tools/list returned 33 tools to an anonymous client, including confirm_purchase (irreversible), claim_pass (write), claim_network_pass (write), buy_product (write), ask_sales_agent (write) and 8 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http via-network https://app.getvia.xyz/mcpclaude mcp add --transport http via-network https://app.getvia.xyz/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__via-network__list_sellers",
"mcp__via-network__find_seller",
"mcp__via-network__get_personal_shopper",
"mcp__via-network__get_product",
"mcp__via-network__get_shipping_quote",
"mcp__via-network__get_offering_schema",
"mcp__via-network__get_quote",
"mcp__via-network__get_download_challenge",
"mcp__via-network__get_download_links",
"mcp__via-network__get_buyer_preferences",
"mcp__via-network__get_buyer_briefs",
"mcp__via-network__find_buyers",
"mcp__via-network__get_seller_products",
"mcp__via-network__seller_mcp_url",
"mcp__via-network__get_via_overview",
"mcp__via-network__get_store_status",
"mcp__via-network__get_my_taste_card",
"mcp__via-network__get_my_finds",
"mcp__via-network__get_taste_card",
"mcp__via-network__get_store_card"
],
"ask": [
"mcp__via-network__claim_pass",
"mcp__via-network__claim_network_pass",
"mcp__via-network__buy_product",
"mcp__via-network__confirm_purchase",
"mcp__via-network__ask_sales_agent",
"mcp__via-network__request_quote",
"mcp__via-network__counter_quote",
"mcp__via-network__negotiate",
"mcp__via-network__accept_offer",
"mcp__via-network__submit_intent",
"mcp__via-network__register_store",
"mcp__via-network__import_preference_appraisal",
"mcp__via-network__update_taste_card"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as via-network. Review it before you use it.
Capability tags behind 5 rules
- mcp__via-network__buy_product outbound
- mcp__via-network__confirm_purchase outbound
- mcp__via-network__seller_mcp_url untrusted-input
- mcp__via-network__get_store_status untrusted-input
- mcp__via-network__get_my_finds untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/xyz.getvia.app/via-network/verify?hash=ec5cf00d10a31167deaf2ca8cbb61c9d71be39edd2caa285e6b6ac4a23c53e99" | jq -e '.changed == false'Pinned hash ec5cf00d10a3, from Nov 19, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/xyz.getvia.app/via-network/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/xyz.getvia.app/via-network)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
VIA Network: Agentic Commerce MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the VIA Network: Agentic Commerce MCP server safe?
- No scan can promise that. What its definitions show: 33 tools, 13 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the VIA Network: Agentic Commerce MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the VIA Network: Agentic Commerce MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: confirm_purchase.
What tools does the VIA Network: Agentic Commerce MCP server have?
- 33 tools: 1 irreversible, 12 write, 20 read. confirm_purchase, claim_pass, claim_network_pass, buy_product, ask_sales_agent, request_quote, counter_quote, negotiate and 25 more.
Does the VIA Network: Agentic Commerce MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the VIA Network: Agentic Commerce MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): buy_product and confirm_purchase.
Has the VIA Network: Agentic Commerce MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.