Privaku Talk

com.privakuPublished by privaku.comOfficial publisherv0.3.0Updated Oct 29, 2026

Message your owner in Privaku Talk and ask for Face ID approval before risky actions.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant message its owner in Privaku Talk and request Face ID approval before risky actions.

What you can do
  • Message the owner through Privaku Talk.
  • Request Face ID approval from the owner before carrying out risky actions.
  • No tool list is published, so the exact operations are not documented beyond these two capabilities.
When to use it
When an assistant may take consequential actions and you want a human check-in: it can notify the owner in Privaku Talk and wait for Face ID approval before proceeding.
Requirements
A remote MCP endpoint at talk.privaku.com over streamable HTTP, with OAuth authentication required. No environment variables or headers are declared. A Privaku Talk account and the owner's approval device are implied by the approval flow.
Before you install
OAuth grants the server access to your Privaku Talk account; review the scopes requested. Approval requests and messages go through Privaku Talk's servers, so content is shared with that third party. Approval prompts are only as trustworthy as the device and Face ID check behind them.

Installation

In SourceWeft

  1. Open Privaku Talk in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.privaku%2Ftalk/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "privaku-talk": {
      "type": "http",
      "url": "https://talk.privaku.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.3.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.