RMCP.DEV
← yetty.ai

INDIVIDUAL MCP TOOL

yetty_login_status

Check an email sign-in: pending (owner has not clicked yet) -> approved (returns api_key ONCE + reconnect instructions).

yetty.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.yetty.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for yetty_login_status and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name, description or schema mentions credentials.
  • A tool name or description suggests sending messages.

Parent server

yetty.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.yetty]
url = "https://mcp.yetty.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "yetty": {
      "type": "http",
      "url": "https://mcp.yetty.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: yetty
Remote MCP URL: https://mcp.yetty.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "yetty": {
      "url": "https://mcp.yetty.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "yetty": {
      "type": "http",
      "url": "https://mcp.yetty.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "yetty",
  "transport": "streamable-http",
  "url": "https://mcp.yetty.ai/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools