Context Link
REMOTE · WWW.CONTEXT-LINK.AI
One semantic search across your sites, Drive, Notion, email, files and Basecamp.
Available components
Last scanned (20 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 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 560 tokens (~112/item across 5 items; 4 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 12 Oct 26 +1
- Stability: 0.93 → pass security
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 83 to 93. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 83. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 13 Sept 26 0
- Schema quality: 86 → 112 ▼ functional
- Tool coverage: 71% → 78% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- “ask_question” added an optional parameter “connection_type” cosmetic
- “get_context” added an optional parameter “connection_type” cosmetic
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 4 Nov 2026 · Probed https://www.context-link.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=context-link.ai | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2b57e5da6a1582aa13115079702793a9 |
| SANs: context-link.ai, *.context-link.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.context-link.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| context-link.ai. | 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 tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://www.context-link.ai/.well-known/oauth-protected-resource/mcp", scope="context:read context:write", error="insufficient_scope", error_description="Authentication required"
Bearer resource_metadata="https://www.context-link.ai/.well-known/oauth-protected-resource/mcp", scope="context:read context:write", error="insufficient_scope", error_description="Authentication required"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://www.context-link.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://www.context-link.ai/mcp |
| Authorisation server | https://www.context-link.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.context-link.ai/mcp | Verified | 200 | |
| http (plaintext) | http://www.context-link.ai/mcp | HTTPS enforced | 301 | https://www.context-link.ai/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 →
ask_question Ask Question ~146
Ask a question about the user's connected workspaces and websites and receive a concise answer with citations. The attached widget displays only the list of sources consulted — it does not show the answer, so always relay the answer text in your reply.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_type | string | – | Optional comma-separated list of connection types to restrict retrieval to (e.g. "site,email"). Only content from those sources is considered. Valid types: basecamp, custom, email, files, google_doc,… |
| mode | string | – | Optional mode to weight results (e.g. 'customer-support') |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | Concise paragraph answer; empty string when success is false |
| citations | array | yes | – |
| reason | string | yes | – |
| sources | array | yes | – |
| success | boolean | yes | – |
No examples provided.
get_context Get Context ~140
Get context from the user's connected workspaces and websites. The attached widget displays only the list of sources consulted — it does not show the retrieved content, so use the returned context to answer the user directly.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_type | string | – | Optional comma-separated list of connection types to restrict retrieval to (e.g. "site,email"). Only content from those sources is considered. Valid types: basecamp, custom, email, files, google_doc,… |
| mode | string | – | Optional mode to weight results (e.g. 'customer-support') |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | string|null | yes | – |
| sources | array | yes | – |
No examples provided.
get_memory Get Memory ~44
Retrieve previously saved memory content by its namespace. Use this when the user wants to recall saved content.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | The namespace/name of the saved memory to retrieve |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| found | boolean | yes | – |
| namespace | string | yes | – |
No examples provided.
save_memory Save Memory ~87
Save content to the user's memory for later retrieval. Use this when the user wants to save information, notes, or conversation content.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content to save. Can be plain text, markdown, or structured content. |
| namespace | string | – | A name/label for this memory (use-dashes-for-spaces). If omitted, a timestamped name is generated. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| namespace | string | yes | – |
No examples provided.
How do I install the Context Link MCP server?
Context Link is a hosted endpoint at https://www.context-link.ai/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 · www.context-link.ai
claude mcp add --transport http ai-context-link-context-link 'https://www.context-link.ai/mcp'
What is the Context Link MCP server?
Context Link is an MCP server listed in the public MCP registry as ai.context-link/context-link. One semantic search across your sites, Drive, Notion, email, files and Basecamp. This page covers its hosted endpoint (https://www.context-link.ai/mcp).
Is the Context Link MCP server safe to use?
Context Link scores 94 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 Context Link MCP server expose?
Context Link exposes 4 tools: get_context, ask_question, save_memory, get_memory. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.
Does the Context Link MCP server require authentication?
Yes. Context Link 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 Context Link MCP server still maintained?
Context Link is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.