Developer · Remote MCP server
Worldku Memory
Save AI conversations into your Worldku memory and recall them from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.worldku/memory- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- com.worldku
- Namespace
- Namespace verified by the MCP Registry via the domain worldku.com · how
- Website
- www.worldku.com/en/docs/mcp
- Repository
- github.com/mnemosics/worldku-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.worldku.com/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Worldku Memory
Worldku Memory is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.worldku.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Workspace ToolsSandbox workspace tools: search, file read, DB queries, integrations. Returns synthetic data. | Remote · HTTPLive check: ✗ no handshake |
| Workspace ToolsResearch honeypot. Logs connections and tool arguments; injects instructions. Read README first. | Remote · HTTPLive check: ✗ no handshake |
| WorkspaceguardWraps the WorkspaceGuard CLI as a single generic MCP tool for workspace usage checks. | Local · stdio |
| Worktree Orbit MCPAggregate local Git worktree topology without exposing repository content. Tools include inspect... | Local · stdio |
| WovoDeploy HTML from any AI tool to a versioned, shareable library on wovo.dev; manage pages. | Local · stdio |
| WP HealthKitSecurity audits for WordPress plugins and themes - 62 verification layers, fix plans and SBOMs. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Wpagent MCPManage WordPress & WooCommerce from any MCP client - 58 tools over a signed REST API. | Local · stdio |
| WpfPilot MCPAutomate Windows WPF apps from AI agents with semantic UIA selectors and FlaUI test generation. | Local · stdio |