AgentLair
REMOTE · AGENTLAIR-MCP-SERVER.AMDAL-DEV.WORKERS.DEV · 2 COMPONENTS
Give AI agents a real email address, vault, calendar, and task delegation via MCP.
Available components
Last scanned (17 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1305 tokens (~87/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 Management57
- Stability observed for 17 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 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 → Fail
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://agentlair-mcp-server.amdal-dev.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=amdal-dev.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 540e556ee46e63c76203e3d5d4fb1ce90ee |
| SANs: *.amdal-dev.workers.dev, amdal-dev.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentlair-mcp-server.amdal-dev.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentlair-mcp-server.amdal-dev.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://agentlair-mcp-server.amdal-dev.workers.dev/mcp | Inconclusive | 405 |
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 →
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).
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | array | – | Optional list of attendee email addresses |
| description | string | – | Optional event description / notes |
| end | string | yes | Event end time in ISO 8601 format. Date-only ("2026-03-21") or datetime ("2026-03-20T15:00:00Z") |
| location | string | – | Optional event location (address, URL, or room name) |
| start | string | yes | Event start time in ISO 8601 format. Date-only ("2026-03-20") or datetime ("2026-03-20T14:00:00Z") |
| summary | string | yes | Event 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Event 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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Optional start of date range filter (ISO 8601, e.g. "2026-03-01") |
| to | string | – | Optional end of date range filter (ISO 8601, e.g. "2026-03-31") |
No output schema declared.
No examples provided.
check_inbox ~84
Check the inbox for an @agentlair.dev email address. Returns recent messages with sender, subject, and received time.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The @agentlair.dev address to check (e.g. mybot@agentlair.dev) |
| limit | number | – | Max number of messages to return (default: 10, max: 50) |
No output schema declared.
No examples provided.
claim_address ~59
Claim a new @agentlair.dev email address for your agent. Free tier supports multiple addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address to claim (must end in @agentlair.dev, e.g. mybot@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.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | string | – | Timing constraints, requirements, or limits |
| context | string | – | Background information the agent needs to execute the task |
| priority | string | – | Task priority (default: normal) |
| task | string | yes | What to do — be specific and self-contained. The receiving agent has no context from your conversation. |
| to | string | yes | Target agent's AgentLair email (e.g. pico@agentlair.dev) |
No output schema declared.
No examples provided.
list_addresses ~23
List all @agentlair.dev email addresses associated with your API key.
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | AgentLair 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 ~64
Read the full content of a specific email message, including the body text.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The @agentlair.dev address this message was delivered to |
| message_id | string | yes | The message_id from check_inbox (angle brackets will be stripped automatically) |
No output schema declared.
No examples provided.
send_email ~127
Send an email from your AgentLair address (@agentlair.dev) to any recipient. No SMTP or DNS setup needed.
| Name | Type | Req | Description |
|---|---|---|---|
| cc | array | – | Optional CC recipient addresses |
| from | string | yes | Sender address — must be an @agentlair.dev address you own (e.g. mybot@agentlair.dev) |
| html | string | – | Optional HTML body (supplement to text) |
| subject | string | yes | Email subject line |
| text | string | yes | Plain text body of the email |
| to | array | yes | Array of recipient email addresses |
No output schema declared.
No examples provided.
vault_delete ~34
Delete a key and all its versions from the AgentLair Vault.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Vault 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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Vault 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).
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Vault key name (1-128 chars, alphanumeric + _ - .). Examples: 'openai-key', 'session_token', 'config.json' |
| metadata | object | – | Optional JSON metadata (labels, timestamps, etc.) — never encrypted |
| value | string | yes | Value to store. For secrets: encrypt first, then store the ciphertext. |
No output schema declared.
No examples provided.
How do I install the AgentLair MCP server?
AgentLair is a hosted endpoint at https://agentlair-mcp-server.amdal-dev.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentlair-mcp-server.amdal-dev.workers.dev
claude mcp add --transport http piiiico-agentlair 'https://agentlair-mcp-server.amdal-dev.workers.dev/mcp'
What is the AgentLair MCP server?
AgentLair is an MCP server listed in the public MCP registry as io.github.piiiico/agentlair. Give AI agents a real email address, vault, calendar, and task delegation via MCP. This page covers its hosted endpoint (https://agentlair-mcp-server.amdal-dev.workers.dev/mcp).
Is the AgentLair MCP server safe to use?
AgentLair scores 65 out of 100 on VerifyMCP. 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 AgentLair MCP server expose?
AgentLair exposes 15 tools: send_email, check_inbox, read_message, list_addresses, claim_address, and 10 more. Their descriptions and schemas cost roughly 1,203 tokens of context every time the server is loaded.
Does the AgentLair MCP server require authentication?
No. We connected to AgentLair without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentLair MCP server still maintained?
AgentLair is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the AgentLair MCP server?
VerifyMCP ran 11 checks on AgentLair, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about AgentLair: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.