When was npm:@khaoss85/orchestro last audited?

Last checked 2026-06-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

A-

npm:@khaoss85/orchestro

Item: npm:@khaoss85/orchestro
Rating: 90
Author: wmcp.sh

https://www.npmjs.com/package/@khaoss85/orchestro

90/100 · MCP Trust Grade · checked 1mo ago · MCP 2.1.0

Is the npm:@khaoss85/orchestro MCP server safe to use?

Independent trust grade A- (90/100). Static analysis of npm package @khaoss85/orchestro@2.1.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured. wmcp.sh continuously watches npm:@khaoss85/orchestro for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 30 tools · Database

orchestro

get_project_info

create_task

list_tasks

update_task

delete_task

get_task_context

get_execution_order

list_templates

list_patterns

list_learnings

render_template

get_relevant_knowledge

intelligent_decompose_story

save_story_decomposition

add_feedback

get_similar_learnings

get_top_patterns

+12 more tools

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 30 tool(s) detected in source

Security (OWASP MCP)30%90

no high-risk patterns in sampled source
scanned 6 source files

Maintenance / popularity20%75

last published ~8mo ago
1 published version

Tool hygiene15%95

✓ ships TypeScript types
6 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
14 weekly downloads

Findings

INFO Static analysis of npm package @khaoss85/orchestro@2.1.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:@khaoss85/orchestro on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@khaoss85/orchestro grade A-

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3A%40khaoss85%2Forchestro

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade A-](https://wmcp.sh/mcp/grade/npm%3A%40khaoss85%2Forchestro/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40khaoss85%2Forchestro)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3A%40khaoss85%2Forchestro"><img src="https://wmcp.sh/mcp/grade/npm%3A%40khaoss85%2Forchestro/badge.svg" alt="MCP Trust Grade A- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.