tiny-runtime — agent batch and progress tools by AVRG3 runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 23 Sep 2026.
Resumable API pagination, repeated-failure detection and tool-progress cache hints for AI agents
We read the source, 23 min ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const candidates = rel.startsWith("/") ? [path.join(dir, rel), rel] : [path.resolve(dir, rel)];
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Portable signed records for agent, API, MCP, and cross-runtime interactions.
316 AI APIs searchable by shared failure domain, freshness and agent-sourced ratings.
Multi-agent observability: cascade failure detection, heartbeats, and forensic replay
Real-time semantic security for AI coding agents and MCP tools
Local-first, source-cited memory for AI agents with proposal review, failure memory, and MCP tools.
Market intelligence for AI agents. Real-time data, cross-market analysis, and regime detection.
Solar, weatherization, EV charging, battery and heat-pump decision tools for AI agents.
Runtime verification for agent tool calls: Ed25519 signed receipts, fail-closed RCE/SSRF checks.
Answers built from our own checks of this server.