audius-test-suite

Run parallel read-only health checks across Audius MCP server tools.

5|2|Updated Feb 1, 2025
One-click install
npx skills add https://github.com/glassBead-tc/audius-mcp-atris --skill audius-test-suite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audius-test-suite
Source: https://github.com/glassBead-tc/audius-mcp-atris/tree/main/.claude/skills/audius-test-suite
Command: npx skills add https://github.com/glassBead-tc/audius-mcp-atris --skill audius-test-suite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Test all tools and endpoints of the Audius MCP server in parallel using subagents to verify server health and tool readiness.

Core Features & Use Cases

  • Run smoke-style, read-only checks across mcp__audius-mcp__search, mcp__audius-mcp__execute, mcp__audius-mcp__subgraph, and mcp__audius-mcp__play to validate availability and responses.
  • Orchestrate 4 subagents in parallel to produce per-tool PASS/FAIL reports and a consolidated summary.
  • Use for routine health checks, end-to-end readiness validation, and API responsiveness verification against live Audius endpoints.

Quick Start

Run the test suite against a live Audius MCP server to perform parallel, read-only tool health checks.

Frequently Asked Questions about audius-test-suite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run read-only health checks for an Audius MCP server?

Read-only health checks for an Audius MCP server are automated by spawning parallel subagents that exercise each MCP tool. This validates server health, endpoint availability, and tool responses against live Audius API endpoints.

What is the best way to test MCP tools in parallel without writing data?

Testing MCP tools in parallel without writing data is achieved by orchestrating four subagents that perform read-only checks across search, execute, subgraph, and play tools. This enforces read-only interactions and reports per-tool PASS or FAIL results.

Can I validate Audius endpoint availability using subagents?

Audius endpoint availability can be validated using subagents by executing real MCP tool calls against the live server. The subagents perform smoke-style checks across the Audius API and The Graph to verify responsiveness and readiness.

Does the Audius MCP test suite require a live server connection?

The Audius MCP test suite requires a live server connection because it relies on the live Audius API and The Graph to execute real MCP tool calls. It automates end-to-end readiness validation against these active endpoints.

How do I get per-tool PASS or FAIL reports for Audius MCP tools?

Per-tool PASS or FAIL reports for Audius MCP tools are generated by spawning parallel subagents that exercise each tool individually. The subagents produce a consolidated summary of availability and end-to-end behavior results.

What are the limitations of using parallel subagents for MCP server testing?

Limitations of using parallel subagents for MCP server testing include strict read-only interaction enforcement and a dependency on live Audius API and The Graph availability. The scope is restricted to health checks and tool readiness validation without write capabilities.