# io.github.mjaskolski/developer-toolkit-mcp (remote · developertoolkit.ai)

The documentation, as a tool your agent can call: 950+ AI-dev guides. Search + fetch tools.

- Trust score: 74/100 (medium)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `developertoolkit.ai`: 74/100 (this document), [markdown](https://verifymcp.io/servers/mjaskolski-developer-toolkit-mcp/developertoolkit.md), [page](https://verifymcp.io/servers/mjaskolski-developer-toolkit-mcp/developertoolkit)

## Channel facts

- Endpoint: `https://developertoolkit.ai/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-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 354 tokens (~177/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 44/100
  - Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions.
- **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.
  - 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 io.github.mjaskolski/developer-toolkit-mcp server?

io.github.mjaskolski/developer-toolkit-mcp is a hosted endpoint at https://developertoolkit.ai/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 mjaskolski-developer-toolkit-mcp 'https://developertoolkit.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mjaskolski-developer-toolkit-mcp": {
      "url": "https://developertoolkit.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mjaskolski-developer-toolkit-mcp": {
      "type": "http",
      "url": "https://developertoolkit.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mjaskolski-developer-toolkit-mcp]
url = "https://developertoolkit.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mjaskolski-developer-toolkit-mcp": {
      "type": "remote",
      "url": "https://developertoolkit.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mjaskolski-developer-toolkit-mcp --url 'https://developertoolkit.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mjaskolski-developer-toolkit-mcp:
    url: "https://developertoolkit.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mjaskolski-developer-toolkit-mcp": {
      "Transport": "http",
      "Url": "https://developertoolkit.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mjaskolski-developer-toolkit-mcp -t streamable-http -u 'https://developertoolkit.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mjaskolski-developer-toolkit-mcp": {
      "type": "http",
      "url": "https://developertoolkit.ai/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-09-19 (score 74, −7)

- [security regression] Stability: 0.97 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [functional regression] Schema quality: pass → fail
- [functional regression] “fetch” added a required parameter “llm_model”, so existing callers break
- [functional regression] “search” added a required parameter “llm_model”, so existing callers break

### 2026-09-17 (score 81, +1)

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

### 2026-09-15 (score 80, +1)

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

### 2026-09-13 (score 79, +1)

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

### 2026-09-11 (score 78, +1)

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

### 2026-09-09 (score 77, +1)

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

### 2026-09-07 (score 76, 0)

- [security] Tool “fetch” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 70 → 103

### 2026-09-06 (score 76, +1)

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

## MCP tools (2)

### `search` (~186 tokens)

Search the documentation

Search the AI Developer Toolkit documentation: 950+ guides on Cursor, Claude Code and OpenAI Codex, covering setup, agent workflows, hooks, MCP, testing, CI and deployment, in English and Polish. Returns at most 10 ranked results, each with a short snippet rather than the article text; an empty list means the corpus has nothing on the topic. Pass a result id to `fetch` for the full text.

Input parameters:

- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `query` (string, required): Natural-language query or keywords. Polish queries return Polish articles.

Output parameters:

- `results` (array)

### `fetch` (~168 tokens)

Fetch a documentation article

Retrieve the complete markdown of one documentation article by the id returned from `search` (for example `en/claude-code/advanced-techniques/hooks-automation`). The text is returned in full; `metadata.gated` only reports whether the article sits behind the paywall on the web. An unknown id is an error — call `search` first.

Input parameters:

- `id` (string, required): Article id from a `search` result.
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mjaskolski-developer-toolkit-mcp/developertoolkit#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 76
- 2026-09-05: 75
- 2026-09-04: 75
- 2026-09-03: 74
- 2026-09-02: 74
- 2026-09-01: 73
- 2026-08-31: 73
- 2026-08-30: 72
- 2026-08-29: 72
- 2026-08-28: 71
- 2026-08-27: 71
- 2026-08-26: 70
- 2026-08-25: 69
- 2026-08-24: 68
- 2026-08-23: 68
- 2026-08-22: 67

## Common questions

### What is the io.github.mjaskolski/developer-toolkit-mcp server?

io.github.mjaskolski/developer-toolkit-mcp is listed in the public MCP registry as io.github.mjaskolski/developer-toolkit-mcp. The documentation, as a tool your agent can call: 950+ AI-dev guides. Search + fetch tools. This page covers its hosted endpoint (https://developertoolkit.ai/mcp).

### Is the io.github.mjaskolski/developer-toolkit-mcp server safe to use?

io.github.mjaskolski/developer-toolkit-mcp 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 io.github.mjaskolski/developer-toolkit-mcp server expose?

io.github.mjaskolski/developer-toolkit-mcp exposes 2 tools: search, fetch. Their descriptions and schemas cost roughly 354 tokens of context every time the server is loaded.

### Does the io.github.mjaskolski/developer-toolkit-mcp server require authentication?

No. We connected to io.github.mjaskolski/developer-toolkit-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.mjaskolski/developer-toolkit-mcp server still maintained?

io.github.mjaskolski/developer-toolkit-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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://developertoolkit.ai/mcp
- Repository: https://github.com/mjaskolski/developer-toolkit-mcp
- Website: https://developertoolkit.ai/en/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/mjaskolski-developer-toolkit-mcp/developertoolkit.xml
- Changelog JSON feed: https://verifymcp.io/servers/mjaskolski-developer-toolkit-mcp/developertoolkit.json
- HTML version of this page: https://verifymcp.io/servers/mjaskolski-developer-toolkit-mcp/developertoolkit