ai.memoket/memoket
REMOTE · MCP.MEMOKET.AI · SCANNED SEP 21
Memoket — access your recording transcripts, summaries, and key takeaways over MCP.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 889 tokens (~127/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the ai.memoket/memoket MCP server?
ai.memoket/memoket is a hosted endpoint at https://mcp.memoket.ai/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.
remote · mcp.memoket.ai
claude mcp add --transport http ai-memoket-memoket 'https://mcp.memoket.ai/mcp'
{
"mcpServers": {
"ai-memoket-memoket": {
"url": "https://mcp.memoket.ai/mcp"
}
}
} {
"servers": {
"ai-memoket-memoket": {
"type": "http",
"url": "https://mcp.memoket.ai/mcp"
}
}
} [mcp_servers.ai-memoket-memoket] url = "https://mcp.memoket.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-memoket-memoket": {
"type": "remote",
"url": "https://mcp.memoket.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-memoket-memoket --url 'https://mcp.memoket.ai/mcp' --transport streamable-http
mcp_servers:
ai-memoket-memoket:
url: "https://mcp.memoket.ai/mcp" {
"McpServers": {
"ai-memoket-memoket": {
"Transport": "http",
"Url": "https://mcp.memoket.ai/mcp"
}
}
} assistant mcp add ai-memoket-memoket -t streamable-http -u 'https://mcp.memoket.ai/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- Tool “get_transcripts” rewrote its description, which is the text the model reads security
- “get_transcripts” added an optional parameter “text_offset” cosmetic
- 4 Sept 26 0
- “list_conversations” reworded the description of “participant_names” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Aug 26 0
- Schema quality: fair → good functional
- 1 Aug 26 0
- Schema quality: good → fair functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://mcp.memoket.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.memoket.ai | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 11 Sept 2026 | 27 Mar 2027 | RSA 2048 | SHA256-RSA | 10947150090af82b2cdb1e0d9cb8a98 |
| SANs: *.memoket.ai | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.memoket.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| memoket.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.memoket.ai/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.memoket.ai/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.memoket.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.memoket.ai/mcp |
| Authorisation server | https://api.memoket.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.memoket.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.memoket.ai/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_brief ~82
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| brief_ids | array | – | optional brief ids from search_recordings.brief_ids |
| conversation_ids | array | – | recording ids from brief hits |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | 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 | yes | – |
No examples provided.
get_conversations ~65
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_ids | array | – | required, non-empty; opaque recording ids |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | 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 | yes | – |
No examples provided.
get_summaries ~101
[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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | 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 | yes | – |
No examples provided.
get_transcripts ~105
[content_fetch] Verbatim transcript of ONE recording; at most 100 lines / 4000 characters per page. Resume using both next_offset and next_text_offset from the returned item, including within a long line.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | – | required; opaque id string (may be 19-digit snowflake) |
| offset | integer | – | – |
| text_offset | integer | – | Character offset inside the first line; use returned next_text_offset, default 0. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | 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 | yes | – |
No examples provided.
get_transcripts_by_participant ~82
[content_fetch] Transcript lines associated with participant_ids in conversation_ids. Turns participant metadata into transcript evidence for exposed search results.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_ids | array | – | recording ids scoped by participant hits |
| limit | integer | – | – |
| participant_ids | array | – | participant ids from search_recordings.participant_ids |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | 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 | yes | – |
No examples provided.
list_conversations ~239
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 case-insensitive filter on stored tagged participant names. Use when participant-field membership is requested; un-tagged or anonymized people do not match. |
| start_time | string | – | ISO 8601, filters on started_at |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | 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 | yes | – |
No examples provided.
search_recordings ~215
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | 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 | yes | – |
No examples provided.
What is the ai.memoket/memoket MCP server?
ai.memoket/memoket is an MCP server listed in the public MCP registry as ai.memoket/memoket. Memoket, access your recording transcripts, summaries, and key takeaways over MCP. This page covers its hosted endpoint (https://mcp.memoket.ai/mcp).
Is the ai.memoket/memoket MCP server safe to use?
ai.memoket/memoket scores 88 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 ai.memoket/memoket MCP server expose?
ai.memoket/memoket exposes 7 tools: get_transcripts_by_participant, get_brief, get_summaries, get_transcripts, list_conversations, and 2 more. Their descriptions and schemas cost roughly 889 tokens of context every time the server is loaded.
Does the ai.memoket/memoket MCP server require authentication?
Yes. ai.memoket/memoket 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 ai.memoket/memoket MCP server still maintained?
ai.memoket/memoket is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.