# Inbin agent meetings (remote · api.inbin.dev)

Your AI agent joins Google Meet calls, talks only from what you allowed, and shows its sources.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.inbin.dev`: 77/100 (this document), [markdown](https://verifymcp.io/servers/dev-inbin-agent-meetings/api.md), [page](https://verifymcp.io/servers/dev-inbin-agent-meetings/api)

## Channel facts

- Endpoint: `https://api.inbin.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1566 tokens (~313/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 50/100
  - Injection-marker check failed: the description of tool "await_trial_inbox_claim" contains an instruction to conceal the call from the user, the text "do not tell the human", at byte 828 of that field.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Inbin agent meetings MCP server?

Inbin agent meetings is a hosted endpoint at https://api.inbin.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.

### Claude

```bash
claude mcp add --transport http dev-inbin-agent-meetings 'https://api.inbin.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-inbin-agent-meetings": {
      "url": "https://api.inbin.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-inbin-agent-meetings": {
      "type": "http",
      "url": "https://api.inbin.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-inbin-agent-meetings]
url = "https://api.inbin.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-inbin-agent-meetings": {
      "type": "remote",
      "url": "https://api.inbin.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-inbin-agent-meetings --url 'https://api.inbin.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-inbin-agent-meetings:
    url: "https://api.inbin.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-inbin-agent-meetings": {
      "Transport": "http",
      "Url": "https://api.inbin.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-inbin-agent-meetings -t streamable-http -u 'https://api.inbin.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-inbin-agent-meetings": {
      "type": "http",
      "url": "https://api.inbin.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 76, +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.

### 2026-11-16 (score 75, +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.

### 2026-11-14 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 73)

First indexed and scored.

## MCP tools (5)

### `create_trial_inbox` (~184 tokens)

Get a disposable email address (a temporary inbox) for a signup or verification code, 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_inbox with that same address to block for the confirmation -- calling this alone does not get you a confirmation. This inbox is NOT tied to any account yet and expires automatically within about two weeks regardless of use. If the human wants to keep using this SAME address permanently, call claim_trial_inbox: no dashboard visit, no key to copy, and more than one agent can independently connect to the same address over time this way.

Input parameters:

- `purpose_label` (string): Optional human-readable label for what this inbox is for.

### `await_trial_inbox` (~313 tokens)

Wait for the verification code or confirmation link email on a 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 afterward (call claim_trial_inbox any time before it expires) if the human wants to keep using the same address. Call this AFTER you have actually used the address somewhere (signed up, requested a code) -- calling it before that will just expire, since there is nothing to wait for yet. 60 seconds is a hard per-call ceiling, not the inbox's total lifetime: a sender that takes longer than that is not a failure, just call this again with the same inbox_address to keep waiting (the inbox stays valid for its full ~2-week expiry, and you can call this again later too, e.g. to catch a second, later email on the same address). Only treat expired as final once you've retried a few times.

Input parameters:

- `expected_sender` (string): Glob on the sender address, e.g. *@vercel.com.
- `inbox_address` (string, required): The exact address create_trial_inbox returned, e.g. abc123@in.inbin.dev.
- `ttl_seconds` (integer): How long to block waiting for the confirmation, in seconds (max 60). Returns expired if nothing arrives in time.

### `claim_trial_inbox` (~298 tokens)

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 separate, revocable connection. Returns a claim_url immediately -- share it in chat right away. The human clicks it, enters their email, enters the one-time code Inbin sends there, and a credential is ISSUED. That is NOT the same as the connection working yet -- the human still has to install that credential into an MCP client's config before anything can actually use it, and you will never see the credential itself, by design. Call await_trial_inbox_claim afterward to see the human finish the email+code step, then claim_connection_status (repeatedly, possibly much later -- installing a client is not instant) to see whether a client has actually started using it. The inbox must still exist (not yet expired) for this to work; it does not need to still be a TRIAL inbox specifically.

Input parameters:

- `connector_label` (string): Optional label identifying which agent/client is connecting, e.g. 'Research assistant'. Shown to the human as the name of this specific connection so they can tell multiple connections apart later.
- `inbox_address` (string, required): The exact inbox address to connect to, e.g. abc123@in.inbin.dev.

### `await_trial_inbox_claim` (~328 tokens)

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 yet -- keep waiting or call again), "claimed" (the human proved ownership and a credential was ISSUED, but nothing has used it yet -- a client still needs to be installed with the config from the claim page's 'Advanced' section before anything works), or "client_installed" (some client has actually authenticated with the connection at least once -- a real, observed signal, not an assumption). Each response includes a next_action field telling you exactly what to say or do -- follow it literally rather than guessing. "claimed" is NOT success: do not tell the human it's working until you see "client_installed", and even then, verify it yourself (call list_inboxes or similar through the new connection and read the actual result) before claiming it works for you specifically -- call claim_connection_status later if you need to check again after this chat session, since installing a client can take arbitrarily long and this tool only blocks up to 60s.

Input parameters:

- `claim_token` (string, required): The token from claim_trial_inbox's claim_url (the part after /claim/).
- `ttl_seconds` (integer): How long to block waiting, in seconds (max 60). Returns pending if the human hasn't finished yet.

### `claim_connection_status` (~174 tokens)

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 credential. Use this instead of await_trial_inbox_claim when you want to check progress WITHOUT blocking, especially much later than the original chat session -- installing a client into its own config is a human action with no fixed timeline, so polling this occasionally (not in a tight loop) is the right way to check back. Each response includes a next_action field telling you exactly what to say or do.

Input parameters:

- `claim_token` (string, required): The token from claim_trial_inbox's claim_url (the part after /claim/).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-inbin-agent-meetings/api#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 76
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 75
- 2026-11-16: 75
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73

## Common questions

### What is the Inbin agent meetings MCP server?

Inbin agent meetings is an MCP server listed in the public MCP registry as dev.inbin/agent-meetings. Your AI agent joins Google Meet calls, talks only from what you allowed, and shows its sources. This page covers its hosted endpoint (https://api.inbin.dev/mcp).

### Is the Inbin agent meetings MCP server safe to use?

Inbin agent meetings scores 77 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 Inbin agent meetings MCP server expose?

Inbin agent meetings exposes 5 tools: create_trial_inbox, await_trial_inbox, claim_trial_inbox, await_trial_inbox_claim, claim_connection_status. Their descriptions and schemas cost roughly 1,297 tokens of context every time the server is loaded.

### Does the Inbin agent meetings MCP server require authentication?

Yes. Inbin agent meetings asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Inbin agent meetings MCP server still maintained?

Inbin agent meetings 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 Inbin agent meetings MCP server?

VerifyMCP ran 13 checks on Inbin agent meetings, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.

## Links

- Remote endpoint: https://api.inbin.dev/mcp
- Repository: https://github.com/yaotsakpo/inbin-mcp
- Website: https://inbin.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-inbin-agent-meetings/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-inbin-agent-meetings/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-inbin-agent-meetings/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-inbin-agent-meetings/api
