KeyID

io.github.KeyID-AIPublished by GitHub account KeyID-AIv0.4.1Updated Oct 24, 2026

Signup sessions, browser continuity, email, SMS, and OTP/TOTP infrastructure for AI agents.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Gives an assistant signup sessions, browser continuity, and email, SMS, and OTP/TOTP infrastructure for agent-driven account flows.

What you can do
KeyID supplies infrastructure for AI agents that need to create and maintain accounts. According to its description it covers signup sessions, browser continuity, and email, SMS, and OTP/TOTP handling. It can be reached as a remote endpoint or run locally through the @keyid/agent-kit npm package. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Reach for it when an agent must complete signup or verification flows that depend on email, SMS, or one-time and time-based codes, or when a browser session needs to persist across steps. It is not aimed at general coding or data tasks.
Requirements
A remote endpoint at keyid.ai over streamable HTTP, or a local process run with npx from the npm package @keyid/agent-kit over stdio. OAuth authentication is required. No environment variables or headers are declared. Network access is needed for the remote endpoint.
Before you install
Authentication is required and uses OAuth, so the assistant is granted access to an account on the provider's service. The server handles email, SMS, and OTP/TOTP flows, which are sensitive identity operations; treat any codes, sessions, or credentials it manages as secrets. No tool list is published, so review exactly which actions it can take before granting access.

Installation

In SourceWeft

  1. Open KeyID 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/io.github.KeyID-AI%2Fkeyid/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": {
    "keyid": {
      "type": "http",
      "url": "https://keyid.ai/mcp"
    }
  }
}

README

This repository has no README.

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.4.1LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.