
agenvoy
UNCLAIMEDTOOL USE AND MCPAGENT FRAMEWORKSCODE EXECUTION SANDBOXES
agenvoy — Self-hosted 24/7 personal AI agent that runs on your own machine — memory, schedules, tools and credentials stay local. Single Go binary with MCP. Listed under Tool use and MCP in the Orchestration / Agents layer. 7 of 14 comparison attributes are recorded, each with the page it was read from.
Private, local AI agent and personal AI assistant for AI automation: runs 24/7, builds its own AI tools, and works with Claude Code, Codex, Ollama and MCP.
4 OF 4 SIGNALS HELD
What it runs on, and what runs on it
0 cited edgesComputed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.
No edges on record for agenvoy.
Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.
Submit a documented integration →From agenvoy? No claim is needed for this: a link to your docs that names what agenvoy runs on is enough.
Open-source signals
A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE
Price
We hold no price for this product.
This is open-source software: you can run it yourself and the licence costs nothing. If the project also sells a hosted service, we do not yet hold the page it prices it on. If that changes — or if you publish /.well-known/pricing.json — it appears here with a capture date.
How we read prices →What its categories ask
7 answered · 7 unanswered14 questions declared by Tool use and MCP and Agent frameworks and Code execution sandboxes. Most rows across the directory read like these.
“2026-08-05 pi indexed harness recovery queries 2026-08-05 pi validate harness recovery record logs 2026-08-05 pi harness v2 jsonl backend 2026-08-06 pi atomic writes + torn-tail truncation 2026-08-14 pi AgentHarness R3 generation recovery 2026-08-14 pi AgentHarness R4 tool execution”2026-10-13
“A plain command with no shell metacharacter (`\|`, `&&`, `>`, `*`, `~`) is called directly, never wrapped; pipes, redirects and globbing need an explicit `['sh','-c','...']`, whose script is parsed and validated command-by-command — every binary must be a **bare command name**, and anything on `deni”2026-10-06
“Share your tools with Claude Code or Codex | [MCP Server](/docs/mcp-server)”2026-09-29
A ROW WITH NO ANSWER IS NOT A ROW WITH A “NO” · A VENDOR MAY ANSWER A BLANK ONE, MARKED VENDOR CLAIMED WITH ITS SOURCE · A DOCUMENTED VALUE IS DISPUTED, NOT OVERWRITTEN, AND STAYS VISIBLE WHILE WE RE-READ THE SOURCE
Practitioner reviews
Nobody has written one yet.
A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.
NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER
Also in this category
198 products in Tool use and MCP. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.
Frequently asked
Is agenvoy open source?
Does agenvoy offer MCP server?
Does agenvoy offer open source?
What does a blank mean on the agenvoy page?
Where do the agenvoy figures come from?
Can agenvoy change what this page says?
Something here is wrong — how do I fix it?
Is this listing run by agenvoy?
Cite this page
A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.
infratoapp, “agenvoy — Tool use and MCP”, read 13 October 2026. Cold start: 1 s as published at agenvoy.com. https://www.infratoapp.com/products/agenvoy
What agenvoy can and cannot change here
Claiming the organisation lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.