diggercamp
REMOTE · MCP.DIGGERCAMP.COM · SCANNED SEP 25
Find independent music by how it sounds: similar tracks and playlists from a track link.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 951 tokens (~158/item across 6 items; 6 tools + 0 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the diggercamp MCP server?
diggercamp is a hosted endpoint at https://mcp.diggercamp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.diggercamp.com
claude mcp add --transport http com-diggercamp-music-similarity 'https://mcp.diggercamp.com/mcp'
{
"mcpServers": {
"com-diggercamp-music-similarity": {
"url": "https://mcp.diggercamp.com/mcp"
}
}
} {
"servers": {
"com-diggercamp-music-similarity": {
"type": "http",
"url": "https://mcp.diggercamp.com/mcp"
}
}
} [mcp_servers.com-diggercamp-music-similarity] url = "https://mcp.diggercamp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-diggercamp-music-similarity": {
"type": "remote",
"url": "https://mcp.diggercamp.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-diggercamp-music-similarity --url 'https://mcp.diggercamp.com/mcp' --transport streamable-http
mcp_servers:
com-diggercamp-music-similarity:
url: "https://mcp.diggercamp.com/mcp" {
"McpServers": {
"com-diggercamp-music-similarity": {
"Transport": "http",
"Url": "https://mcp.diggercamp.com/mcp"
}
}
} assistant mcp add com-diggercamp-music-similarity -t streamable-http -u 'https://mcp.diggercamp.com/mcp'
{
"mcpServers": {
"com-diggercamp-music-similarity": {
"type": "http",
"url": "https://mcp.diggercamp.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Probed https://mcp.diggercamp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=diggercamp.com | CN=YE2,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 67d3d10d94d78efd9125cff497d8251d958 |
| SANs: *.diggercamp.com, diggercamp.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.diggercamp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| diggercamp.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.diggercamp.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.diggercamp.com/mcp | Inconclusive | 406 |
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 →
deep_match ~42
Deep Match: technical match by rhythm, timbre and key — great for building DJ sets. Requires a Pro or Studio plan.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
find_similar ~41
Find sonically similar tracks to a song (closest by sound). Paste a Bandcamp, YouTube or SoundCloud link.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_playlist ~171
Generate and SAVE a playlist to the user's diggercamp account. It starts from a seed track and develops the set from there (energy and genre flow), optionally ending on a chosen track. Requires the user to be signed in to diggercamp. - url: seed track link (Bandcamp / YouTube / SoundCloud) — the playlist starts here. - n: number of tracks, 5 to 30 (default 15). - end_url: optional link of the track to END on. - vibe: optional one of warm_up, afterhours, yoga, focus, sunset (shapes the energy curve).
| Name | Type | Req | Description |
|---|---|---|---|
| end_url | string | – | – |
| n | integer | – | – |
| url | string | yes | – |
| vibe | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
inspire_me ~86
Discovery: pick a starting track and show similar tracks. For signed-in users with search history the pick is personalised on their recent digs; spread controls how far to roam: familiar (right next to their digs), fresh (close relatives, default), adventurous (two hops out, same lineage but unexpected), random (the whole crate).
| Name | Type | Req | Description |
|---|---|---|---|
| spread | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
playlist_match ~58
Find tracks that fit a SET of 2-8 tracks together (their combined sound / centroid), not similarity to a single seed. Pass 2-8 Bandcamp/YouTube/SoundCloud links.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
surprise_me ~37
Surprise: sonically related tracks with wider variety / less obvious picks. Requires a Pro or Studio plan.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the diggercamp MCP server?
diggercamp is an MCP server listed in the public MCP registry as com.diggercamp/music-similarity. Find independent music by how it sounds: similar tracks and playlists from a track link. This page covers its hosted endpoint (https://mcp.diggercamp.com/mcp).
Is the diggercamp MCP server safe to use?
diggercamp scores 76 out of 100 on VerifyMCP. 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 diggercamp MCP server expose?
diggercamp exposes 6 tools: find_similar, deep_match, surprise_me, playlist_match, inspire_me, generate_playlist. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.
Does the diggercamp MCP server require authentication?
No. We connected to diggercamp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the diggercamp MCP server still maintained?
diggercamp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.