Jan Linketscher
REMOTE · JANLINKETSCHER.COM
Profile and essays of Jan Linketscher (i22, Bonn), full-text search, and booking a call.
Available components
Last scanned (15 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Education and Research
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1014 tokens (~92/item across 11 items; 7 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 19 Oct 26 +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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 13 Oct 26 +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.
- 12 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Oct 26 68
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 23 Oct 2026 · Probed https://janlinketscher.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=janlinketscher.com | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 314f903a698f005113dd445b00d7a420 |
| SANs: janlinketscher.com, *.janlinketscher.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of janlinketscher.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| janlinketscher.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://janlinketscher.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://janlinketscher.com/api/mcp | Inconclusive | 405 |
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 →
book_meeting Book a call ~284
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | Only for clients without elicitation: true = the user has explicitly approved this booking. |
| string | – | Email of the person attending; the confirmation goes there. | |
| meeting_type | string | yes | – |
| name | string | – | Full name of the person attending. |
| notes | string | – | Optional: what the call is about, in one or two sentences. |
| start | string | yes | Slot start from get_availability (ISO 8601). |
| time_zone | string | – | IANA time zone of the attendee, e.g. "Europe/Berlin" (default Europe/Berlin). |
| Name | Type | Req | Description |
|---|---|---|---|
| attendee | object | yes | – |
| end | string | yes | – |
| meetingType | string | yes | – |
| message | string | yes | – |
| start | string | yes | – |
| status | string | yes | pending: Jan confirms the request by email. not_booked: the user declined. |
No examples provided.
get_availability Availability ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day (YYYY-MM-DD). Default: today. |
| meeting_type | string | yes | Kind of call. |
| to | string | – | Last day (YYYY-MM-DD), inclusive. Default: from + 13 days. |
| Name | Type | Req | Description |
|---|---|---|---|
| bookingUrl | string | yes | – |
| from | string | yes | – |
| meetingType | string | yes | – |
| minutes | integer | yes | – |
| slots | array | yes | – |
| timeZone | string | yes | – |
| to | string | yes | – |
No examples provided.
get_essay Get essay ~61
Full text of one essay as Markdown (with front matter). Use the slug from list_essays or search.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Essay slug, e.g. "mein-essay" (the last part of /essays/<slug>). |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| markdown | string | yes | – |
| slug | string | yes | – |
| title | string | yes | – |
| topics | array | – | – |
| url | string | yes | – |
No examples provided.
get_profile Profile ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Limit the text answer to one section (default: all). Structured output is always complete. |
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | – |
| background | string | – | – |
| contact | object | yes | – |
| employer | object | yes | – |
| image | string | – | – |
| locations | array | – | – |
| name | string | yes | – |
| role | string | yes | – |
| summary | string | yes | – |
| writing | string | – | How the texts are produced (AI-assisted, human-reviewed). |
No examples provided.
list_essays List essays ~89
List the essays, newest first: title, date, one-sentence summary, topics, URL and slug. Optionally filter by topic slug. Also returns the available topics.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of essays (default 20). |
| topic | string | – | Topic slug, e.g. "transformation" or "agentic-visibility". Omit for all essays. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| essays | array | yes | – |
| series | object | yes | – |
| topics | array | yes | – |
No examples provided.
list_meeting_types Meeting types ~60
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meetingTypes | array | yes | – |
| timeZone | string | yes | – |
No examples provided.
search Search ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (default 5). |
| query | string | yes | Search terms. |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
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.
remote · janlinketscher.com
claude mcp add --transport http com-janlinketscher-site 'https://janlinketscher.com/api/mcp'
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.