_ registry / mcp + a2a JSONRPC · checked 2h ago

StudioMeyer Memory

listed under this name in a public catalogue; the server gives only its address, memory.studiomeyer.io

https://memory.studiomeyer.io

Registry code: 923e6ba888d8aeb9

api record

AI memory server with 52 tools. Knowledge Graph, semantic search, multi-agent.

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

endpoint
https://memory.studiomeyer.io/mcp
door code
01dcdc947cc4e4bb
protocol
JSONRPC ·0.3
authentication
bearer
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 StudioMeyer Memory live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is StudioMeyer Memory 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 StudioMeyer Memory have?
10 tools: Search across all memory, Session start, end, replay, Provider-agnostic memory backend, Analytics, insights, contradictions, decay, Track which patterns work, Persist learnings and decisions, Knowledge graph entity tracking, Import ChatGPT, Claude, Gemini history, ….
Is StudioMeyer Memory 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
100%

90 days 99.5%· all time 99.5%

latency
149ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 804 checks · signed record
  • down → live
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
ai & agents memory & context
used for
  • store memories in knowledge graph
  • search memories semantically
takes → gives
text → data
_ 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 10 tools
10 auth-required 10 of 10 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.

  • memory-search auth-required never probed

    Unified search with temporal decay across decisions, learnings, sessions, skills, evolution, entity observations. Trigram + full-text + LIKE. Recent memories rank higher.

    memorysearchrecallrrftemporal

  • session-continuity auth-required never probed

    Auto-loaded context on session start, structured summaries on session end, full session replay with timeline visualization. Sessions persist across multiple AI conversations.

    sessionscontinuityreplaytimeline

  • multi-llm-memory auth-required never probed

    Connect through an MCP-capable AI client or a REST integration such as n8n. Model support depends on your client; Memory provides the storage and search layer.

    multi-llmagnosticmcpbyo-llm

  • analytics-insights auth-required never probed

    Knowledge graph health analytics, contradiction detection, learning decay (forgetting curve), proactive suggestions, communities clustering, deduplication, synthesis from learning clusters.

    analyticsinsightshealthcommunities

  • skill-tracking auth-required never probed

    Skill registry with success/failure tracking per domain. Recipe lookup returns the best tool-chain for a task based on past experience.

    skillspatternsrecipes

  • learn-and-decide auth-required never probed

    Store typed learnings (pattern, mistake, insight, research, architecture, infrastructure, tool, workflow, performance, security) with built-in duplicate-prevention gatekeeper. Log decisions with confidence scores and alternatives.

    memorylearndecidegatekeeper

  • knowledge-graph auth-required never probed

    Bi-temporal knowledge graph with entities, observations, relations. Time-travel queries via asOf parameter. Entity merge, deep-search, history, communities. 56 tools total in MCP surface.

    knowledge-graphentitiesbi-temporalobservations

  • memory-import auth-required never probed

    Bulk import conversation history from ChatGPT, Claude.ai, Gemini exports. Auto-extracts learnings, entities, and relations into the knowledge graph.

    importchatgptclaudegeminimigration

  • visualization-graph auth-required never probed

    Cinema-mode 3D-Force-Graph rendering of the knowledge graph with time-travel slider and session-replay timeline. Available as MCP Apps UI resources for clients that support sandboxed iframes (Claude.ai, VS Code Copilot, Goose, Postman, MCPJam).

    visualization3dmcp-appstime-travel

  • tenant-isolation auth-required never probed

    Shared PostgreSQL tables with tenant-scoped application queries. Storage at Hetzner Nuremberg (Germany, EU). AI features may send relevant content to configured model providers; EU storage does not imply EU-only model processing. Bearer API key + OAuth 2.1 + Magic Link auth.

    multi-tenanttenant-scopingoauth-2.1eu-storage

_ try it over a2a 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 923e6ba888d8aeb9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/923e6ba888d8aeb9/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/923e6ba888d8aeb9/badge.svg)](https://brick.blue/agent/923e6ba888d8aeb9?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 knowoff the mcp door
card completeness
20%

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.

_ also on studiomeyer.io 4 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.