tokio-prompt-orchestrator — security grade SAFE, quality 64/100

Security audit verdict: SAFE · quality 64/100

No red flags found in any of the 11 categories — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →

by Mattbusel · MCP Server · ★ 57

Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h

🔒 Is tokio-prompt-orchestrator safe to install? View the security audit →

About tokio-prompt-orchestrator

tokio-prompt-orchestrator Production-grade, multi-core Tokio orchestration for LLM inference pipelines. Five-stage bounded-backpressure DAG with deduplication, circuit breakers, rate limiting, prompt injection/jailbreak detection, provider arbitrage (cheapest provider meeting your latency SLA), adaptive worker pool sizing, and an optional autonomous self-improving control loop. Supports Anthropic, OpenAI, llama.cpp, vLLM, and any custom backend. Exposes REST, WebSocket, SSE, MCP (Claude Desktop), Prometheus metrics, and OpenTelemetry distributed tracing.

agentasyncbackpressurecircuit-breakerdeduplicationllmllm-inferencemcpmodel-context-protocolmulti-agent

Quick Facts

Stars57
Forks5
LanguageRust
CategoryMCP Server
LicenseMIT
Quality Score63.7379725213552/100
Open Issues2
Last Updated2026-03-23
Created2025-10-07
Platformsmcp, rust
Est. Tokens~20012k

tokio-prompt-orchestrator alternative? Top 6 similar tools

Looking for a tokio-prompt-orchestrator alternative? If you're comparing tokio-prompt-orchestrator with other mcp server tools, these 6 projects are the closest alternatives on Agent Skills Hub — ranked by topic overlap, star count, and community traction.

  • omnicoreagent by omnirexflora-labs · ⭐ 246

    Open Python agent harness for production AI apps: tools, MCP, memory, workspace, telemetry, subagents, backgro

  • gopher-mcp by GopherSecurity · ⭐ 147

    C++ MCP SDK - build Model Context Protocol (MCP) servers and clients in C++ / CPP. Enterprise-grade security,

  • sub-agents-mcp by shinpr · ⭐ 98

    Define task-specific AI sub-agents in Markdown for any MCP-compatible tool.

  • hermes-memory-installer by mage0535 · ⭐ 195

    🧠 Production-grade memory sidecar for AI agents — gbrain + Hindsight + 3-tier recall. Agent-agnostic, battle-

  • captain-claw by kstevica · ⭐ 165

    Self-hosted framework for orchestrating fleets of specialist AI agents — ensemble reasoning and a full agentic

  • claude-code-open by kill136 · ⭐ 158

    Open source AI coding platform with Web IDE, multi-agent system, 37+ tools, MCP protocol. MIT licensed.

More MCP Server Tools

Explore other popular mcp server tools:

View all MCP Server tools →

Popular Rust Agent Tools

Frequently Asked Questions

What is tokio-prompt-orchestrator?

tokio-prompt-orchestrator is Multi-core, Tokio-native orchestration for LLM pipelines.. It is categorized as a MCP Server with 57 GitHub stars.

What programming language is tokio-prompt-orchestrator written in?

tokio-prompt-orchestrator is primarily written in Rust. It covers topics such as agent, async, backpressure.

How do I install or use tokio-prompt-orchestrator?

You can find installation instructions and usage details in the tokio-prompt-orchestrator GitHub repository at github.com/Mattbusel/tokio-prompt-orchestrator. The project has 57 stars and 5 forks, indicating an active community.

What license does tokio-prompt-orchestrator use?

tokio-prompt-orchestrator is released under the MIT license, making it free to use and modify according to the license terms.

What are the best alternatives to tokio-prompt-orchestrator?

The top alternatives to tokio-prompt-orchestrator on Agent Skills Hub include omnicoreagent, gopher-mcp, sub-agents-mcp. Each offers a different approach to the same problem space — compare them side-by-side by stars, quality score, and community activity.

How this security grade is produced

Grades come from a rule-based scan built on the SlowMist agent-security taxonomy, covering 11 red-flag categories including credential harvesting, data exfiltration, and curl | sh installers. It is a first-layer scan, not a manual audit — we say so rather than overstate it.

The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.

Sources & who's responsible:

View on GitHub → Browse MCP Server tools