You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: servers/mcp-neo4j-memory/README.md
+128Lines changed: 128 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,6 +195,134 @@ The server supports three transport modes:
195
195
}
196
196
```
197
197
198
+
## 🔒 Security Protection
199
+
200
+
The server includes comprehensive security protection with **secure defaults** that protect against common web-based attacks while preserving full MCP functionality when using HTTP transport.
201
+
202
+
### 🛡️ DNS Rebinding Protection
203
+
204
+
**TrustedHost Middleware** validates Host headers to prevent DNS rebinding attacks:
205
+
206
+
**Secure by Default:**
207
+
- Only `localhost` and `127.0.0.1` hosts are allowed by default
- Be specific: `["https://example.com", "https://example.com"]`
243
+
- Never use `"*"` in production with credentials
244
+
- Use HTTPS origins in production
245
+
246
+
**For `allowed_hosts`:**
247
+
- Include your actual domain: `["example.com", "www.example.com"]`
248
+
- Include localhost only for development
249
+
- Never use `"*"` unless you understand the risks
250
+
251
+
## 🐳 Docker Deployment
252
+
253
+
The Neo4j Memory MCP server can be deployed using Docker for remote deployments. Docker deployment should use HTTP transport for web accessibility. In order to integrate this deployment with applications like Claude Desktop, you will have to use a proxy in your MCP configuration such as `mcp-remote`.
254
+
255
+
### 📦 Using Your Built Image
256
+
257
+
After building locally with `docker build -t mcp-neo4j-memory:latest .`:
0 commit comments