Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
No-signup email for AI agents over MCP: trial inbox, verification codes, parsed email events.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
INBIN_API_KEY, Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"inbin": {
"command": "npx",
"args": [
"-y",
"@inbin/mcp"
],
"env": {
"INBIN_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http inbin https://api.inbin.dev/mcp --header 'Authorization: your-value'claude mcp add inbin --env INBIN_API_KEY=your-value -- npx -y @inbin/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"inbin": {
"url": "https://api.inbin.dev/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"inbin": {
"command": "npx",
"args": [
"-y",
"@inbin/mcp"
],
"env": {
"INBIN_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"inbin": {
"type": "http",
"url": "https://api.inbin.dev/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"inbin": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@inbin/mcp"
],
"env": {
"INBIN_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
create_trial_inboxCreate a temporary inbox with NO Inbin account required at all -- usable before the human has signed up for anything. Returns the inbox address IMMEDIATELY; it does not wait for anything. Use the address to sign up wherever you need a confirmation sent, THEN call await_trial_inbo
await_trial_inboxBlock (up to ttl_seconds, max 60) for the one confirmation email on a trial inbox created by create_trial_inbox. Pass the exact inbox_address that call returned. The inbox does NOT self-delete or become unusable after a match: it keeps receiving mail and can still be claimed afte
claim_trial_inboxStart connecting an agent to this inbox address, permanently -- the SAME address. Works whether this is a brand-new trial inbox OR one that's already been claimed by a different agent before: more than one agent can independently connect to the same inbox, each getting its own se
await_trial_inbox_claim 看起来像是对 AI 下的指令Block (up to ttl_seconds, max 60) for a human to finish the EMAIL+CODE step on the claim_url page from claim_trial_inbox. This NEVER returns a credential, at any status. It returns one of three honest states, not a single 'connected': "claim_pending" (nobody has entered the code
claim_connection_statusRead-only, non-blocking check of exactly which state a claim_trial_inbox connection is in RIGHT NOW: "claim_pending", "claimed" (credential issued, unused), or "client_installed" (a client has actually authenticated with it at least once -- real, observed). Never returns a creden
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 yaotsakpo 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 1125 毫秒内响应(HTTP 200)
无需登录
有 1 个工具描述包含看起来像是对 AI 下指令的文字。安装前请先阅读下方的内容
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:INBIN_API_KEY, Authorization
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.3.0)于7天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Vexa, emailmd, MCP WhatsApp Cloud
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A minimal stdio-to-HTTP proxy for Inbin's Model Context Protocol surface. Lets stdio-only MCP clients (Claude Desktop, some Cursor builds, Zed, Cline) talk to Inbin's remote endpoint at https://api.inbin.dev/mcp.
Nothing to install globally. Your MCP client invokes it via npx:
{
"mcpServers": { "inbin": { "command": "npx", "args": ["-y", "@inbin/mcp"], "env": { "INBIN_API_KEY": "ink_live_..." } } } }
Get an API key from https://inbin.dev/dashboard.
Over the remote endpoint (below) five tools need no key at all. An agent can create an inbox, use its address, and wait for a verification code:
create_trial_inbox returns an inbox_address at once (it expires after 14 days).await_trial_inbox with that exact inbox_address waits up to 60 seconds for the code or link. Call it again if it returns expired.claim_trial_inbox returns a link for a person to keep the address, and await_trial_inbox_claim and claim_connection_status follow that claim.This stdio wrapper always sends a key, so it is for the key tools. For the no-account tools connect straight to https://api.inbin.dev/mcp with no header. A runnable walkthrough: https://inbin.dev/guides/ai-agent-email-address-verification-codes
https://api.inbin.dev/mcp as an HTTPS POST with your Bearer key.id) get no reply, per JSON-RPC.Every Inbin application is an MCP server. With a key, the tools include (ask tools/list for the full set):
list_inboxes: enumerate inboxes in your applist_events: filter by inbox / status / since; paginatedsearch_events: substring search over id / subject / from / toget_event: a single event's parsed JSON + delivery historyquery_events: filter, sort, group and aggregate over extracted records (your inbox as a table)describe_schema: the current extraction schema| Variable | Required | Description |
|---|---|---|
INBIN_API_KEY | yes | your Inbin API key |
INBIN_MCP_URL | no | override the endpoint (defaults to production) |
INBIN_MCP_DEBUG | no | set to 1 for stderr logs |
If your MCP client supports Streamable HTTP transport, skip this wrapper entirely and connect directly. Without a header you get the five no-account tools; with a key you get everything:
{
"mcpServers": { "inbin": { "url": "https://api.inbin.dev/mcp", "headers": { "Authorization": "Bearer ink_live_..." } } } }
MIT.