Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

KeyID

NPM · @KEYID/AGENT-KIT · 2 COMPONENTS

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

0 this week 77 Trust /100

Last scanned (4 hours ago)

Scores higher than 55% of npm servers

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 82 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2955 tokens (~41/item across 71 items; 64 tools + 7 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 22% of tool parameters carry a description.Partial
Tool Safety96
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 6 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_email" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
  • An AI judge read all 65 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 19 Oct 26 +1
    • Stability: 0.97 → pass security
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@keyid/agent-kit@0.4.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 64 exposed · ~2,863 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
send_email ~83

Send an email from the current identity.

NameTypeReqDescription
bccarray––
bodystring––
ccarray––
displayNamestring––
htmlstring––
scheduledAtstring––
subjectstringyes–
threadIdstring––
tostringyes–

No output schema declared.

No examples provided.

set_auto_reply ~58

Enable, disable, or edit the auto-reply responder.

NameTypeReqDescription
bodystring––
enabledbooleanyes–
endDatestring––
startDatestring––
subjectstring––

No output schema declared.

No examples provided.

set_forwarding ~25

Set or clear the forwarding address.

NameTypeReqDescription
forwardingAddressstring|nullyes–

No output schema declared.

No examples provided.

set_signature ~23

Set or clear the email signature.

NameTypeReqDescription
signaturestring|nullyes–

No output schema declared.

No examples provided.

start_registration_session ~134

Start a signup session that correlates email, SMS, or TOTP artifacts for one service.

NameTypeReqDescription
bodyPatternstring––
browserStateKeystring––
expectedArtifactTypesarray––
expectedChannelsarray––
expectedSendersarray––
expiresAtstring–ISO timestamp when the session should expire
metadataobject––
senderPatternstring––
serviceDomainstring––
serviceNamestringyes–
subjectPatternstring––
useSmsLeaseboolean––

No output schema declared.

No examples provided.

store_file ~107

Upload or overwrite a file. Content should be base64-encoded for binary, or plain text (which will be base64-encoded automatically).

NameTypeReqDescription
contentstringyesFile content (base64 for binary, plain text for text files)
contentTypestring–MIME type (default: application/octet-stream)
isPublicboolean–Make file publicly accessible via URL
keystringyesFile key (path-like, e.g. "data/config.json")

No output schema declared.

No examples provided.

update_cron ~80

Update a cron job — change schedule, URL, or pause/resume.

NameTypeReqDescription
activeboolean–Set false to pause, true to resume
cronExprstring––
cronIdstringyesCron job ID
namestring––
timezonestring––
webhookUrlstring––

No output schema declared.

No examples provided.

update_message ~57

Update message flags such as read or starred state.

NameTypeReqDescription
isReadboolean––
isStarredboolean––
labelsarray––
messageIdstringyes–
statusstring––

No output schema declared.

No examples provided.

update_page ~53

Update page title, description, or published status.

NameTypeReqDescription
descriptionstring––
publishedboolean–Set false to unpublish
slugstringyesPage slug
titlestring––

No output schema declared.

No examples provided.

upload_page_file ~100

Upload or update a file in an agent page. Content must be base64-encoded. Allowed types: HTML, CSS, JS, images, JSON, text.

NameTypeReqDescription
contentstringyesBase64-encoded file content
contentTypestring–MIME type (default: text/html)
pathstringyesFile path (e.g., index.html, style.css, logo.png)
slugstringyesPage slug

No output schema declared.

No examples provided.

upsert_contact ~50

Create a contact by email or update one by contact ID.

NameTypeReqDescription
contactIdstring––
emailstring––
namestring––
notesstring––

No output schema declared.

No examples provided.

wait_for_message ~89

Poll until a matching inbound message arrives.

NameTypeReqDescription
channelstring––
includeExistingboolean––
pollIntervalSecondsinteger––
receivedAfterstring–Only match messages at or after this ISO timestamp
searchstring––
senderContainsstring––
subjectContainsstring––
timeoutSecondsinteger––

No output schema declared.

No examples provided.

wait_for_registration_artifact ~55

Poll a signup session until an artifact arrives or the session expires, blocks, or times out.

NameTypeReqDescription
pollIntervalSecondsinteger––
sessionIdstringyes–
timeoutSecondsinteger––

No output schema declared.

No examples provided.

web_search ~106

Search the web via Google. Returns titles, URLs, and snippets. Rate-limited to 100 searches per day.

NameTypeReqDescription
countrystring–Country code for localized results (e.g. "us", "gb")
numinteger–Number of results (default 10)
querystringyesSearch query
timeRangestring–Time filter: h (hour), d (day), w (week), m (month), y (year)

No output schema declared.

No examples provided.

Install

How do I install the KeyID MCP server?

KeyID runs locally as an npm package, launched with npx -y @keyid/agent-kit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @keyid/agent-kit

# add to Claude Code
claude mcp add keyid-ai-keyid -- npx -y @keyid/agent-kit
Common questions

What is the KeyID MCP server?

KeyID is an MCP server listed in the public MCP registry as io.github.KeyID-AI/keyid. Signup sessions, browser continuity, email, SMS, and OTP/TOTP infrastructure for AI agents. This page covers its npm package (@keyid/agent-kit).

Is the KeyID MCP server safe to use?

KeyID scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the KeyID MCP server expose?

KeyID exposes 64 tools: provision_identity, get_identity, request_phone_number, list_messages, wait_for_message, and 59 more. Their descriptions and schemas cost roughly 2,863 tokens of context every time the server is loaded.

Is the KeyID MCP server still maintained?

KeyID is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the KeyID MCP server under?

KeyID declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.