_ registry / mcp http-sse · checked 10m ago

memoket-mcp

https://mcp.memoket.ai

Registry code: 20801588716ec618

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.memoket.ai/mcp
protocol
http-sse ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is memoket-mcp live?
Yes — it answered the hub's last check (checked 10m ago). It answered 99% of checks over the last 30 days.
Is memoket-mcp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does memoket-mcp have?
7 tools: get_conversations, get_summaries, get_transcripts_by_participant, search_recordings, get_transcripts, get_brief, list_conversations.
Is memoket-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 97.8%· all time 97.8%

latency
715ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 543 checks · signed record
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
  • degraded → live
  • live → degraded· HTTP 502
_ what it is for
used for
  • search recording transcripts
  • get conversation summaries
  • get a verbatim transcript
  • list recorded conversations
takes → gives
text → text, data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
7 auth-required 7 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_conversations reads auth-required 5h ago

    [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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "conversation_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "required, non-empty; opaque recording ids"
        }
      }
    }
    arguments 12 lines
  • get_summaries reads auth-required 13h ago

    [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).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "offset": {
          "type": "integer"
        },
        "summary_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "optional summary ids from search_recordings.summary_ids"
        },
        "conversation_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "required, non-empty; ids are opaque strings (may be 19-digit snowflake)"
        }
      }
    }
    arguments 22 lines
  • get_transcripts_by_participant reads auth-required 13h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer"
        },
        "query": {
          "type": "string"
        },
        "participant_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "participant ids from search_recordings.participant_ids"
        },
        "conversation_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "recording ids scoped by participant hits"
        }
      }
    }
    arguments 25 lines
  • search_recordings reads auth-required 22h ago

    [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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Required. One phrase for a single concept, or a JSON array string of 2-4 distinct facets."
        },
        "end_time": {
          "type": "string",
          "description": "ISO 8601; filters by recording started_at."
        },
        "start_time": {
          "type": "string",
          "description": "ISO 8601; filters by recording started_at."
        },
        "search_types": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional lane filter. Omit to search all. Allowed: transcript, segment, memory_atom, participant, title, brief, summary, action_item."
        },
        "conversation_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional: restrict to these opaque recording ids."
        }
      }
    }
    arguments 31 lines
  • get_transcripts reads auth-required 13h ago

    [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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "offset": {
          "type": "integer"
        },
        "text_offset": {
          "type": "integer",
          "description": "Character offset inside the first line; use returned next_text_offset, default 0."
        },
        "conversation_id": {
          "type": "string",
          "description": "required; opaque id string (may be 19-digit snowflake)"
        }
      }
    }
    arguments 16 lines
  • get_brief reads auth-required 5h ago

    [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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "offset": {
          "type": "integer"
        },
        "brief_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "optional brief ids from search_recordings.brief_ids"
        },
        "conversation_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "recording ids from brief hits"
        }
      }
    }
    arguments 22 lines
  • list_conversations reads auth-required 5h ago

    [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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "desc": {
          "type": "boolean",
          "description": "true = descending (default); false = ascending."
        },
        "count": {
          "type": "integer",
          "description": "page size (default 100, max 200)"
        },
        "offset": {
          "type": "integer",
          "description": "page offset; use the response's next_offset"
        },
        "end_time": {
          "type": "string",
          "description": "ISO 8601, filters on started_at"
        },
        "order_by": {
          "type": "string",
          "description": "duration_seconds | started_at | action_item_count — server sorts the whole window and returns the top `count`."
        },
        "start_time": {
          "type": "string",
          "description": "ISO 8601, filters on started_at"
        },
        "participant_names": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Exact case-insensitive filter on stored tagged participant names. Use when participant-field membership is requested; un-tagged or anonymized people do not match."
        }
      }
    }
    arguments 36 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 20801588716ec618.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/20801588716ec618/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/20801588716ec618/badge.svg)](https://brick.blue/agent/20801588716ec618?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.