Context — ctxt.io
REMOTE · CTXT.IO · SCANNED AUG 20
Share text, markdown, code, or HTML as auto-expiring links
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_context). See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 686 tokens (~228/item across 3 items; 3 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · ctxt.io
claude mcp add --transport http io-ctxt-mcp https://ctxt.io/mcp
[mcp_servers.io-ctxt-mcp] url = "https://ctxt.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-ctxt-mcp": {
"type": "remote",
"url": "https://ctxt.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-ctxt-mcp --url https://ctxt.io/mcp --transport streamable-http
mcp_servers:
io-ctxt-mcp:
url: "https://ctxt.io/mcp" {
"mcpServers": {
"io-ctxt-mcp": {
"type": "http",
"url": "https://ctxt.io/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.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 61
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 20 Aug 2026 · Probed https://ctxt.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ctxt.io | CN=WR3,O=Google Trust Services,C=US | 22 Jul 2026 | 20 Oct 2026 | RSA 2048 | SHA256-RSA | c4704b4991bda8ad0970a0d0a72192e8 |
| SANs: ctxt.io | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of ctxt.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| ctxt.io. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ctxt.io/mcp | Verified | 200 | |
| http (plaintext) | http://ctxt.io/mcp | HTTPS enforced | 302 | https://ctxt.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.
create_context Create a ctxt.io share link ~392
Share text, markdown, code, or HTML as an auto-expiring ctxt.io link. For visual output (styled reports, tables, charts, diagrams) prefer format=html with self-contained HTML: inline CSS and inline SVG render fully; <script> is stripped server-side and JavaScript never runs, so keep it static. Free expiries: 5m, 30m, 1h (default), 8h, 1d — these return the share URL immediately. ttl=30d and the Pro options (name, password) cost $1 one-time: the link is created in a pending state and the result includes a payment_url a human can open in a browser to complete checkout (platforms enrolled for agentic payments receive an acp block instead and can pay programmatically); until payment the link lives 1 day without Pro features. Anyone with the link can read it. The returned delete_token authorizes deletion via delete_context — keep it private.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content to share (max 4MB). |
| format | string | – | How to render the content: text (verbatim), markdown (rendered rich), code (syntax highlighted), or html (sanitized and rendered — best for visual output; inline CSS/SVG work, scripts are stripped). |
| lang | string | – | With format=code: the language to highlight (e.g. python, javascript, diff). Omit to auto-detect. |
| name | string | – | Pro, ttl=30d only: human-readable name appended to the URL as a slug. |
| password | string | – | Pro, ttl=30d only: password required to read the link. Access control, not encryption — content is plaintext at rest. |
| ttl | string | – | How long the link stays readable. 5m–1d are free; 30d costs $1. |
| Name | Type | Req | Description |
|---|---|---|---|
| acp | object | – | Present when this deployment accepts Agentic Commerce Protocol payments: checkout_endpoint + item_id let an enrolled agent platform complete the $1 purchase without a browser. |
| current_ttl_seconds | integer | yes | – |
| delete_token | string | yes | – |
| expires_at | string | yes | – |
| json_url | string | yes | – |
| manage_url | string | yes | Browser page where a human holding this link's delete_token can delete or upgrade it later — share it only with the link's owner. |
| markdown_url | string | yes | – |
| paid_ttl_seconds | integer | – | – |
| payment_url | string | – | – |
| pending_payment | boolean | yes | – |
| text_url | string | yes | – |
| url | string | yes | – |
| x402 | object | – | Present when this deployment accepts x402 payments: any agent with an x402 wallet can pay the $1 via the upgrade_context tool — no enrollment. |
No examples provided.
delete_context Delete a ctxt.io link ~87
Delete a ctxt.io link you created. Requires the delete_token returned by create_context. Immediately removes public access and requests backing-storage deletion. Destructive and not undoable — confirm with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| delete_token | string | yes | The delete_token from create_context. |
| url_or_key | string | yes | Full ctxt.io URL, /3/<code> path, or bare code. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
No examples provided.
read_context Read a ctxt.io link ~93
Fetch the content of an existing ctxt.io link. Accepts a full ctxt.io URL, a /3/<code> path, or a bare code. Password-protected links need the password argument.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Representation to return. |
| password | string | – | Password for protected links. |
| url_or_key | string | yes | Full ctxt.io URL, /3/<code> path, or bare code. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| created | string | yes | – |
| expires_at | string | yes | – |
| ttl_seconds | integer | yes | – |
No examples provided.