https://www.context-link.ai/mcp ↗
One semantic search across your sites, Drive, Notion, email, files and Basecamp.
Context Link is a remote MCP server published at www.context-link.ai. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 566 ms, a delay an agent will notice. It offers a narrow, focused set of 4 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
get_context — Parameter 'mode' and 'connection_type' lack defined enums or constraints.ask_question — Shares identical parameter names with get_context, risking overlap.Risk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
get_contextGet 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.
querystringrequiredmodestringconnection_typestringask_questionAsk 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.
querystringrequiredmodestringconnection_typestringsave_memorySave content to the user's memory for later retrieval. Use this when the user wants to save information, notes, or conversation content.
contentstringrequirednamespacestringget_memoryRetrieve previously saved memory content by its namespace. Use this when the user wants to recall saved content.
namespacestringrequiredDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/ai-context-link-context-link)<a href="https://mcpmetrics.io/servers/ai-context-link-context-link"><img src="https://mcpmetrics.io/badge/ai.context-link/context-link/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Medical RAG: semantic search for clinical guidelines, drug interactions, diagnoses & EHR data.
Live web search, image search, topic filters and full-text fetch over our own crawled index.
*One workspace for your prompts, documents, and collections — accessible from every AI client you use.* Context Repo is an AI context management platform for capturing, organizing, versioning, and searching the knowledge artifacts you use with AI tools. This MCP server exposes **28 tools** that give Claude, Cursor, ChatGPT, Factory, Windsurf, Codex, Claude Code, and any other MCP-compatible client direct read-and-write access to your personal workspace — no copy-paste, no context loss between conversations. ## Features - **Prompts** — Full CRUD with version history, rollback, and semantic search across your prompt library - **Documents** — Markdown and plain-text storage with automatic chunking and 1536-dim vector embeddings - **Collections** — Named folders that group prompts and documents into project-scoped contexts - **Catalog Search** — `find_items` returns ranked results across prompts, documents, and collections in a single call (semantic by default, literal fallback) - **Dee
Semantic search for Historical Soundscapes. Search eventos, entities, filters. Cross-lingual ES/EN.
Find availability and book across a network of independent venues via your AI assistant.
OSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Dual-era | 200 | 489 | 200 | 414 | 2026-07-28 |
| 2026-09-12 23:31:36 | Dual-era | 200 | 790 | 200 | 864 | 2026-07-28 |
| 2026-09-12 21:29:15 | Dual-era | 200 | 309 | 200 | 297 | 2026-07-28 |
| 2026-09-12 19:27:29 | Dual-era | 200 | 521 | 200 | 513 | 2026-07-28 |
| 2026-09-12 17:24:09 | Dual-era | 200 | 1157 | 200 | 1202 | 2026-07-28 |
| 2026-09-12 15:21:42 | Dual-era | 200 | 650 | 200 | 566 | 2026-07-28 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.