Search and read the current MemorySync documentation while writing integration code.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://docs.memorysync.io/mcp3 tools · 264mssearch_docsSearch the MemorySync documentation and return matching pages with their headings and a link to the full Markdown text.Search the MemorySync documentation and return matching pages with their headings and a link to the full Markdown text.
| Parameter | Type | Description |
|---|---|---|
| query* | string | What to search for, in natural language or keywords. |
| limit | integer | Maximum pages to return (1-20). |
read_docRead the full Markdown text of one documentation page. Prefer this over a search snippet when you need exact method names, parameters, fields or limits.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.
| Parameter | Type | Description |
|---|---|---|
| path* | string | Page path such as '/quickstart' or '/api/memory/add', or its full URL. |
list_doc_sectionsList the top-level documentation sections and how many pages each contains, to orient before searching.List the top-level documentation sections and how many pages each contains, to orient before searching.
No input schema was published for this tool.
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Search and read the current MemorySync documentation while writing integration code.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.