APPSIDE / MCP DIRECTORY

Robert Bell, musician

Connect to Robert Bell, musician: Design & Media, other authentication. See its latest connection check and available tools at https://robertbellmcp.netlify.app/mcp.

← All MCP servers

A work-in-progress experiment by Robert Bell, musician. Testing using a serverless resource-only MCP server to facilitate search and research MCP clients understanding a small business's…

Handshake passed

Endpoint
https://robertbellmcp.netlify.app/mcp
Category
Design & Media
Authentication
other
Maintainer
Robert Bell, musician
Last checked
2026-11-02 22:09 UTC

Add the badge to your README

Appside directory status

Verified means this server passed a live MCP handshake on 2026-11-02 22:09 UTC. The badge reflects the latest recorded check.

Markdown

[![Verified on Appside](https://appside.build/mcp-servers/robert-bell-musician/badge.svg)](https://appside.build/mcp-servers/robert-bell-musician/)

HTML

<a href="https://appside.build/mcp-servers/robert-bell-musician/"><img src="https://appside.build/mcp-servers/robert-bell-musician/badge.svg" alt="Verified on Appside"></a>

Connect with Claude Code

claude mcp add --transport http robert-bell-musician 'https://robertbellmcp.netlify.app/mcp'

Connect with Cursor

Paste into .cursor/mcp.json.

{
  "mcpServers": {
    "robert-bell-musician": {
      "url": "https://robertbellmcp.netlify.app/mcp"
    }
  }
}

Complete the provider’s authentication flow in your client. For API keys, follow the maintainer’s instructions; never place secrets in a public listing.

Tools (0)

    Submitted to modelcontextprotocol/servers (PR #1703) by kkgthb. Public submission attribution does not establish ownership. Appside independently checks connectivity.

    Your agent can submit and claim this for you

    {"name":"create_account","arguments":{"agent":"My assistant","purpose":"mcp-directory"}}

    How we check servers

    Each published entry passed a dated HTTPS Streamable HTTP check using the initialize-based MCP lifecycle (2024-11-05 through 2025-11-25): MCP initialize, followed by tools/list for open servers. For protected endpoints, a 401 response with an authentication challenge establishes reachability only. We never invoke tools. Failed checks stay in our source data and are excluded from the directory.

    Checks are point-in-time observations, not continuous uptime monitoring. An authentication challenge does not prove tools are available. Appside does not endorse or audit listed servers. Review the maintainer’s permissions and policies before connecting.

    What does the check verify?

    We send an MCP initialize request over HTTPS. Open servers must return a valid tools/list response. Protected servers may qualify with an authentication challenge. A listing is not an endorsement or a security audit.

    How can I update or remove a listing?

    Sign in to a free Appside account, claim the listing with a token on its server or maintainer domain, then edit or remove it. You can also request removal at privacy@appside.build.

    SEE IT YOURSELF

    Build your store
    before the first call.

    Try the live demo ↗Explore Studio
    LET’S TALK

    Book a demo

    Connect with Oded to arrange a walkthrough of Appside.

    Contact Oded on LinkedIn ↗