io.github.withpica/pica
NPM · @WITHPICA/MCP-SERVER · 2 COMPONENTS
manage your music catalog through conversation — works, recordings, credits, agreements, royalties
Available components
Last scanned (4 hours ago)
Scores higher than 65% of npm servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 670 tokens (~134/item across 5 items; 3 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Stability: 0.97 → pass security
- Dependency health: unverified → 0.84 ▲ functional
- 4 Nov 26 +5
- Known CVEs: pass → unverified ▼ security
- Stability: 0.93 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: pass → partial ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: 0.84 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Dependency health: 0.84 → partial functional
- Package version: 2.117.0 → 2.119.0 functional
- Package version: 2.117.0 → 2.118.0 functional
- 3 Nov 26 −1
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.93 functional
- Package version: 2.115.0 → 2.117.0 functional
- Package version: 2.115.0 → 2.116.0 functional
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 2.113.0 → 2.115.0 functional
- Package version: 2.113.0 → 2.114.0 functional
- 1 Nov 26 +5
- CVE-2026-118663 no longer affects this package ▲ security
- CVE-2026-111767 no longer affects this package ▲ security
- CVE-2026-104850 no longer affects this package ▲ security
- CVE-2026-111768 no longer affects this package ▲ security
- CVE-2026-111771 no longer affects this package ▲ security
- CVE-2026-111769 no longer affects this package ▲ security
- GHSA-f897-62hf-6gxq no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Package version: 2.95.2 → 2.113.0 functional
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@withpica/mcp-server@2.119.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| No linked repository | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pica_sign_in ~50
sign in to PICA with your email — sends a magic link to your inbox. use this to connect your music catalog. no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | your email address |
No output schema declared.
No examples provided.
pica_sign_out ~21
sign out of PICA — clears your saved credentials
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pica_signup_start ~357
[settings] Sign up for withPICA from inside the agent, without leaving the chat. Use this when the user wants to create a new withPICA account / catalog and you're talking to them through an unauthenticated MCP connection (stdio without an API key, or HTTP without a Bearer token). The tool mints a single-use signup link valid for 15 minutes — surface the URL to the user as a clickable resource_link. The link opens a page that verifies their email by magic-link, creates their organisation, starts their free runway (a non-expiring usage allowance — no day-count trial), and (for stdio) shows a connection key to paste into Claude Desktop's MCP config or (for HTTP) resumes the OAuth flow. For existing users, prefer pica_sign_in.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email address. The signup link is sent to this inbox; the user clicks it to verify ownership before any account is created. Required. | |
| org_name | string | – | Optional human name for the user's catalog/organisation. Defaults to '<email-localpart>'s catalog' if omitted. Editable later in settings. |
| purpose | string | – | Optional free-text — what the user is trying to do with PICA, captured for product analytics (e.g. 'managing my first album credits', 'exporting royalty statements'). Not surfaced to the user. |
| referral_code | string | – | Optional referral code from an existing withPICA user who invited this person (their `?ref=` code, shown in Settings → invite & earn). When supplied, the signup is attributed to that referrer and bot… |
No output schema declared.
No examples provided.
How do I install the io.github.withpica/pica MCP server?
io.github.withpica/pica runs locally as an npm package, launched with npx -y @withpica/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @withpica/mcp-server
claude mcp add withpica-pica -- npx -y @withpica/mcp-server
What is the io.github.withpica/pica MCP server?
io.github.withpica/pica is an MCP server listed in the public MCP registry as io.github.withpica/pica. manage your music catalog through conversation, works, recordings, credits, agreements, royalties. This page covers its npm package (@withpica/mcp-server).
Is the io.github.withpica/pica MCP server safe to use?
io.github.withpica/pica scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.withpica/pica MCP server expose?
io.github.withpica/pica exposes 3 tools: pica_sign_in, pica_sign_out, pica_signup_start. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.
Is the io.github.withpica/pica MCP server still maintained?
io.github.withpica/pica is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.withpica/pica MCP server under?
io.github.withpica/pica declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.