Meting-Agent
Meting-Agent wraps the metowolf/Meting multi-platform music API into a unified interface and provides it as both an MCP server (via @eldment/meting-agent) and a “Skill” release (via skills/meting-agent). It exposes operations like searching tracks/albums/artists, fetching song/album/artist/playlist details, retrieving playable URLs, lyrics, and cover images for platforms such as NetEase, QQ Music, KuGou, and Kuwo.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security details (TLS/auth/secret handling/scope) are not provided in the supplied README content, so scores are based on uncertainty. As a music-metadata aggregator, it may rely on upstream/third-party access methods that could involve cookies/headers/config; ensure secrets are managed via environment variables and avoid logging request headers. Treat provider responses as untrusted data; do not blindly execute/interpret lyrics/metadata content.
⚡ Reliability
Best When
You want a unified music-data toolset for AI agents (MCP/skills) and can tolerate provider/API volatility typical of scraped/third-party music endpoints.
Avoid When
You require strict guarantees about uptime, backward compatibility, or transparent auth/rate-limit policies for the upstream music providers.
Use Cases
- • AI agents that need to search and retrieve music metadata across multiple Chinese music platforms
- • Lyrics/cover retrieval for chatbots or media apps
- • Building LLM toolchains that can call music search and fetch functions via MCP
- • Rapid prototyping of music-related agent skills (search, lookup, URL, lyrics)
Not For
- • High-assurance/regulated contexts requiring audited security and compliance guarantees
- • Use cases needing a formal, stable OpenAPI/SDK contract (not evidenced in the provided content)
- • Direct end-user playback services that require a dedicated licensing/compliance review of provider terms
Interface
Authentication
No authentication details are present in the provided README content; auth requirements (if any) likely depend on the MCP/Skill deployment configuration and underlying meting provider access patterns.
Pricing
No pricing information provided in the supplied content (MIT repo; MCP/Skill packages may incur hosting costs only).
Agent Metadata
Known Gotchas
- ⚠ Music-provider endpoints can be rate-limited or change without notice; agent retries may require backoff and graceful failure handling.
- ⚠ Because the provided content doesn’t specify error formats, tool-level failure modes should be tested in your environment before production use.
- ⚠ Different platforms may return different fields/limits for search and detail endpoints; agents should handle missing/partial data.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Meting-Agent.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.