startupregistry
Record SR-00016·First registered 24 Aug 2026

virtuprobe.studio

VirtuProbe Studio | The request manager that chains every protocol

Recorded wording

120 lines, exactly as the page had them.

Snapshot24 Aug 2026, 06:13 UTC
  1. 01VirtuProbe Studio | The request manager that chains every protocol
  2. 02We're on Microlaunch through the end of August. Come and back VirtuProbe with an upvote.
  3. 03Upvote on Microlaunch →
  4. 04v2.3.1 is out · UI performance improvements
  5. 05v2.3.1 · macOS · Linux · Windows
  6. 06The request manager that chains every protocol
  7. 07and integrates with your agents.
  8. 08Started by one engineer (20+ years from core-banking to big data) who hit the limits of every testing tool and built the one that wasn't there, now built with a small team. The story →
  9. 09HTTP · SMTP · IMAP · LDAP · DNS · SMB · Kerberos · SpamAssassin · MySQL · MongoDB · PostgreSQL
  10. 10No cloud · runs where your targets are
  11. 11VirtuProbe Studio v2.3.1
  12. 12More videos on YouTube
  13. 13Bring your whole collection and you're working in under a minute.
  14. 14import OpenAPI · Postman · Bruno · HAR · .http · Insomnia · cURL
  15. 15Agents work in the same workspace you do.
  16. 16VirtuProbe runs an MCP server, so an agent can build and run tests in your workspace instead of improvising its own. What it makes is an ordinary chain in an ordinary bundle. You can open it, change it, rerun it, and it is still there tomorrow.
  17. 17An agent connects over MCP.
  18. 18Those tools call the same services the interface calls. No second implementation, and no separate permission model.
  19. 19An agent inherits your tier. There is no separate agent licence.
  20. 20You decide what it may touch.
  21. 21A new agent can read the workspace, but it cannot change or run anything until you approve it, and approving is a choice of which projects it may reach.
  22. 22Every write and every run resolves its target back to the projects that own it, and is refused outside the grant. You can revoke an agent while it is working.
  23. 23Reading is free. Writing and running need your consent.
  24. 24Its runs appear while they happen.
  25. 25Connected agents are listed with the runs they start, step by step as they execute. MCP over HTTP holds no connection open, so connected means an agent sent a request recently rather than that a socket is live.
  26. 26Attempts that were refused appear too, with the reason they were refused, so a missing grant or an unlicensed protocol is never a silent failure.
  27. 27The same view you get from a run you started yourself.
  28. 28Open what it is working on.
  29. 29A failed step is a link. Clicking it opens that chain at that step in the editor, with the same tools you would have if you had written it yourself.
  30. 30This does not interrupt the agent. It hands you the artefact while it is still being worked on.
  31. 31Nothing an agent makes is a second class object.
  32. 32Hand over a capability, not the workspace.
  33. 33A skill publishes a chain or a script under a fixed contract: typed inputs, declared outputs, one pinned environment. An input marked secret carries the name of a credential binding, never a value.
  34. 34The environment cannot be passed in, because choosing it is choosing what a stored credential gets pointed at. Point at a chain you already have and the contract is derived for you to review.
  35. 35Arguments in. Never secrets.
  36. 36Every run, on a stream.
  37. 37Runs are published as Server-Sent Events, whether you started them, a schedule did, or an agent did. Filter to agent-driven runs, to a single chain, or to failures only.
  38. 38Not gated on any tier. Watching what your own instance is doing carries nothing the run history does not already hold.
  39. 39Wire it into whatever you already watch.
  40. 40A quick tour of the app
  41. 41You can see the method, the URL, the headers, the body and the response at the same time. Variables resolve when you send, so a secret never has to sit in the file, and what comes back is the status, the latency and the raw bytes.
  42. 42Drop probes into a sequence and pass data between steps with {{variables}} . Branch on a response, loop over a list, fan out in parallel. HTTP → IMAP → LDAP in a single artefact you can replay in CI.
  43. 43Every scheme sits behind one picker, and the probe stores only which credential to use. The panel shows you which one resolved and where it came from before you send.
  44. 44The query and the variables get an editor each, and they serialize into the request body and come back unchanged. After that you can chain it, script it or fuzz it like any other HTTP call.
  45. 45Drop in the CA cert, point your client at :1080 , watch every flow land in the table. Filter by host, status class, method. Promote any line to a saved probe and it's part of your chain.
  46. 46Service virtualization
  47. 47Rules are evaluated top to bottom and the first match wins, so the order is the logic. A rule that matches answers from here and the request never leaves your machine.
  48. 48A script is JavaScript or Groovy, chosen per script, and a new one starts in JavaScript. The editor highlights, completes and checks as you type, and the script drives probes through vp.send(…) , then asserts on what comes back.
  49. 49An agent connected over MCP shows up here with the runs it starts, step by step as they happen. You approve which projects it can reach before it can change or run anything, and you can block it while it is working.
  50. 50Three jobs, one workbench
  51. 51Every protocol you test, in one place
  52. 52Iterate over a list, branch on a JavaScript or Groovy condition, fan out in parallel, or call a sub-chain. Mix protocols freely: fire an HTTP call, read the resulting email over IMAP, look the user up in LDAP, all in one runnable artefact.
  53. 53End-to-end flows you can run in CI.
  54. 54A signup flow touches HTTP, SMTP, IMAP and LDAP. You build it once as a chain, and it runs the same way on your machine and in CI.
  55. 55Cross-protocol assertions Assert that the API call produced a verification email carrying the right token, inside a time limit you set.
  56. 56Iterators & fixtures Drive a chain from a CSV, a vault, or another probe's response.
  57. 57MCP client The HTTP probe speaks Model Context Protocol, so it can call an MCP server, thread the session through a chain, and assert on the tools that server exposes.
  58. 58Reproducible artefacts A chain exports as a single file you can commit next to the code it tests.
  59. 59Mail & identity infra
  60. 60Mail, directory and identity protocols in one place.

Showing the first 60 of 120 recorded lines · Lines under 20 characters are not recorded: too short to prove anything

Register entry

ReferenceSR-00016
Entryunclaimed
First registered24 Aug 2026
Snapshot24 Aug 2026
Domain verifiednot yet
Watchnone
Last sweep24 Aug 2026
Matches found0

Sweep

Find out who else is using your wording.

We search the open web for your exact lines, read every page we find, and show you what overlaps. It takes a minute or two and you watch it happen.

The first sweep on a record is free.

See the whole register

Sweep history

24 Aug 2026, 06:13 UTC18 pages read0 matchesOpen

Unclaimed entry

This record was built from the public page, not by its founder.

Nothing here is invented: the wording is what the page said on the date shown, and there are no numbers we were not given. If it is your domain you can take it over, and if you would rather it were not here at all, say so and it comes down within 24 hours.

virtuprobe.studio · SR-00016 — startupregistry