An OAuth Server for the music-streaming-mcp-server
{
"mcpServers": {
"oauth-music-streaming-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An OAuth Server for the music-streaming-mcp-server
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 175 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Search, evaluate, and compare 17,000+ MCP servers — each scored on security, maintenance, and efficiency.
Model Context Protocol (MCP) Server to connect your AI with any MediaWiki
MCP server for Apple Developer Documentation - Search iOS/macOS/SwiftUI/UIKit docs, WWDC videos, Swift/Objective-C APIs & code examples in Claude, Cursor & AI assistants
AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL.
MCP Security Weekly
Get CVE alerts and security updates for Oauth Music Streaming Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Secure OAuth 2.0 and MCP-compliant authorization server bridging Spotify’s Web API with Model Context Protocol (MCP) tool servers — built for scale, observability, and developer experience.
This repository implements a custom OAuth 2.0 Authorization Server that bridges authentication between:
Built with ASP.NET Core 8, it delivers a secure and extensible authentication layer using:
Implements Spotify’s Authorization Code with PKCE flow for secure public-client authentication.
Flow Summary:
/authorize with code_challenge=S256code → /spotify-callback/token)
This ensures that no secrets are exposed client-side and that token exchanges are verified using code_verifier and S256.
var spotifyTokenRequest = new SpotifyTokenRequest
{
GrantType = "authorization_code",
Code = code,
RedirectUri = redirectUri,
CodeVerifier = verifier
};
Enables runtime client onboarding without manual setup.
Example Request:
POST /register
Content-Type: application/json
{
"client_name": "my-mcp-client",
"redirect_uris": ["https://localhost:3000/callback"],
"grant_types": ["authorization_code"],
"response_types": ["code"],
"scope": "mcp:tools openid profile email"
}
Response:
{
"client_id": "abc123",
"registration_access_token": "securetoken",
"registration_client_uri": "https://localhost:8080/register/abc123"
}
Dynamic registration allows multi-tenant tool ecosystems to register securely at runtime — ideal for automated AI agent provisioning and decentralized MCP tool discovery.
📘 Reference: RFC 7591 §3.3
Access tokens are minted as RSA-signed JWTs using a PEM private key, encapsulated by t