# Jan Linketscher (remote · janlinketscher.com)

Profile and essays of Jan Linketscher (i22, Bonn), full-text search, and booking a call.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `janlinketscher.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-janlinketscher-site/api-mcp.md), [page](https://verifymcp.io/servers/com-janlinketscher-site/api-mcp)

## Channel facts

- Endpoint: `https://janlinketscher.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1014 tokens (~92/item across 11 items; 7 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Jan Linketscher MCP server?

Jan Linketscher is a hosted endpoint at https://janlinketscher.com/api/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.

### Claude

```bash
claude mcp add --transport http com-janlinketscher-site 'https://janlinketscher.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-janlinketscher-site": {
      "url": "https://janlinketscher.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-janlinketscher-site": {
      "type": "http",
      "url": "https://janlinketscher.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-janlinketscher-site]
url = "https://janlinketscher.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-janlinketscher-site": {
      "type": "remote",
      "url": "https://janlinketscher.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-janlinketscher-site --url 'https://janlinketscher.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-janlinketscher-site:
    url: "https://janlinketscher.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-janlinketscher-site": {
      "Transport": "http",
      "Url": "https://janlinketscher.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-janlinketscher-site -t streamable-http -u 'https://janlinketscher.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-janlinketscher-site": {
      "type": "http",
      "url": "https://janlinketscher.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-11 (score 68)

First indexed and scored.

## MCP tools (7)

### `get_profile` (~73 tokens)

Profile

Who Jan Linketscher is: managing director and shareholder of the digital agency i22 (Bonn), his background, how his texts are written, and how to contact him. Content is in German.

Input parameters:

- `section` (string): Limit the text answer to one section (default: all). Structured output is always complete.

Output parameters:

- `about` (string)
- `background` (string)
- `contact` (object)
- `employer` (object)
- `image` (string)
- `locations` (array)
- `name` (string)
- `role` (string)
- `summary` (string)
- `writing` (string): How the texts are produced (AI-assisted, human-reviewed).

### `list_essays` (~89 tokens)

List essays

List the essays, newest first: title, date, one-sentence summary, topics, URL and slug. Optionally filter by topic slug. Also returns the available topics.

Input parameters:

- `limit` (integer): Maximum number of essays (default 20).
- `topic` (string): Topic slug, e.g. "transformation" or "agentic-visibility". Omit for all essays.

Output parameters:

- `count` (integer)
- `essays` (array)
- `series` (object)
- `topics` (array)

### `get_essay` (~61 tokens)

Get essay

Full text of one essay as Markdown (with front matter). Use the slug from list_essays or search.

Input parameters:

- `slug` (string, required): Essay slug, e.g. "mein-essay" (the last part of /essays/<slug>).

Output parameters:

- `date` (string)
- `markdown` (string)
- `slug` (string)
- `title` (string)
- `topics` (array)
- `url` (string)

### `search` (~62 tokens)

Search

Full-text search across all essays and pages (about, context). Returns the best matches with title, URL and a short snippet. German queries work best.

Input parameters:

- `limit` (integer): Maximum number of results (default 5).
- `query` (string, required): Search terms.

Output parameters:

- `query` (string)
- `results` (array)

### `list_meeting_types` (~60 tokens)

Meeting types

The kinds of calls that can be booked with Jan Linketscher ("kennenlernen" (Kennenlernen, 30 min), "sparring" (Sparring, 60 min)), with duration, purpose and a booking link for humans.

Output parameters:

- `meetingTypes` (array)
- `timeZone` (string)

### `get_availability` (~144 tokens)

Availability

Free time slots for a call with Jan Linketscher. meeting_type: "kennenlernen" (Kennenlernen, 30 min), "sparring" (Sparring, 60 min). Optional date range (YYYY-MM-DD, default: the next 14 days, at most 90 days ahead). Times are ISO 8601 with offset; the text answer lists them in Europe/Berlin.

Input parameters:

- `from` (string): First day (YYYY-MM-DD). Default: today.
- `meeting_type` (string, required): Kind of call.
- `to` (string): Last day (YYYY-MM-DD), inclusive. Default: from + 13 days.

Output parameters:

- `bookingUrl` (string)
- `from` (string)
- `meetingType` (string)
- `minutes` (integer)
- `slots` (array)
- `timeZone` (string)
- `to` (string)

### `book_meeting` (~284 tokens)

Book a call

Book a call with Jan Linketscher on behalf of your user. The start must be a slot returned by get_availability. If your client supports elicitation (form mode, MCP 2026-07-28), the server itself asks the user to confirm time, name and email – name and email are then prefilled from your arguments and can be corrected by the user. Otherwise: show the user meeting type, date and time (with time zone), name and email, get their explicit approval, then pass name, email and confirmed: true. Use the user's real name and email; never invent them. Cal.com sends the confirmation with a calendar invite and links to reschedule or cancel to that email address.

Input parameters:

- `confirmed` (boolean): Only for clients without elicitation: true = the user has explicitly approved this booking.
- `email` (string): Email of the person attending; the confirmation goes there.
- `meeting_type` (string, required)
- `name` (string): Full name of the person attending.
- `notes` (string): Optional: what the call is about, in one or two sentences.
- `start` (string, required): Slot start from get_availability (ISO 8601).
- `time_zone` (string): IANA time zone of the attendee, e.g. "Europe/Berlin" (default Europe/Berlin).

Output parameters:

- `attendee` (object)
- `end` (string)
- `meetingType` (string)
- `message` (string)
- `start` (string)
- `status` (string): pending: Jan confirms the request by email. not_booked: the user declined.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-janlinketscher-site/api-mcp#diagnostics

## Score history

- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72
- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 69
- 2026-10-13: 69
- 2026-10-12: 68
- 2026-10-11: 68

## Common questions

### What is the Jan Linketscher MCP server?

Jan Linketscher is an MCP server listed in the public MCP registry as com.janlinketscher/site. Profile and essays of Jan Linketscher (i22, Bonn), full-text search, and booking a call. This page covers its hosted endpoint (https://janlinketscher.com/api/mcp).

### Is the Jan Linketscher MCP server safe to use?

Jan Linketscher scores 74 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 Jan Linketscher MCP server expose?

Jan Linketscher exposes 7 tools: get_profile, list_essays, get_essay, search, list_meeting_types, and 2 more. Their descriptions and schemas cost roughly 773 tokens of context every time the server is loaded.

### Does the Jan Linketscher MCP server require authentication?

No. We connected to Jan Linketscher without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Jan Linketscher MCP server still maintained?

Jan Linketscher is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://janlinketscher.com/api/mcp
- Website: https://janlinketscher.com/agent
- Changelog RSS feed: https://verifymcp.io/servers/com-janlinketscher-site/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-janlinketscher-site/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-janlinketscher-site/api-mcp