Yaver

endpoint

https://yaver.io/api/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is Yaver live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is Yaver free to use?

Yes — the hub reached it with no key and no payment.

What tools does Yaver have?

9 tools: yaver_app_runtime_guide, yaver_codex_setup, yaver_game_manifest_audit, yaver_project_bootstrap_guide, yaver_native_oauth_guide, yaver_mcp_package_info, yaver_privacy_summary, yaver_strategy_game_native_guide, ….

Is Yaver safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• yaver_game_manifest_audit reads open 15h ago

  Validate that a Yaver-native game manifest requires Yaver OAuth, Yaver billing ownership, no source copying, native host declarations, and release-only source sharing.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "required": [
      "manifest"
    ],
    "properties": {
      "manifest": {
        "type": "object",
        "description": "Parsed yaver.game.yaml or yaver.game.json manifest.",
        "additionalProperties": true
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• yaver_project_bootstrap_guide reads open 15h ago

  Explain the first safe MCP calls for creating a local-first Yaver project and pairing a phone.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "properties": {
      "projectType": {
        "enum": [
          "react_native",
          "web",
          "full_stack",
          "unknown"
        ],
        "type": "string",
        "description": "The kind of app the user wants to start or connect."
      }
    },
    "additionalProperties": false
  }

  arguments 16 lines copy
• yaver_native_oauth_guide reads open 24h ago

  Explain how a Yaver-native app or game should use Yaver OAuth as the platform identity layer below its own standalone auth providers.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233

  {
    "type": "object",
    "required": [
      "appId",
      "appKind"
    ],
    "properties": {
      "appId": {
        "type": "string",
        "description": "Yaver app/game id, for example game_sfmg or game_carrotbet."
      },
      "appKind": {
        "enum": [
          "app",
          "game"
        ],
        "type": "string",
        "description": "Whether the integration is a general Yaver-native app or game."
      },
      "externalProvidersOutsideYaver": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Optional standalone providers outside Yaver, such as google, apple, email, github."
      },
      "standaloneAuthAllowedOutsideYaver": {
        "type": "boolean",
        "description": "Whether the app can keep its own auth outside Yaver builds."
      }
    },
    "additionalProperties": false
  }

  arguments 33 lines copy
• yaver_mcp_package_info reads open 5h ago

  Return public package and registry metadata for the local Yaver MCP server.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• yaver_privacy_summary reads open 5h ago

  Summarize how Yaver's hosted coordination plane differs from the local MCP server.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• yaver_strategy_game_native_guide reads open 5h ago

  Explain the Yaver-native strategy game contract for mobile, tablet, TV, watch, browser, and remote-runner compatibility.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "properties": {
      "gameType": {
        "enum": [
          "sfmg",
          "strategy",
          "simulation",
          "unknown"
        ],
        "type": "string",
        "description": "The game or strategy-game family being integrated."
      }
    },
    "additionalProperties": false
  }

  arguments 16 lines copy
• yaver_app_manifest_audit reads open 15h ago

  Validate that a Yaver-native app manifest preserves external release freedom while enforcing Yaver OAuth, billing, source-sharing, native host, MCP, and surface policy for catalog builds.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "required": [
      "manifest"
    ],
    "properties": {
      "manifest": {
        "type": "object",
        "description": "Parsed yaver.app.yaml or yaver.app.json manifest.",
        "additionalProperties": true
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• yaver_app_runtime_guide reads unknown never probed

  Explain the Yaver app runtime contract for external release, optional Yaver catalog distribution, MCP, cloud inference, and multi-surface support.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "properties": {
      "appType": {
        "enum": [
          "game",
          "simulation",
          "workflow",
          "assistant_connector",
          "devtool",
          "unknown"
        ],
        "type": "string",
        "description": "The app family being integrated."
      }
    },
    "additionalProperties": false
  }

  arguments 18 lines copy
• yaver_codex_setup reads unknown never probed

  Get the recommended Yaver MCP setup steps for Codex Desktop, Codex CLI, Claude Code, or OpenCode.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "properties": {
      "client": {
        "enum": [
          "codex_desktop",
          "codex_cli",
          "claude_code",
          "opencode",
          "other"
        ],
        "type": "string",
        "description": "The MCP client the user wants to configure."
      }
    },
    "additionalProperties": false
  }

  arguments 17 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.