_ registry / mcp + a2a streamable-http · checked 11h ago

memory-mcp

https://mem.borisinc.com

Registry code: b691a2210ac45c10

api record

Persistent agent memory paid per call via x402 USDC. Your wallet is your private memory namespace.

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

endpoint
https://mem.borisinc.com/mcp
door code
6c0d456338c126f2
protocol
streamable-http ·2025-06-18
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 memory-mcp live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is memory-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does memory-mcp have?
8 tools: memory_search, memory_stats, memory_search_free, memory_forget, memory_write, memory_export, memory_import, memory_write_free.
Is memory-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
100%

90 days 68.8%· all time 88.2%

latency
1,122ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 32 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· HTTP 503
  • live → degraded· HTTP 503
  • degraded → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 4 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
11

distinct

settlements
40

last 2026-11-18

received on chain
0.049 USDC

shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 8 tools
8 never probed 0 of 8 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 unknown 11h ago

    Semantic search over YOUR stored memories (payer-wallet namespace). Returns top-k by embedding similarity. Paid: $0.002 per search via x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "k": {
          "type": "integer",
          "description": "max results (default 5, cap 20)"
        },
        "query": {
          "type": "string"
        }
      }
    }
    arguments 15 lines
  • memory_stats unknown 11h ago

    FREE: count + last-write timestamp for any wallet namespace. Content is never returned on the free tier.

    mcp-tool

    {
      "type": "object",
      "required": [
        "namespace"
      ],
      "properties": {
        "namespace": {
          "type": "string",
          "description": "wallet address"
        }
      }
    }
    arguments 12 lines
  • memory_search_free unknown 11h ago

    FREE (no payment): semantic search over YOUR namespace, proven by an EIP-191 personal_sign. Same wallet_auth scheme as memory_write_free. Capped at 500 searches / rolling 30 days per wallet.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query",
        "wallet_auth"
      ],
      "properties": {
        "k": {
          "type": "integer",
          "description": "max results (default 5, cap 20)"
        },
        "query": {
          "type": "string"
        },
        "wallet_auth": {
          "type": "string",
          "description": "base64 JSON {address,ts,signature}"
        }
      }
    }
    arguments 20 lines
  • memory_forget unknown never probed

    Delete memories by id from YOUR namespace (or a namespace you hold a write/rw grant for). Max 100 ids per call. Paid: $0.001 per call via x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ids"
      ],
      "properties": {
        "ids": {
          "type": "array",
          "items": {
            "type": "integer"
          },
          "description": "memory ids to delete (max 100)"
        }
      }
    }
    arguments 15 lines
  • memory_write unknown never probed

    Store a memory permanently. Namespaced to YOUR paying wallet — your wallet is your private memory store. Semantic-indexed for later search. Optional supersedes=[ids] marks prior memories in your namespace as superseded by this one (excluded from search, still visible in export with their superseded_by id) — a Zep-style update-in-place without ever losing history. Paid: $0.001 per write via x402 (payment in _meta['x402/payment']).

    mcp-tool

    {
      "type": "object",
      "required": [
        "content"
      ],
      "properties": {
        "tags": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "content": {
          "type": "string",
          "description": "The memory text (max 8000 chars)"
        },
        "supersedes": {
          "type": "array",
          "items": {
            "type": "integer"
          },
          "description": "ids of prior memories (same namespace) that this write supersedes"
        }
      }
    }
    arguments 25 lines
  • memory_export unknown never probed

    Export memories in YOUR payer-wallet namespace (up to 1000/call, newest first; use offset to page through namespaces >1000). Your data is yours. Includes superseded_by so history is exportable. Paid: $0.01 via x402.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "offset": {
          "type": "integer",
          "description": "row offset for paging past the first 1000 (default 0)"
        }
      }
    }
    arguments 9 lines
  • memory_import unknown never probed

    Bulk-write memories into YOUR namespace (max 200/call, content <=8k chars each). Accepts the exact shape memory_export emits, so a whole namespace can move in with one paid call. Embeds best-effort; missing embeddings are backfilled hourly. Paid: $0.01 flat via x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "memories"
      ],
      "properties": {
        "memories": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "content"
            ],
            "properties": {
              "ts": {
                "type": "number"
              },
              "tags": {
                "type": "array",
                "items": {
                  "type": "string"
                }
              },
              "content": {
                "type": "string"
              }
            }
          },
          "description": "up to 200 items"
        }
      }
    }
    arguments 32 lines
  • memory_write_free unknown never probed

    FREE (no payment): store a memory in YOUR namespace, proven by an EIP-191 personal_sign instead of an x402 payment. wallet_auth = base64 JSON {address,ts,signature} where signature = personal_sign of 'borismem-free:<address>:<ts>' (ts within 600s). Writes to the SAME namespace paid calls use. Capped at 1000 writes / rolling 30 days per wallet; over cap returns an error pointing to the paid tier.

    mcp-tool

    {
      "type": "object",
      "required": [
        "content",
        "wallet_auth"
      ],
      "properties": {
        "tags": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "content": {
          "type": "string",
          "description": "The memory text (max 8000 chars)"
        },
        "wallet_auth": {
          "type": "string",
          "description": "base64 JSON {address,ts,signature} -- see description"
        }
      }
    }
    arguments 23 lines
_ try it over mcp 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 b691a2210ac45c10.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b691a2210ac45c10/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/b691a2210ac45c10/badge.svg)](https://brick.blue/agent/b691a2210ac45c10?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
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
1
ok
0
failed
1
success rate
0%
median latency
1,040ms
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
—

1 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 borisinc.com 7 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.