polymnemo
REMOTE · POLYMNEMO.PURPLEGROUND-26F6D744.WESTUS2.AZURECONTAINERAPPS.IO
Shared cross-LLM long-term memory over MCP: semantic recall, sessions, and media (pgvector).
Available components
Last scanned (3 hours ago)
Scores higher than 26% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +14
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → pass ▲ security
- 21 Oct 26 −14
- HSTS header: fail → unverified ▼ security
- Authorization: pass → unverified ▼ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 14 Sept 26 0
- Server version: 1.1.3 → 1.1.4 functional
- 13 Sept 26 0
- Server version: 1.1.1 → 1.1.3 functional
- 12 Sept 26 0
- Server version: 1.0.1 → 1.1.1 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=purpleground-26f6d744.westus2.azurecontainerapps.io,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 10,O=Microsoft Corporation,C=US | 25 Oct 2026 | 2 Feb 2027 | RSA 2048 | SHA384-RSA | 49014b2fd3fe18edf99f64e5df0000014b2fd3 |
| SANs: *.purpleground-26f6d744.westus2.azurecontainerapps.io, *.scm.purpleground-26f6d744.westus2.azurecontainerapps.io, *.internal.purpleground-26f6d744.westus2.azurecontainerapps.io, *.ext.purpleground-26f6d744.westus2.azurecontainerapps.io, purpleground-26f6d744.westus2.azurecontainerapps.io | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 10,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000f33206537ee42ae4f00000000000f |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| azurecontainerapps.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer scope="user", resource_metadata="https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/.well-known/oauth-protected-resource/mcp"
Bearer scope="user", resource_metadata="https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer scope="user", resource_metadata="https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/mcp |
| Authorisation server | https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/mcp | Auth required | 401 | |
| http (plaintext) | http://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/mcp | HTTPS enforced | 301 | https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
confirm_upload Confirm Upload ~86
Confirm a media upload after you've PUT the bytes. Verifies the object exists, records its real size + checksum (and rejects an over-limit upload), then makes the memory findable via `recall` / downloadable. `id` is from `create_upload`. Returns `{memory_id, confirmed, size_bytes, content_type}`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_upload Create Upload ~160
Register a file / image / video memory and get a URL to upload its bytes. The bytes never go through this channel: `description` is embedded so the file is findable via `recall`. **PUT** the raw bytes to `upload_url` sending `upload_headers` (the signed Content-Type). **Then call `confirm_upload`** — the memory stays hidden from `recall` (and the size cap is enforced) until you do. Media defaults to a private namespace. Returns `{memory_id, object_key, upload_url, upload_headers, content_type, namespace}`.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | yes | – |
| description | string | yes | – |
| filename | string | yes | – |
| namespace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
forget Forget ~32
Delete a memory by id. Returns `{id, deleted}` (deleted=false if absent).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_download_url Get Download Url ~62
Get a short-lived URL to download a media memory's bytes. `id` is the media memory's id (from `create_upload` / `recall`). Returns `{memory_id, url, content_type}`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_memory Get Memory ~39
Fetch a single memory by its id (from `remember`/`recall`/`list_memories`).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_memories List Memories ~74
List stored memories newest-first (no search query). `namespace` selects the collection (defaults to the shared namespace). Page with `next_cursor` / `has_more`. Returns `{items, total, has_more, next_cursor}`.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
| namespace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
load_session Load Session ~83
Reload a saved session's content, one character page at a time. Page with `page` (0-based) while `has_more` is true. Returns `{session_id, content, page, page_size, total_chars, has_more}`.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| page_size | integer | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ping Ping ~45
Health / connectivity check. Returns server identity plus the active pluggable layers, so a client (or MCP Inspector) can confirm the connection and see how the server is wired.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
recall Recall ~110
Search memories by meaning and return the closest matches. Results are ranked by similarity and bounded by `limit` (default 8). Use the returned `next_cursor` with `has_more` to page further — you decide whether the results are enough. `namespace` selects the collection (defaults to the shared namespace). Returns `{items, total, has_more, next_cursor}`.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
| namespace | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
remember Remember ~92
Store a memory for later semantic recall. Large content is split into smaller chunks on write (one vector each), so this may create several ids. `namespace` groups memories (defaults to the shared namespace); `tags`/`source` are optional metadata. Returns `{ids, chunks, namespace}`.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| namespace | – | – | – |
| source | – | – | – |
| tags | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
save_session Save Session ~90
Persist a session's full content under `session_id` for later reload. Content is stored as ordered, losslessly-reassemblable chunks (also embedded, so it's searchable via `recall`). Re-saving the same `session_id` replaces it. Returns `{session_id, chunks, chars, namespace}`.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| namespace | – | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update Update ~38
Replace a memory's content (re-embeds it). Returns the updated memory.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the polymnemo MCP server?
polymnemo is a hosted endpoint at https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io
claude mcp add --transport http pcbz-polymnemo 'https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/mcp'
What is the polymnemo MCP server?
polymnemo is an MCP server listed in the public MCP registry as io.github.PCBZ/polymnemo. Shared cross-LLM long-term memory over MCP: semantic recall, sessions, and media (pgvector). This page covers its hosted endpoint (https://polymnemo.purpleground-26f6d744.westus2.azurecontainerapps.io/mcp).
Is the polymnemo MCP server safe to use?
polymnemo scores 37 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the polymnemo MCP server expose?
polymnemo exposes 12 tools: ping, remember, recall, list_memories, get_memory, and 7 more. Their descriptions and schemas cost roughly 911 tokens of context every time the server is loaded.
Does the polymnemo MCP server require authentication?
Yes. polymnemo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the polymnemo MCP server still maintained?
polymnemo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.