ContexteTech
REMOTE · CONTEXTETECH.COM · 2 COMPONENTS
Search and load AI datasets, prompts and few-shot contexts from the ContexteTech catalogue.
Available components
Last scanned (10 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 22 Oct 2026.
Category AI and Machine Learning
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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 986 tokens (~164/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability check failed: schema churn in the 7 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 1 to 4.
- 19 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- 18 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “load_resource” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 17 Oct 26 +1
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still online ▼ security
- Tool “get_download_link” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_resources” rewrote its description, which is the text the model reads security
- Tool “load_resource” rewrote its description, which is the text the model reads security
- Tool “fill_prompt” rewrote its description, which is the text the model reads security
- Tool “estimate_cost” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- MCP protocol: fail → pass ▲ functional
- Schema quality: good → excellent functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- 16 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 71
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 22 Oct 2026 · Probed https://contextetech.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=contextetech.com | CN=YE2,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 575225b80064ddfc620375297a1cd0bb864 |
| SANs: contextetech.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
| CN=ISRG Root X1,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 4 Jun 2015 | 4 Jun 2035 | RSA 4096 | SHA256-RSA | 8210cfb0d240e3594463e0bb63828b00 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of contextetech.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| contextetech.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=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://contextetech.com/mcp | Verified | 200 | |
| http (plaintext) | http://contextetech.com/mcp | HTTPS enforced | 301 | https://contextetech.com/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 →
estimate_cost Estimate the cost ~132
Estimate in euros what a ContexteTech resource costs to run with common AI models, from the week's list prices. Use it when the user asks about cost, budget or the cheapest model. For a prompt or context: input and output tokens, cost per call for each model and batch discount; for a dataset: cost of one pass over all rows and a fine-tuning estimate on rented GPUs (hours and offers); for a model: memory (VRAM) needed and GPU offers that fit. Returns available: false with a note when no estimate exists for that type.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Short code |
No output schema declared.
No examples provided.
fetch Fetch (connector format) ~36
Fetch the full content of a ContexteTech resource by the id returned by search.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Resource id or short code |
No output schema declared.
No examples provided.
fill_prompt Fill a prompt ~134
Fill a ContexteTech prompt template and return the ready-to-send text, nothing else. Use it when the user wants a prompt applied to their own case; call load_resource first if you need the template or the exact variable names. 'variables' maps each {{name}} of the template to its text value; extra keys are ignored. Fails with an error if the code is unknown, if the resource is not a prompt, or if a template variable is missing (the error lists the missing names).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Short code of the prompt |
| variables | object | yes | Values for each {{variable}} |
No output schema declared.
No examples provided.
load_resource Load a resource ~218
Read one ContexteTech resource, usually right after search_resources or when the user gives a code or page URL. Accepts the short code (end of the page URL, e.g. 'jr6t0n'), 'author/name', or 'code#v2' for a fixed version. Always returns title, type, licence, language, source, version and page URL; plus, for a dataset, the total number of rows, the first rows (default 10, max 50); for a prompt, the template and its {{variables}} (then call fill_prompt); for a context, the system prompt, knowledge and examples. The result ends with a Source line (resource, author, original data source, publisher, licence): citing it with its links is required. Fails with an error if the code does not exist or the resource is private.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Short code (end of the resource URL) |
| rows | integer | – | Dataset rows to return (default 10, max 50) |
No output schema declared.
No examples provided.
search Search (connector format) ~39
Search the ContexteTech catalogue of AI datasets, prompts and contexts. Returns results with id, title and url.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search words |
No output schema declared.
No examples provided.
search_resources Search the ContexteTech catalogue ~285
Search the ContexteTech catalogue of AI building blocks: fine-tuning and evaluation datasets (chat, DPO, agent traces), prompts, few-shot contexts, MCP servers, models and more, many grounded in official European sources, in 9 languages. Use it first when the user needs AI training or evaluation data, a prompt, a context or an AI component, then call load_resource with a returned code. Write the topic in a few words, in English or the content language; common topics are matched across French, English, German and Spanish (e.g. 'marine weather' finds 'météo marine'), and a type word such as 'dataset' or 'prompt' puts that type first. Resources matching every topic come first; weaker matches carry match: partial. Returns up to 15 matches, each with short code, title, type, language, licence, author, rows (datasets), description and page URL; when nothing matches, returns a short message suggesting how to rephrase.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional content language: fr, en, es, de, it, nl, pt, sv, pl |
| query | string | yes | Search words, e.g. 'customs code' or 'GDPR' |
| type | string | – | Optional type: dataset, prompt, context, tool, model, agent, eval, rag… |
No output schema declared.
No examples provided.
How do I install the ContexteTech MCP server?
ContexteTech is a hosted endpoint at https://contextetech.com/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 · contextetech.com
claude mcp add --transport http contexte-tech-contexte 'https://contextetech.com/mcp'
What is the ContexteTech MCP server?
ContexteTech is an MCP server listed in the public MCP registry as io.github.contexte-tech/contexte. Search and load AI datasets, prompts and few-shot contexts from the ContexteTech catalogue. This page covers its hosted endpoint (https://contextetech.com/mcp).
Is the ContexteTech MCP server safe to use?
ContexteTech 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 ContexteTech MCP server expose?
ContexteTech exposes 6 tools: search_resources, load_resource, fill_prompt, estimate_cost, search, fetch. Their descriptions and schemas cost roughly 844 tokens of context every time the server is loaded.
Does the ContexteTech MCP server require authentication?
No. We connected to ContexteTech without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ContexteTech MCP server still maintained?
ContexteTech is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.