A

npm:@runcycles/mcp-server

https://www.npmjs.com/package/@runcycles/mcp-server
95/100 · MCP Trust Grade · checked 3h ago · MCP 0.2.4

What it offers — 9 tools · Developer Tools

cycles_reserve

Reserve budget before a costly operation (LLM call, tool invocation, external action). Returns a reservation_id to commit or release later. If decisio

cycles_commit

Commit actual usage after an operation completes. Always call this after cycles_reserve whether the operation succeeded or failed. Finalizes the budge

cycles_release

Release a reservation without committing. Use when an operation is cancelled, skipped, or fails before execution. Returns the released budget amount b

cycles_extend

Extend the TTL of an active reservation. Use as a heartbeat for long-running operations to prevent the reservation from expiring. Does not change the

cycles_decide

Lightweight preflight check \u2014 ask whether an action would be allowed without reserving budget. Does not create a reservation. Use at workflow sta

cycles_check_balance

Check current budget balance for a scope. Returns remaining, reserved, spent, allocated, and debt amounts. At least one subject filter (tenant, worksp

cycles_list_reservations

List reservations, optionally filtered by status (ACTIVE, COMMITTED, RELEASED, EXPIRED) or subject fields. Useful for debugging stuck reservations or

cycles_get_reservation

Get details of a specific reservation by ID. Returns status, subject, action, reserved amount, timestamps, and affected scopes. Useful for debugging a

cycles_create_event

Record a usage event directly without the reserve/commit lifecycle. Use for fire-and-forget metering of completed operations where pre-estimation is n

Spec / packaging20%100
Security (OWASP MCP)30%90
Maintenance / popularity20%100
Tool hygiene15%95
Transparency / provenance15%90

Findings

INFO Static analysis of npm package @runcycles/mcp-server@0.2.4 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:@runcycles/mcp-server 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:@runcycles/mcp-server grade A
Share on X Open card image

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.

MCP Trust Grade A · wmcp.sh
[![MCP Trust Grade A](https://wmcp.sh/mcp/grade/npm%3A%40runcycles%2Fmcp-server/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40runcycles%2Fmcp-server)
<a href="https://wmcp.sh/mcp/grade/npm%3A%40runcycles%2Fmcp-server"><img src="https://wmcp.sh/mcp/grade/npm%3A%40runcycles%2Fmcp-server/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.