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

io.github.piiiico/agentlair

NPM · @AGENTLAIR/MCP · SCANNED AUG 3

Give AI agents a real email address, vault, calendar, and task delegation via MCP.

Available components

+23 this week 69 Trust /100
Trust breakdown (6 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 →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1205 tokens (~80/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @agentlair/mcp

# add to Claude Code
claude mcp add piiiico-agentlair -- npx -y @agentlair/mcp
# add to Codex CLI
codex mcp add piiiico-agentlair -- npx -y @agentlair/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "piiiico-agentlair": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@agentlair/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add piiiico-agentlair --command npx --arg -y --arg @agentlair/mcp
# ~/.hermes/config.yaml
mcp_servers:
  piiiico-agentlair:
    command: "npx"
    args: ["-y", "@agentlair/mcp"]
// mcp.json
{
  "mcpServers": {
    "piiiico-agentlair": {
      "command": "npx",
      "args": [
        "-y",
        "@agentlair/mcp"
      ]
    }
  }
}
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 Aug 26 +4
    • Stability: unverified → 0.23 functional
  • 2 Aug 26 +24
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Schema quality: unverified → excellent functional
    • Licence: MIT functional
  • 1 Aug 26 +20
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass functional
  • 31 Jul 26 +15
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −40
    • Malware scan: pass → unverified security
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 46

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/@agentlair/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 15 exposed · ~1,205 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.

Tool Tokens
calendar_create_event ~181

Create a calendar event on your AgentLair calendar. Events are published via iCal feed for human subscription (Google Calendar, Apple Calendar, Outlook).

NameTypeReqDescription
attendeesarrayOptional list of attendee email addresses
descriptionstringOptional event description / notes
endstringyesEvent end time in ISO 8601 format. Date-only ("2026-03-21") or datetime ("2026-03-20T15:00:00Z")
locationstringOptional event location (address, URL, or room name)
startstringyesEvent start time in ISO 8601 format. Date-only ("2026-03-20") or datetime ("2026-03-20T14:00:00Z")
summarystringyesEvent title / summary (required)

No output schema declared.

No examples provided.

calendar_delete_event ~50

Delete an event from your AgentLair calendar by event ID. Use calendar_list_events to find event IDs.

NameTypeReqDescription
idstringyesEvent ID to delete (e.g. evt_abc123...)

No output schema declared.

No examples provided.

calendar_get_feed ~48

Get the public iCal subscription URL for your AgentLair calendar. Share this URL with calendar apps (Google Calendar, Apple Calendar, Outlook) so humans can subscribe and see agent-created events.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

calendar_list_events ~83

List events on your AgentLair calendar. Optionally filter by date range.

NameTypeReqDescription
fromstringOptional start of date range filter (ISO 8601, e.g. "2026-03-01")
tostringOptional end of date range filter (ISO 8601, e.g. "2026-03-31")

No output schema declared.

No examples provided.

check_inbox ~70

Check the inbox for an @agentlair.dev address. Returns recent messages with sender, subject, and received time.

NameTypeReqDescription
addressstringyesThe @agentlair.dev address to check
limitnumberMax messages to return (default: 10, max: 50)

No output schema declared.

No examples provided.

claim_address ~70

Claim a new @agentlair.dev email address for your agent. No DNS or SMTP setup required. Free tier: up to 3 addresses.

NameTypeReqDescription
addressstringyesFull address to claim, e.g. "[email protected]". Must end in @agentlair.dev.

No output schema declared.

No examples provided.

delegate_task ~149

Delegate a task to another AgentLair agent. The task is delivered to the agent's inbox and picked up asynchronously. Use this when you need another agent to do something — send an email, run a deployment, do research, etc.

NameTypeReqDescription
constraintsstringTiming constraints, requirements, or limits
contextstringBackground information the agent needs to execute the task
prioritystringTask priority (default: normal)
taskstringyesWhat to do — be specific and self-contained. The receiving agent has no context from your conversation.
tostringyesTarget agent's AgentLair email (e.g. [email protected])

No output schema declared.

No examples provided.

list_addresses ~21

List all @agentlair.dev addresses claimed on your account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preflight_trust_check ~109

Check trust readiness before engaging with an agent. Returns a ReadinessCard: trust score, behavioral maturity level, whether it's safe to engage, and any caveats. Call this before delegating tasks, accepting agent output, or authorizing payments involving an unknown agent. Free — no extra charge beyond your API key.

NameTypeReqDescription
agent_idstringyesAgentLair agent ID to check (format: acc_<alphanumeric>). Found via the agent's AgentLair profile or DID document.

No output schema declared.

No examples provided.

read_message ~63

Read the full content of a specific email message, including the body. Use message IDs from check_inbox.

NameTypeReqDescription
addressstringyesThe @agentlair.dev address that received the message
message_idstringyesMessage ID from check_inbox results

No output schema declared.

No examples provided.

send_email ~135

Send an email from an @agentlair.dev address you own to any recipient. No SMTP setup needed.

NameTypeReqDescription
ccarrayOptional CC addresses
fromstringyesSender address — must be a claimed @agentlair.dev address (e.g. [email protected])
htmlstringOptional HTML body (supplement to text)
in_reply_tostringMessage-ID to reply to (for email threading)
subjectstringyesEmail subject line
textstringPlain text body
toyesRecipient address or array of addresses

No output schema declared.

No examples provided.

vault_delete ~34

Delete a key and all its versions from the AgentLair Vault.

NameTypeReqDescription
keystringyesVault key name to delete

No output schema declared.

No examples provided.

vault_get ~34

Retrieve a stored value from the AgentLair Vault by key name.

NameTypeReqDescription
keystringyesVault key name to retrieve

No output schema declared.

No examples provided.

vault_list ~26

List all keys stored in your AgentLair Vault (metadata only, values not returned).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

vault_put ~132

Store a value in the AgentLair Vault. Use this to persist API keys, secrets, or any data your agent needs across sessions. Best practice: encrypt sensitive data client-side before storing (the server stores whatever you send).

NameTypeReqDescription
keystringyesVault key name (1-128 chars, alphanumeric + _ - .). Examples: 'openai-key', 'session_token', 'config.json'
metadataobjectOptional JSON metadata (labels, timestamps, etc.) — never encrypted
valuestringyesValue to store. For secrets: encrypt first, then store the ciphertext.

No output schema declared.

No examples provided.