β Claim or Update Your Listing
Maintainer of a listed remote MCP server? Three self-service ways to verify ownership and keep your listing accurate β no account required.
Method 1 β Publish a Server Card Recommended
Serve a standards-based MCP Server Card (SEP-1649/2127) at https://<your-domain>/.well-known/mcp.json. When the card is reachable on the same domain as your endpoint, we can auto-verify ownership and mark your listing Server Card β
. It must pass Check 5 of our OAuth debugger.
{
"$schema": "https://static.modelcontextprotocol.io/schemas/server-card/v1.json",
"name": "com.example/mcp",
"title": "Your Product MCP Server",
"description": "One-line description of what your remote MCP endpoint exposes.",
"version": "1.0.0",
"homepageUrl": "https://mcp.upstash.com",
"remotes": [
{
"type": "streamable-http",
"url": "https://mcp.upstash.com/mcp"
}
],
"authentication": {
"type": "oauth2"
},
"capabilities": {
"tools": true,
"resources": false,
"prompts": false
}
}Keep remotes[0].url identical to the endpoint we list and host the JSON on the endpoint's apex domain β that match is what proves ownership.
Method 2 β Embed the Live Status Badge
Add our real-time status badge to your official repository README, then send us the repo link β a human review confirms the listing is maintained by the vendor.
[](https://remotemcp.net/servers/upstash)
Method 3 β Submit an Update Request
Report a new endpoint URL, an OAuth configuration change, or an MCP Apps / Server Card capability in ~10 seconds. The claim form pre-fills everything we already know about your listing β you only edit what changed. Prefer email? Write to easytoreach365@gmail.com from your official domain.
Verified claims keep your listing's endpoint, auth metadata and capability flags accurate β which directly affects how confidently clients connect to you.