Context — ctxt.io MCP server
online · 100% uptimeio.ctxt/mcp·v1.0.0·3 starsShare text, markdown, code, or HTML as auto-expiring links
3 stars
Reviews
Write oneNobody has reviewed Context — ctxt.io yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Context — ctxt.io tools (3, 2 write)
write = sends, deletes, buys or postscreate_contextwrite actionFreeShare 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.
delete_contextwrite actionFreeDelete 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.
read_contextFreeFetch 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.
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 476ms20/20
- Tool poisoning3 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
- Maintenancelast push 32 days ago12/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How Context — ctxt.io compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 67%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 355 ms
- faster than 41% of 30,031 servers
- GitHub stars
- 3
- more than 80% of 28,688 servers
What its tools let an agent do: 1 read · 1 create · 1 delete
Install Context — ctxt.io in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp https://ctxt.io/mcp
What the publisher says
From the Context — ctxt.io repository's README, as published. We do not edit it. Read it on GitHub
ctxt.io for agents
Share whatever your agent produces as auto-expiring links. This repo packages the ctxt.io MCP server for agent runtimes: a Claude Code plugin (MCP + share skill), a Codex plugin, a Cursor plugin, and install recipes for VS Code and claude.ai.
- MCP endpoint: https://ctxt.io/mcp (streamable HTTP, no auth, no account)
- Tools: createcontext, readcontext, delete_context
- Free expiries: 5m – 1d. ttl=30d and Pro options (name, password) cost $1 one-time; the tool result says how payment completes — a payment_url a human opens, plus any agent-payment capability the server currently advertises.
Claude Code (plugin — recommended)
/plugin marketplace add ctxt-io/ctxt-agents
/plugin install ctxt@ctxtYou get the MCP server and a share skill that teaches Claude when to share and how to produce good-looking HTML output (self-contained HTML + inline SVG — scripts are stripped server-side, so static only). The skill also registers the /ctxt:share slash command.
MCP server only, no plugin:
claude mcp add --transport http ctxt https://ctxt.io/mcpCodex
Codex plugin (bundles the MCP server + the share skill; lives in codex/ctxt/ with a .codex-plugin/plugin.json manifest):
codex plugin marketplace add ctxt-io/ctxt-agents
codex plugin add ctxt@ctxtMCP server only — add to ~/.codex/config.toml:
[mcp_servers.ctxt]
url = "https://ctxt.io/mcp"Skill only — Codex loads skills from ~/.agents/skills (open Agent Skills format):
mkdir -p ~/.agents/skills
cp -r codex/ctxt/skills/share ~/.agents/skills/ctxt-shareCursor
One-click install (opens Cursor with the server pre-filled):
Add to Cursor
Cursor plugin (bundles the MCP server + the share skill, which Cursor registers as /share; lives in cursor/ctxt/ with a .cursor-plugin/plugin.json manifest, and the repo root carries a .cursor-plugin/marketplace.json so the whole repo can be added as a marketplace):
Cursor → Settings → Tools & MCP → add marketplace → ctxt-io/ctxt-agentsMCP server only, by hand — add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"ctxt": { "url": "https://ctxt.io/mcp" }
}
}VS Code
Add to .vscode/mcp.json — note VS Code uses a top-level servers map, not mcpServers:
{
"servers": {
"ctxt": { "type": "http", "url": "https://ctxt.io/mcp" }
}
}claude.ai / Claude Desktop
Customize → Connectors → Add custom connector → https://ctxt.io/mcp (no auth).
Any other MCP client
Point it at https://ctxt.io/mcp: stateless streamable HTTP, plain JSON responses, no authentication.
Notes
- Links are bearer-accessible by default — anyone holding the URL can read them; password-protected (Pro) links additionally require the password. Don't share secrets.
- The delete_token returned at creation is a deletion capability. Treat it as a secret and keep it out of shared content.
- Releasing: bump version in all three plugin manifests together (Claude only updates installed plugins when the version changes) and tag the release; CI checks the manifests stay in sync.
- Docs: https://ctxt.io/mcp/docs · Terms: https://ctxt.io/tos · Privacy: https://ctxt.io/privacy
- Security reports: see SECURITY.md.
License
MIT
Nothing above is checked by us. What we check is on the safety report.
Context — ctxt.io: common questions
- Is Context — ctxt.io MCP server safe?
- Mostly: it is graded B (77/100). Read the Context — ctxt.io safety report
- How do I install Context — ctxt.io?
- It runs remotely at ctxt.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Context — ctxt.io need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Context — ctxt.io maintained?
- The last commit was 32 days ago (2026-10-03). The latest release is v1.0.0.
- Is Context — ctxt.io up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Context — ctxt.io?
- Servers from other publishers that do the same job: Compiler Explorer MCP server.
- How does Context — ctxt.io compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 67% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Context — ctxt.io
Same job from other publishers: the closest match first, then the best rated.
- Compiler ExplorerCompile code with thousands of compilers, inspect the assembly, and share godbolt.org linksnot reviewedEstablishedB