# ai.memoket/memoket (remote · mcp.memoket.ai)

Memoket — access your recording transcripts, summaries, and key takeaways over MCP.

- Trust score: 75/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.memoket.ai`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ai-memoket-memoket/mcp.md), [page](https://verifymcp.io/servers/ai-memoket-memoket/mcp)

## Channel facts

- Endpoint: `https://mcp.memoket.ai/mcp`
- 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-08-03.

- **Endpoint Security**: 89/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 836 tokens (~119/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-memoket-memoket https://mcp.memoket.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-memoket-memoket]
url = "https://mcp.memoket.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-memoket-memoket": {
      "type": "remote",
      "url": "https://mcp.memoket.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-memoket-memoket --url https://mcp.memoket.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-memoket-memoket:
    url: "https://mcp.memoket.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-memoket-memoket": {
      "type": "http",
      "url": "https://mcp.memoket.ai/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-08-03 (score 75, +2)

No change was recorded against any check on this day. Schema Quality & AI Usability went from 62 to 68. Other categories moved too: Stability & Change Management rose 4.

### 2026-08-02 (score 73, +1)

- [functional] Schema quality: fair → good

### 2026-08-01 (score 72, 0)

- [functional] Schema quality: good → fair

### 2026-07-31 (score 72, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, −1)

No change was recorded against any check on this day. Schema Quality & AI Usability went from 70 to 64. Other categories moved too: Stability & Change Management rose 3.

### 2026-07-29 (score 69, +1)

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

### 2026-07-28 (score 68, +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-07-27 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (7)

### `list_conversations` (~226 tokens)

[metadata_query] List recordings by time window / participants. Returns id, title, started_at, ended_at, duration_seconds, participants, language_code (no content). Paginated (count default 100, max 200; offset). order_by ranks within the window. NOTE: `participants` are speaker labels — placeholders ('Speaker A/B') unless the user tagged them, not necessarily real names.

Input parameters:

- `count` (integer): page size (default 100, max 200)
- `desc` (boolean): true = descending (default); false = ascending.
- `end_time` (string): ISO 8601, filters on started_at
- `offset` (integer): page offset; use the response's next_offset
- `order_by` (string): duration_seconds | started_at | action_item_count — server sorts the whole window and returns the top `count`.
- `participant_names` (array): Exact participant filter (may return 0 for un-tagged/anonymized people).
- `start_time` (string): ISO 8601, filters on started_at

Output parameters:

- `result`: Tool-specific result payload; shape varies per tool (object for most; may be null/array/text for some). Intentionally type-unconstrained for strict-validating clients.
- `took_ms` (integer)
- `tool` (string)

### `search_recordings` (~215 tokens)

[search] Unified recording search. Runs bounded searches over transcript lines, topic segments, memory atoms, participant metadata, titles, briefs, summaries, and action items in one call. Returns typed hits plus conversation_ids, line_ids, segment_ids, memory_atom_ids, participant_ids, brief_ids, summary_ids, action_item_ids. Chat execution expands hits into readable evidence automatically; external callers can fetch returned ids where a matching fetcher is advertised.

Input parameters:

- `conversation_ids` (array): Optional: restrict to these opaque recording ids.
- `end_time` (string): ISO 8601; filters by recording started_at.
- `query` (string): Required. One phrase for a single concept, or a JSON array string of 2-4 distinct facets.
- `search_types` (array): Optional lane filter. Omit to search all. Allowed: transcript, segment, memory_atom, participant, title, brief, summary, action_item.
- `start_time` (string): ISO 8601; filters by recording started_at.

Output parameters:

- `result`: Tool-specific result payload; shape varies per tool (object for most; may be null/array/text for some). Intentionally type-unconstrained for strict-validating clients.
- `took_ms` (integer)
- `tool` (string)

### `get_conversations` (~65 tokens)

[metadata_query] Conversation-level metadata for the given conversation_ids: id, title, started_at, ended_at, duration_seconds, participants, language_code. No transcript, brief, or summary body.

Input parameters:

- `conversation_ids` (array): required, non-empty; opaque recording ids

Output parameters:

- `result`: Tool-specific result payload; shape varies per tool (object for most; may be null/array/text for some). Intentionally type-unconstrained for strict-validating clients.
- `took_ms` (integer)
- `tool` (string)

### `get_transcripts_by_participant` (~82 tokens)

[content_fetch] Transcript lines associated with participant_ids in conversation_ids. Turns participant metadata into transcript evidence for exposed search results.

Input parameters:

- `conversation_ids` (array): recording ids scoped by participant hits
- `limit` (integer)
- `participant_ids` (array): participant ids from search_recordings.participant_ids
- `query` (string)

Output parameters:

- `result`: Tool-specific result payload; shape varies per tool (object for most; may be null/array/text for some). Intentionally type-unconstrained for strict-validating clients.
- `took_ms` (integer)
- `tool` (string)

### `get_brief` (~82 tokens)

[content_fetch] Per-conversation compact report body for the given conversation_ids using Brief -> Summary -> Standard, where Standard is the first completed non-empty type=0 report.

Input parameters:

- `brief_ids` (array): optional brief ids from search_recordings.brief_ids
- `conversation_ids` (array): recording ids from brief hits
- `offset` (integer)

Output parameters:

- `result`: Tool-specific result payload; shape varies per tool (object for most; may be null/array/text for some). Intentionally type-unconstrained for strict-validating clients.
- `took_ms` (integer)
- `tool` (string)

### `get_summaries` (~101 tokens)

[content_fetch] Per-conversation summary body. With summary_ids, fetch exact summary reports from search_recordings. With conversation_ids only, fetch the latest summary report for each conversation. Paginated (offset).

Input parameters:

- `conversation_ids` (array): required, non-empty; ids are opaque strings (may be 19-digit snowflake)
- `offset` (integer)
- `summary_ids` (array): optional summary ids from search_recordings.summary_ids

Output parameters:

- `result`: Tool-specific result payload; shape varies per tool (object for most; may be null/array/text for some). Intentionally type-unconstrained for strict-validating clients.
- `took_ms` (integer)
- `tool` (string)

### `get_transcripts` (~65 tokens)

[content_fetch] Verbatim transcript of ONE recording by conversation_id. Paginated (offset / next_offset) — page through for more.

Input parameters:

- `conversation_id` (string): required; opaque id string (may be 19-digit snowflake)
- `offset` (integer)

Output parameters:

- `result`: Tool-specific result payload; shape varies per tool (object for most; may be null/array/text for some). Intentionally type-unconstrained for strict-validating clients.
- `took_ms` (integer)
- `tool` (string)

## Diagnostics

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

## Score history

- 2026-08-03: 75
- 2026-08-02: 73
- 2026-08-01: 72
- 2026-07-31: 72
- 2026-07-30: 68
- 2026-07-29: 69
- 2026-07-28: 68
- 2026-07-27: 67
- 2026-07-26: 66

## Links

- Remote endpoint: https://mcp.memoket.ai/mcp
- Repository: https://github.com/memoket/memoket-backend-go
- Changelog RSS feed: https://verifymcp.io/servers/ai-memoket-memoket/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-memoket-memoket/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-memoket-memoket/mcp