# Niels Langereis (remote · nielslangereis.com)

Essays, an enterprise AI map and a skill-matrix gap analysis on AI adoption and junior formation.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `nielslangereis.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-nielslangereis-thinking/nielslangereis.md), [page](https://verifymcp.io/servers/com-nielslangereis-thinking/nielslangereis)

## Channel facts

- Endpoint: `https://nielslangereis.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 45/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1027 tokens (~128/item across 8 items; 6 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Niels Langereis MCP server?

Niels Langereis is a hosted endpoint at https://nielslangereis.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.

### Claude

```bash
claude mcp add --transport http com-nielslangereis-thinking 'https://nielslangereis.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-nielslangereis-thinking": {
      "url": "https://nielslangereis.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-nielslangereis-thinking": {
      "type": "http",
      "url": "https://nielslangereis.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-nielslangereis-thinking]
url = "https://nielslangereis.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-nielslangereis-thinking --url 'https://nielslangereis.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-nielslangereis-thinking:
    url: "https://nielslangereis.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-nielslangereis-thinking": {
      "Transport": "http",
      "Url": "https://nielslangereis.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-nielslangereis-thinking -t streamable-http -u 'https://nielslangereis.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-nielslangereis-thinking": {
      "type": "http",
      "url": "https://nielslangereis.com/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-11-03 (score 77, +1)

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

### 2026-11-01 (score 76, +1)

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

### 2026-10-30 (score 75, +1)

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

### 2026-10-28 (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-26 (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-24 (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-22 (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-19 (score 70, +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.

## MCP tools (6)

### `search_essays` (~114 tokens)

Search Niels Langereis's essays

Search the essays of Niels Langereis on AI adoption, organisational change, the politics of AI, junior formation and judgement, brand and AI agents, boards and governance. Returns titles, dates, summaries, a matching snippet and links. Leave query empty to list all essays, newest first. Follow up with get_essay for the full text before quoting him.

Input parameters:

- `query` (string): Topic or question, e.g. 'who owns AI decisions', 'brand lock-in by AI agents'. Empty lists everything.

### `get_essay` (~71 tokens)

Read one essay in full

Get the full text of one essay by Niels Langereis, as Markdown, with its date, site link and the original LinkedIn link. Use the id from search_essays, or a title.

Input parameters:

- `id` (string, required): Essay id (from search_essays) or its title

### `get_enterprise_ai_map` (~259 tokens)

Enterprise AI map

Niels Langereis's enterprise AI map: 24 illustrative AI agents across ten business functions (strategy, product, design, marketing, sales, customer success, operations, people, finance, data and IT), each with its rollout phase, what it optimises for and the trade-off it creates for other functions; plus the coordination layer, the bench and the external renderers that decide whether faster work becomes a better organisation. Use it to reason about someone's own AI rollout. detail='summary' returns only the skeleton (functions, agents, phases and trade-offs, plus one line per remaining part), which is enough for most reasoning; detail='full' (default) adds the complete prose on coordination, the bench and the renderers. Optionally filter by function or phase. Shows an interactive map where the client supports it.

Input parameters:

- `detail` (string): summary: functions, agents and trade-offs only. full (default): also the prose on coordination, the bench and the renderers.
- `function` (string): Optional: focus on one function, e.g. 'Marketing and growth', 'Finance'.
- `phase` (string): Optional: p1 co-pilots, p2 brains, p3 autonomous agents.

### `get_skill_matrix_method` (~81 tokens)

Skill-matrix gap analysis: the method

Explains Niels Langereis's skill-matrix gap analysis: a competency matrix run for formation rather than efficiency, to find where AI has removed the work that used to turn juniors into seniors. Includes the status rule, how to read it, a worked example and credits. Use before run_skill_matrix if the user wants to understand the method first.

### `run_skill_matrix` (~249 tokens)

Run the skill-matrix gap analysis

Runs Niels Langereis's skill-matrix gap analysis for one role and shows it as an interactive matrix the user can edit (who does the work now, bench depth, formation actions). Draft 6 to 10 competencies for the user's role yourself from what you know about it, spanning routine work AI can now do with senior oversight, work AI already runs autonomously, and judgement work that needs a human. Set bench (how many people can do it at the strategic level) from what the user told you; if unknown, use 1 and say it is an estimate they should correct. Omit competencies to show the generic analyst example. The result flags 'At risk' (human work, one person deep), 'Thin' (two deep) and 'Reps gone' (AI runs it autonomously, so the formation that used to happen in reviewing it has gone too: ask where juniors get those reps now). After the user edits, their current matrix arrives in your context.

Input parameters:

- `competencies` (array): The competencies for this role.
- `role` (string): The role being analysed, e.g. 'Marketing manager at a 200-person B2B firm'.

### `about_niels` (~101 tokens)

About Niels Langereis

Who Niels Langereis is and how to work with him: what he does and for whom, how he works, his background, his talks and speaking, and how to get in touch. Use when someone asks whether he could help them, wants to hire or book him, or wants his background. Contact is by email or the site's contact form; this server does not send messages.

Input parameters:

- `topic` (string): What to return. Default overview.

## Diagnostics

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

## Score history

- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 73
- 2026-10-26: 73
- 2026-10-25: 72
- 2026-10-24: 72
- 2026-10-23: 71
- 2026-10-22: 71
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 68

## Common questions

### What is the Niels Langereis MCP server?

Niels Langereis is an MCP server listed in the public MCP registry as com.nielslangereis/thinking. Essays, an enterprise AI map and a skill-matrix gap analysis on AI adoption and junior formation. This page covers its hosted endpoint (https://nielslangereis.com/mcp).

### Is the Niels Langereis MCP server safe to use?

Niels Langereis scores 77 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 Niels Langereis MCP server expose?

Niels Langereis exposes 6 tools: search_essays, get_essay, get_enterprise_ai_map, get_skill_matrix_method, run_skill_matrix, about_niels. Their descriptions and schemas cost roughly 875 tokens of context every time the server is loaded.

### Does the Niels Langereis MCP server require authentication?

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

### Is the Niels Langereis MCP server still maintained?

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

### What did VerifyMCP test on the Niels Langereis MCP server?

VerifyMCP ran 14 checks on Niels Langereis, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://nielslangereis.com/mcp
- Website: https://nielslangereis.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-nielslangereis-thinking/nielslangereis.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-nielslangereis-thinking/nielslangereis/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-nielslangereis-thinking/nielslangereis.json
- HTML version of this page: https://verifymcp.io/servers/com-nielslangereis-thinking/nielslangereis