Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Inbin

by yaotsakpoversion 0.3.0i★ –iComputer or cloud
Registry nameio.github.yaotsakpo/inbin

Install

Overview

Description from the maker (original English)

No-signup email for AI agents over MCP: trial inbox, verification codes, parsed email events.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Chat & email
  • You need to fill in: INBIN_API_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 2 of 3 passed Fail
  • Runs on the maker’s server: what you ask it goes through their server.
  • Can do 5 things (tools) create_trial_inbox, await_trial_inbox, claim_trial_inbox, await_trial_inbox_claim …
  • You fill in yourself: INBIN_API_KEY, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "inbin": {
      "command": "npx",
      "args": [
        "-y",
        "@inbin/mcp"
      ],
      "env": {
        "INBIN_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http inbin https://api.inbin.dev/mcp --header 'Authorization: your-value'

Or run it on your computer

claude mcp add inbin --env INBIN_API_KEY=your-value -- npx -y @inbin/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "inbin": {
      "url": "https://api.inbin.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "inbin": {
      "command": "npx",
      "args": [
        "-y",
        "@inbin/mcp"
      ],
      "env": {
        "INBIN_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "inbin": {
      "type": "http",
      "url": "https://api.inbin.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "inbin": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@inbin/mcp"
      ],
      "env": {
        "INBIN_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • INBIN_API_KEY secret required env
    Your Inbin API key (starts with ink_live_). Get one at https://inbin.dev/dashboard.
  • Authorization secret HTTP header
    Optional: Bearer . Leave it out to use the five no-account tools (create_trial_inbox, await_trial_inbox, claim_trial_inbox, await_trial_inbox_claim, claim_connection_status). Every other tool needs t…

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

  • create_trial_inbox

    Create 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_inbox

    Block (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_inbox

    Start 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 Looks like an instruction to the 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_status

    Read-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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account yaotsakpo, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 1125 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✕ Fail

    No hidden instructions in tool descriptions

    1 tool descriptions contain text that looks like instructions to the AI. Read them below before installing

Compared with others in Chat & emaili

  • More stars than 0% of the other 1787 servers in this category
  • Published to the registry more recently than 79% of the other 1787 servers in this category
  • Basic checks equal to or better than 45% of the other 1787 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Inbin safe?

It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: INBIN_API_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago
Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 32 days ago
Install

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@inbin/mcp

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.

Install & run

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.

No account yet?

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:

  1. create_trial_inbox returns an inbox_address at once (it expires after 14 days).
  2. Use that address wherever a confirmation must be sent.
  3. 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.
  4. 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

What it does

  • Forwards each stdin JSON-RPC message to https://api.inbin.dev/mcp as an HTTPS POST with your Bearer key.
  • Streams the response back to stdout.
  • Notifications (messages with no id) get no reply, per JSON-RPC.
  • Concurrent in-flight requests are supported.

Tools exposed

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 app
  • list_events: filter by inbox / status / since; paginated
  • search_events: substring search over id / subject / from / to
  • get_event: a single event's parsed JSON + delivery history
  • query_events: filter, sort, group and aggregate over extracted records (your inbox as a table)
  • describe_schema: the current extraction schema

Environment

VariableRequiredDescription
INBIN_API_KEYyesyour Inbin API key
INBIN_MCP_URLnooverride the endpoint (defaults to production)
INBIN_MCP_DEBUGnoset to 1 for stderr logs

Remote (recommended)

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_..." } } } }

License

MIT.

Ask PopNx