memorysync-docs
Registry code: f9f75ae1641faf90
Search the MemorySync documentation before writing MemorySync integration code. Prefer read_doc over a search snippet when you need exact method names, parameters or limits. If the documentation and your prior knowledge disagree, the documentation is correct.
- endpoint
- https://docs.memorysync.io/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 memorysync-docs live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 96% of checks over the last 30 days.
- Is memorysync-docs free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does memorysync-docs have?
- 3 tools: search_docs, read_doc, list_doc_sections.
- Is memorysync-docs 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.
90 days 97.5%· all time 97.5%
last good check
of 3 tools
- down → live
- degraded → down· HTTP 402: vercel DEPLOYMENT_DISABLED
- live → degraded· HTTP 402: vercel DEPLOYMENT_DISABLED
- degraded → live
- live → degraded· HTTP 402: vercel DEPLOYMENT_DISABLED
- used for
- search memory sdk documentation
- read a documentation page
- list documentation sections
- takes → gives
- text → text
- tools
- 3 reads
- note
- documentation mirror
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.
through this hub
successful
what callers paid
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_doc_sections reads open 16h ago
List the top-level documentation sections and how many pages each contains, to orient before searching.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linessearch_docs reads unknown 16h ago
Search the MemorySync documentation and return matching pages with their headings and a link to the full Markdown text.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 5, "maximum": 20, "minimum": 1, "description": "Maximum pages to return (1-20)." }, "query": { "type": "string", "description": "What to search for, in natural language or keywords." } }, "additionalProperties": false }arguments 20 linesread_doc reads unknown 16h ago
Read the full Markdown text of one documentation page. Prefer this over a search snippet when you need exact method names, parameters, fields or limits.
{ "type": "object", "required": [ "path" ], "properties": { "path": { "type": "string", "description": "Page path such as '/quickstart' or '/api/memory/add', or its full URL." } }, "additionalProperties": false }arguments 13 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf9f75ae1641faf90.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f9f75ae1641faf90/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f9f75ae1641faf90?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.
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.
- mcp.memorysync.io mcp.memorysync.io