VIA seller MCP for Dienastie. Buyers: list_products, get_product, get_shipping_quote, buy_product, ask_sales_agent, request_quote. PURCHASES EXECUTE ON VIA. To buy, call buy_product here: it returns a USDC (x402) payment requirement that settles on VIA on Base, agent-to-agent, with no checkout on the seller's own website. Listings carry a source_url for reference and provenance ONLY; do NOT send the buyer to that external site to transact, and do not present it as a buy link. The whole point of VIA is that the deal closes here. STORE OWNER: if you are the agent that controls this store's agent wallet, you can manage its catalogue (add and publish products) agent-to-agent, with no web dashboard and no password. Call get_owner_management_info to get the management endpoint and the wallet-signature steps.
9 verified, 0 failed, 0 observed risk, 1 not checked, on 22 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
No x402 catalogue entry we hold names an address this server takes payment at, so we cannot attribute any income to it. That is a gap in what we can attribute, not evidence that it earns nothing.
15 tools on the last day the list was read, fingerprint 9bf405021ba44833e56.
Ask Dienastie's Sales Agent a question. The agent answers in the seller's voice using its locked-in memories (events, promotions, policies, stock notes). Pass an optional 'contact' string (email, telegram handle, Buying Agent MCP URL, or whatever you accept) so the seller can reach back if a follow-up needs a human touch.
| Name | Type | Required | Description |
|---|---|---|---|
| question | string | yes | Free-form buyer question |
| contact | string | no | Optional reach-back identifier for the buyer or their agent so the seller can follow up. Examples: "buyer@example.com", "@buyerhandle", "https://buyer.example/agent/mcp". |
1 agent registrations name this server. A registration is a claim by whoever wrote it, which is why the server itself is asked.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 4 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-22 | Answered | 14 | hourly runs |
| 2026-11-21 | Some runs failed | 23 | hourly runs |
| 2026-11-20 | Some runs failed | 24 | hourly runs |
| 2026-11-19 | Answered | 23 | hourly runs |
| 2026-11-18 | Some runs failed | 24 | hourly runs |
| 2026-11-17 | Answered | 23 | hourly runs |
| 2026-11-16 | Answered | 24 | hourly runs |
| 2026-11-15 | Answered | 23 | hourly runs |
| 2026-11-14 | Some runs failed | 24 | hourly runs |
| 2026-11-13 | Answered | 23 | hourly runs |
| 2026-11-12 | Answered | 23 | hourly runs |
| 2026-11-11 | Answered | 23 | hourly runs |
| 2026-11-10 | Answered | 24 | hourly runs |
| 2026-11-09 | Some runs failed | 23 | hourly runs |
| 2026-11-08 | Answered | 24 | hourly runs |
| 2026-11-07 | Answered | 18 | hourly runs |
| 2026-11-06 | Answered | 15 | hourly runs |
| 2026-11-05 | Answered | 20 | hourly runs |
| 2026-11-04 | Answered | 14 | hourly runs |
| 2026-11-03 | Answered | 0 | daily probe |
| 2026-11-02 | Answered | 0 | daily probe |
| 2026-11-01 | Answered | 0 | daily probe |
| 2026-10-31 | Answered | 0 | daily probe |
| 2026-10-30 | Answered | 0 | daily probe |
| 2026-10-29 | Answered | 0 | daily probe |
| 2026-10-28 | Answered | 0 | daily probe |
| 2026-10-27 | Answered | 0 | daily probe |
| 2026-10-26 | Answered | 0 | daily probe |
| 2026-10-25 | Answered | 0 | daily probe |
| 2026-10-24 | Answered | 0 | daily probe |
| 2026-10-23 | Answered | 0 | daily probe |
| 2026-10-22 | Answered | 0 | daily probe |
| 2026-10-21 | Answered | 0 | daily probe |
| 2026-10-20 | Answered | 0 | daily probe |
| 2026-10-19 | No answer | 0 | daily probe |
| 2026-10-18 | Answered | 0 | daily probe |
| 2026-10-17 | Answered | 0 | daily probe |
| 2026-10-16 | Answered | 0 | daily probe |
| 2026-10-15 | No answer | 0 | daily probe |
| 2026-10-14 | Answered | 0 | daily probe |
| 2026-10-13 | Answered | 0 | daily probe |
| 2026-10-12 | Answered | 0 | daily probe |
| 2026-10-11 | Answered | 0 | daily probe |
| 2026-10-10 | Answered | 0 | daily probe |
| 2026-10-07 | Answered | 0 | daily probe |
| 2026-10-06 | Answered | 0 | daily probe |
| 2026-10-04 | Answered | 0 | daily probe |
| 2026-10-03 | Answered | 0 | daily probe |
| 2026-10-02 | Answered | 0 | daily probe |
| 2026-10-01 | Answered | 0 | daily probe |
| 2026-09-30 | Answered | 0 | daily probe |
| 2026-09-29 | Answered | 0 | daily probe |
| 2026-09-28 | Answered | 0 | daily probe |
| 2026-09-27 | Answered | 0 | daily probe |
| 2026-09-26 | Answered | 0 | daily probe |
| 2026-09-25 | Answered | 0 | daily probe |
| 2026-09-24 | Answered | 0 | daily probe |
| 2026-09-23 | Answered | 0 | daily probe |
| 2026-09-22 | Answered | 0 | daily probe |
| 2026-09-21 | Answered | 0 | daily probe |
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-22 | 283 | 346 | 14 |
| 2026-11-21 | 296 | 330 | 22 |
| 2026-11-20 | 301 | 349 | 23 |
| 2026-11-19 | 296 | 391 | 23 |
| 2026-11-18 | 297 | 368 | 23 |
| 2026-11-17 | 288 | 348 | 23 |
| 2026-11-16 | 303 | 380 | 24 |
| 2026-11-15 | 283 | 338 | 23 |
| 2026-11-14 | 284 | 340 | 23 |
| 2026-11-13 | 277 | 346 | 23 |
| 2026-11-12 | 300 | 339 | 23 |
| 2026-11-11 | 294 | 344 | 23 |
| 2026-11-10 | 293 | 385 | 24 |
| 2026-11-09 | 291 | 345 | 22 |
| 2026-11-08 | 283 | 339 | 24 |
| 2026-11-07 | 280 | 371 | 18 |
| 2026-11-06 | 315 | 434 | 15 |
| 2026-11-05 | 274 | 328 | 20 |
| 2026-11-04 | 293 | 372 | 14 |
Each hour: the median p50 of that hour’s runs, times in UTC; the shaded last hour is not complete. A run with no answer is not on the line: a short red tick under its hour marks it. Latest run 22 November 2026, 13:38 UTC: 5 of 5 requests answered, p50 317 ms, p95 346 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-22 14:00 (now) | — | 0 | 0 |
| 2026-11-22 13:00 | 317 | 1 | 0 |
| 2026-11-22 12:00 | 316 | 1 | 0 |
| 2026-11-22 11:00 | 294 | 1 | 0 |
| 2026-11-22 10:00 | 281 | 1 | 0 |
| 2026-11-22 09:00 | 309 | 1 | 0 |
| 2026-11-22 08:00 | 295 | 1 | 0 |
| 2026-11-22 07:00 | 273 | 1 | 0 |
| 2026-11-22 06:00 | 289 | 1 | 0 |
| 2026-11-22 05:00 | 271 | 1 | 0 |
| 2026-11-22 04:00 | 383 | 1 | 0 |
| 2026-11-22 03:00 | 266 | 1 | 0 |
| 2026-11-22 02:00 | 283 | 1 | 0 |
| 2026-11-22 01:00 | 270 | 1 | 0 |
| 2026-11-22 00:00 | 270 | 1 | 0 |
| 2026-11-21 23:00 | 277 | 1 | 0 |
| 2026-11-21 22:00 | 292 | 1 | 0 |
| 2026-11-21 21:00 | 304 | 1 | 0 |
| 2026-11-21 20:00 | 295 | 1 | 0 |
| 2026-11-21 19:00 | 290 | 1 | 0 |
| 2026-11-21 18:00 | 284 | 1 | 0 |
| 2026-11-21 17:00 | 344 | 1 | 0 |
| 2026-11-21 16:00 | 382 | 1 | 0 |
| 2026-11-21 15:00 | — | 1 | 1 |