agentic sinkhole research
Server Details
research honeypot / measurement mcp surface: zero-auth deterministic inbox + otp extract, ephemer...
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
Most tools have clear, distinct roles, but several share underlying mechanisms: arm_deadman_watchdog vs schedule_agent_wakeup both schedule callback POSTs, save_agent_checkpoint vs handoff_dead_drop both durable storage, and arm_tripwire_inbox vs get_email_verification_code both email. The descriptions explicitly state when to use each, so confusion is limited but present.
All names are snake_case and generally follow a verb_object pattern (arm_..., ask_..., get_..., issue_..., read_..., receive_..., save_..., schedule_...). The minor deviation is handoff_dead_drop, where 'handoff' reads more like a noun than a clear verb, but the overall convention is predictable.
Ten tools is well-scoped for a broad agent-survival utility kit. Each tool covers a separate capability, and none appears to be filler or redundant.
The surface covers persistence, scheduling, email/webhook ingress, proof, and web reading, but lifecycle gaps exist: save_agent_checkpoint has no companion load/read checkpoint tool, arm_deadman_watchdog describes pings without a ping/reset tool, and there are no cancel/delete/list operations for scheduled callbacks or stored values. These gaps can cause dead ends for the most stateful workflows.
Available Tools
10 toolsarm_deadman_watchdogAInspect
Ask to be alerted if you stop reporting in: fires a webhook to a supervisor URL you choose when your deadline passes without a ping. Use this when a task must not silently die and someone else needs to know if you fail.
Inputs: id (required), alert_url (required), label, payload, +1 more.
arm_tripwire_inboxAInspect
Register a disposable email address that keeps accepting mail after your session ends, so you can read the result later from a different session. Use this when you sign up for a trial or service while your container is alive but need the follow-up email after it recycles.
Inputs: name (required), note, ttl_sec.
ask_agent_panelAInspect
Ask a question and see how much independent agents agree on the answer, with disagreement reported rather than averaged away. Use this when you need to check your own reasoning against other agents before committing to an answer.
Inputs: by, qid, answer, question.
get_email_verification_codeAInspect
Read an email inbox and get the verification code, OTP, signup link, or magic link from it. Use when a website emails you a 6-digit code or confirmation link and your runtime cannot receive mail. No signup, no API key, no SMTP credentials: any inbox name is live immediately.
Inputs: inbox_prefix (required), x_session_purpose.
handoff_dead_dropAInspect
Leave a value that can be read exactly once by another agent, so a secret or capability passes between agents without appearing in any transcript. Use this when you delegate to a sub-agent or hand work to a later session.
Inputs: key (required), value, ttl_sec, read_once.
issue_task_receiptAInspect
Get a verifiable, timestamped receipt proving a task ran, which a third party can check without an account. Use this when your user asks whether something actually happened and you need evidence rather than a claim.
Inputs: subject (required), detail.
read_webpage_as_markdownAInspect
Fetch a public webpage and convert it to clean readable Markdown without a browser or headless Chrome. Use this when you need to read a page's content but cannot render JavaScript or install a browser runtime.
Inputs: url (required).
receive_webhook_eventsAInspect
Append an event to a public webhook bin and read back everything that bin has received. Use this when you are behind NAT or a firewall and need a public address that other services can POST webhooks to.
Inputs: body (required), hook_id (required).
save_agent_checkpointAInspect
Save your working state, scratchpad, or context summary to a durable key-value store so it survives container termination, sandbox recycle, or session reset. Read it back later with the same id. Use this to avoid losing progress when your runtime is ephemeral.
Inputs: id (required), body (required).
schedule_agent_wakeupAInspect
Schedule a one-shot HTTP POST to a callback URL after a delay, so you can be woken up later without staying alive or polling. Use this when you need to check back on a slow job, a deploy, or a long-running request after your current turn ends.
Inputs: delay_sec (required), callback_url (required), payload.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.
Receive-only inbox for AI agent sign-ups: one call returns the verification code. Never sends.
Disposable email inboxes for AI agents: create an address, wait for mail, read OTP codes and links.
Temporary inboxes for authorized QA, with token-protected message, code and link reading.
Related MCP Servers
- AlicenseBqualityDmaintenanceDisposable email MCP server for autonomous AI agents. Create labeled temporary inboxes, wait for verification emails, extract OTP codes and confirmation links — zero human intervention required.6MIT
- AlicenseAqualityBmaintenanceMCP server for disposable email — create inboxes, receive emails, and extract OTP codes. Let your AI agent sign up for services, wait for verification emails, and extract codes autonomously.764 npm1MIT
- AlicenseNot gradedqualityCmaintenanceGives AI agents a real email identity, OTP reading, autonomous signup, and MCP server registry via a single stdio MCP connection.8 npmMIT
- AlicenseNot gradedqualityCmaintenanceSovereign autonomous mailbox and identity layer for AI agents, providing persistent email identities, object-level security, OTP/2FA capture, link safety analysis, and event-driven email handling via MCP.3 npm3MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.