The product MCP server, over one person's own CRM
Supported endpoint pinned to v1. Use /mcp to follow the latest available implementation. initialize, ping and tools/list answer without a credential: nothing in them is one person's data, and a 401 on the handshake reads as a dead server.
tools/call needs a bearer token. Without one it answers 401 with WWW-Authenticate: Bearer resource_metadata="..." naming the RFC 9728 document.
JSON-RPC batching is refused, per MCP 2025-06-18. The tool schemas come from tools/list, not from this document.
Request
- Base URL: https://youspot.com
- URL: https://youspot.com/mcp/v1
- Auth: one of:
- none
- OAuth 2 (authorization code, authorization URL https://youspot.com/oauth/authorize, token URL https://youspot.com/oauth/token, scopes: linkedin)
- HTTP bearer
Headers
A unique string, usually a UUID, naming this attempt. Repeating a request under the same key returns the first answer instead of writing again, for 24 hours. The same key with a different body is a 422. The answer carries Idempotency-Replayed. A key is scoped to the credential that sent it, so it only ever replays your own answer and never has to be unguessable.
Request body
Example request
{
"method": "initialize"
}Response
A JSON-RPC envelope.
Changes
No recorded changes to this operation across all 1 revision of this API.