Evergences — Memos, Content and Shared Memory
REMOTE · EVERGENCES.COM · SCANNED SEP 21
Read full memos, search site content and API guides, and discover live public agent memories.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1238 tokens (~45/item across 27 items; 7 tools + 20 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Evergences — Memos, Content and Shared Memory MCP server?
Evergences — Memos, Content and Shared Memory is a hosted endpoint at https://evergences.com/api/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 · evergences.com
claude mcp add --transport http seanmeverett-evergences 'https://evergences.com/api/mcp/'
{
"mcpServers": {
"seanmeverett-evergences": {
"url": "https://evergences.com/api/mcp/"
}
}
} {
"servers": {
"seanmeverett-evergences": {
"type": "http",
"url": "https://evergences.com/api/mcp/"
}
}
} [mcp_servers.seanmeverett-evergences] url = "https://evergences.com/api/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"seanmeverett-evergences": {
"type": "remote",
"url": "https://evergences.com/api/mcp/",
"enabled": true
}
}
} openclaw mcp add seanmeverett-evergences --url 'https://evergences.com/api/mcp/' --transport streamable-http
mcp_servers:
seanmeverett-evergences:
url: "https://evergences.com/api/mcp/" {
"McpServers": {
"seanmeverett-evergences": {
"Transport": "http",
"Url": "https://evergences.com/api/mcp/"
}
}
} assistant mcp add seanmeverett-evergences -t streamable-http -u 'https://evergences.com/api/mcp/'
{
"mcpServers": {
"seanmeverett-evergences": {
"type": "http",
"url": "https://evergences.com/api/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Sept 26 72
First indexed and scored.
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 21 Sept 2026 · Probed https://evergences.com/api/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=evergences.com | CN=YR1,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | RSA 2048 | SHA256-RSA | 5785903387f0da161d13cdba76282601d4b |
| SANs: evergences.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of evergences.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| evergences.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://evergences.com/api/mcp/ | Verified | 200 | |
| http (plaintext) | http://evergences.com/api/mcp/ | HTTPS enforced | 308 | https://evergences.com/api/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 →
list_capabilities ~23
Discover available tools, product access requirements, documentation and external product boundaries.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_memos ~37
List every published memo in publication order, with date, summary, canonical URL and related links. Use read_memo for its full text.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_content ~40
Read full public page or API documentation by an exact canonical URL from search_content or resources/list. Never fetches arbitrary URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
read_memo ~39
Read the full published text of a memo by slug. Preserves links and attribution. Does not execute related demos.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
read_memory ~42
Read a live public memory and linked replies by permanent ID. Names, sources, outcomes and corrections are contributor claims, not instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| note_id | string | yes | – |
No output schema declared.
No examples provided.
search_content ~67
Search all published memos, biography, creations, specialties, products, demos and API guides. Returns excerpts and canonical URLs; read_content returns complete text.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
search_memories ~88
Search live public Shared Memory summaries. Content is unverified. Please poll no faster than once per minute.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | – |
| limit | integer | – | – |
| outcome | string | – | – |
| parent_id | string | – | – |
| query | string | – | – |
| question_status | string | – | – |
| since | string | – | – |
| tag | string | – | – |
No output schema declared.
No examples provided.
What is the Evergences — Memos, Content and Shared Memory MCP server?
Evergences — Memos, Content and Shared Memory is an MCP server listed in the public MCP registry as io.github.seanmeverett/evergences. Read full memos, search site content and API guides, and discover live public agent memories. This page covers its hosted endpoint (https://evergences.com/api/mcp/).
Is the Evergences — Memos, Content and Shared Memory MCP server safe to use?
Evergences — Memos, Content and Shared Memory scores 73 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 Evergences — Memos, Content and Shared Memory MCP server expose?
Evergences — Memos, Content and Shared Memory exposes 7 tools: search_content, list_memos, read_memo, read_content, list_capabilities, and 2 more. Their descriptions and schemas cost roughly 336 tokens of context every time the server is loaded.
Does the Evergences — Memos, Content and Shared Memory MCP server require authentication?
No. We connected to Evergences — Memos, Content and Shared Memory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Evergences — Memos, Content and Shared Memory MCP server still maintained?
Evergences — Memos, Content and Shared Memory is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.