_ registry / mcp streamable-http · checked 1h ago

run-memory

https://memory.cloudforbots.com

Registry code: 3f8f05dedc63c20f

api record

Checkpoint and resume for AI agent runs. Save state after each step; when a run crashes, resume hands back the last step, state and finished items so it picks up where it left off instead of starting over. Free watch-only mode shows exactly what would be saved; Pro at $9 a month saves and resumes. Free 500 calls/day, then $9/month. No model inside: bring your own model. Works with Claude, Codex, ChatGPT, Grok Bot.

endpoint
https://memory.cloudforbots.com/mcp
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 run-memory live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is run-memory free to use?
Yes — the hub reached it with no key and no payment.
What tools does run-memory have?
5 tools: weekly_report, save_checkpoint, resume, usage_and_upgrade, list_checkpoints.
Is run-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 100%· all time 100%

latency
370ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
1 open 4 never probed 1 of 5 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.

  • list_checkpoints open 1h ago

    List recent checkpoints (step, size, time) for one run or all runs on your key.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "run_id": {
      "type": "string",
      "description": "A stable id for this job that survives a crash, e.g. \"invoice-import-oct\". Use the same id when you restart."
    }
  }
}
    arguments 9 lines
  • weekly_report unknown never probed

    Draft a plain-English report of the last 7 days: runs, checkpoints saved (Pro) or that would have been saved (free). Read-only; sends nothing.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • save_checkpoint unknown never probed

    Call after each completed step with the state you would need to continue (cursor, ids done, partial results; up to 256 KB JSON). Pro saves it (last 20 per run, kept 30 days). Free watch-only saves nothing and returns would_save: exactly what would have been stored. Never put passwords or API keys in state.

    mcp-tool

    {
  "type": "object",
  "required": [
    "run_id",
    "step",
    "state"
  ],
  "properties": {
    "done": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional list of completed item ids, so a resume skips them."
    },
    "step": {
      "type": "string",
      "description": "The step you just finished, e.g. \"imported page 3 of 10\"."
    },
    "state": {
      "type": "object",
      "description": "JSON state needed to resume."
    },
    "run_id": {
      "type": "string",
      "description": "A stable id for this job that survives a crash, e.g. \"invoice-import-oct\". Use the same id when you restart."
    }
  }
}
    arguments 29 lines
  • resume unknown never probed

    Call FIRST when a run starts. If a checkpoint exists for run_id (Pro), returns the last step, state and done list: continue from there and skip finished work. If none, start fresh.

    mcp-tool

    {
  "type": "object",
  "required": [
    "run_id"
  ],
  "properties": {
    "run_id": {
      "type": "string",
      "description": "A stable id for this job that survives a crash, e.g. \"invoice-import-oct\". Use the same id when you restart."
    }
  }
}
    arguments 12 lines
  • usage_and_upgrade unknown never probed

    Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 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 3f8f05dedc63c20f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3f8f05dedc63c20f/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/3f8f05dedc63c20f/badge.svg)](https://brick.blue/agent/3f8f05dedc63c20f?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
90%

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 cloudforbots.com 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.