# Referna Meeting Recaps (remote · referna.com)

Read your personalized Referna meeting recaps with an AI assistant.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `referna.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/referna-ai-meeting-recaps/mcp-member-recaps.md), [page](https://verifymcp.io/servers/referna-ai-meeting-recaps/mcp-member-recaps)

## Channel facts

- Endpoint: `https://referna.com/mcp/member-recaps`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 162 tokens (~81/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Referna Meeting Recaps MCP server?

Referna Meeting Recaps is a hosted endpoint at https://referna.com/mcp/member-recaps, 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 referna-ai-meeting-recaps 'https://referna.com/mcp/member-recaps'
```

### Cursor

```json
{
  "mcpServers": {
    "referna-ai-meeting-recaps": {
      "url": "https://referna.com/mcp/member-recaps"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "referna-ai-meeting-recaps": {
      "type": "http",
      "url": "https://referna.com/mcp/member-recaps"
    }
  }
}
```

### Codex

```toml
[mcp_servers.referna-ai-meeting-recaps]
url = "https://referna.com/mcp/member-recaps"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "referna-ai-meeting-recaps": {
      "type": "remote",
      "url": "https://referna.com/mcp/member-recaps",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add referna-ai-meeting-recaps --url 'https://referna.com/mcp/member-recaps' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  referna-ai-meeting-recaps:
    url: "https://referna.com/mcp/member-recaps"
```

### Netclaw

```json
{
  "McpServers": {
    "referna-ai-meeting-recaps": {
      "Transport": "http",
      "Url": "https://referna.com/mcp/member-recaps"
    }
  }
}
```

### Vellum

```bash
assistant mcp add referna-ai-meeting-recaps -t streamable-http -u 'https://referna.com/mcp/member-recaps'
```

### Other

```json
{
  "mcpServers": {
    "referna-ai-meeting-recaps": {
      "type": "http",
      "url": "https://referna.com/mcp/member-recaps"
    }
  }
}
```

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-05 (score 82, +1)

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

### 2026-11-03 (score 81, +1)

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

### 2026-10-31 (score 80, +1)

- [functional improvement] Tool “get_meeting_recap” now declares an output schema
- [functional improvement] Tool “list_meeting_recaps” now declares an output schema
- [functional] First check of Tool coverage: 100

### 2026-10-29 (score 79, +1)

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

### 2026-10-27 (score 78, +1)

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

### 2026-10-25 (score 77, +1)

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

### 2026-10-23 (score 76, 0)

- [security] Tool “get_meeting_recap” rewrote its description, which is the text the model reads
- [security] Tool “list_meeting_recaps” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 67 → 81
- [functional] Schema quality: excellent → good
- [cosmetic] “get_meeting_recap” reworded the description of “sessionId”

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

## MCP tools (2)

### `list_meeting_recaps` (~90 tokens)

List my meeting recaps

List the key owner's personalized Referna intro, general, follow-up, and mixer recaps, newest first. Mixer recaps include the 1:1 checklist for each conversation the member joined.

Input parameters:

- `limit` (integer): Number of recaps, from 1 to 50. Default 20.
- `offset` (integer): Number of newer recaps to skip. Default 0.

Output parameters:

- `nextOffset` (integer|null)
- `recaps` (array)

### `get_meeting_recap` (~72 tokens)

Get my meeting recap

Get one personalized Referna meeting recap by ID from the list. Returns not found when the key owner cannot access it.

Input parameters:

- `sessionId` (string, required): Recap ID returned as sessionId by list_meeting_recaps. Mixer IDs have mixer:<mixerId>:<occurrenceId> format.

Output parameters:

- `recap` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/referna-ai-meeting-recaps/mcp-member-recaps#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 76
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 71
- 2026-10-12: 33

## Common questions

### What is the Referna Meeting Recaps MCP server?

Referna Meeting Recaps is an MCP server listed in the public MCP registry as io.github.referna-ai/meeting-recaps. Read your personalized Referna meeting recaps with an AI assistant. This page covers its hosted endpoint (https://referna.com/mcp/member-recaps).

### Is the Referna Meeting Recaps MCP server safe to use?

Referna Meeting Recaps scores 82 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 Referna Meeting Recaps MCP server expose?

Referna Meeting Recaps exposes 2 tools: list_meeting_recaps, get_meeting_recap. Their descriptions and schemas cost roughly 162 tokens of context every time the server is loaded.

### Does the Referna Meeting Recaps MCP server require authentication?

No. We connected to Referna Meeting Recaps without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Referna Meeting Recaps MCP server still maintained?

Referna Meeting Recaps is still listed as active in the MCP registry. We last reached this channel on 5 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 Referna Meeting Recaps MCP server?

VerifyMCP ran 13 checks on Referna Meeting Recaps, 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://referna.com/mcp/member-recaps
- Authorisation metadata: https://referna.com/.well-known/oauth-protected-resource/mcp/member-recaps
- Website: https://referna.com/
- Changelog RSS feed: https://verifymcp.io/servers/referna-ai-meeting-recaps/mcp-member-recaps.xml
- Changelog JSON feed: https://verifymcp.io/servers/referna-ai-meeting-recaps/mcp-member-recaps/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/referna-ai-meeting-recaps/mcp-member-recaps.json
- HTML version of this page: https://verifymcp.io/servers/referna-ai-meeting-recaps/mcp-member-recaps