# PersonalKnowHow (remote · personalknowhow-demo.kxtwrdzt6g.workers.dev)

Live public demo: query one person's learning and work history as a knowledge graph via MCP.

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

## Components

- remote · `personalknowhow-demo.kxtwrdzt6g.workers.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/georgi-petkov-personalknowhow/personalknowhow-demo.md), [page](https://verifymcp.io/servers/georgi-petkov-personalknowhow/personalknowhow-demo)

## Channel facts

- Endpoint: `https://personalknowhow-demo.kxtwrdzt6g.workers.dev/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**: 46/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 4 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 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 953 tokens (~238/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 PersonalKnowHow MCP server?

PersonalKnowHow is a hosted endpoint at https://personalknowhow-demo.kxtwrdzt6g.workers.dev/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 georgi-petkov-personalknowhow 'https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "georgi-petkov-personalknowhow": {
      "url": "https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "georgi-petkov-personalknowhow": {
      "type": "http",
      "url": "https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.georgi-petkov-personalknowhow]
url = "https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "georgi-petkov-personalknowhow": {
      "type": "remote",
      "url": "https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add georgi-petkov-personalknowhow --url 'https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  georgi-petkov-personalknowhow:
    url: "https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "georgi-petkov-personalknowhow": {
      "Transport": "http",
      "Url": "https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add georgi-petkov-personalknowhow -t streamable-http -u 'https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "georgi-petkov-personalknowhow": {
      "type": "http",
      "url": "https://personalknowhow-demo.kxtwrdzt6g.workers.dev/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-20 (score 65, +1)

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

### 2026-09-18 (score 64, +1)

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

### 2026-09-15 (score 63, +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-09-13 (score 62, +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-09-11 (score 61, +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-09-09 (score 60, +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-09-08 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-07 (score 59)

First indexed and scored.

## MCP tools (4)

### `query_knowhow` (~355 tokens)

Query know-how

Search this person's real, grounded skills/experience graph for a topic using semantic search. Returns only entries with real evidence -- never guesses. Every entry here represents something actually done or completed (project, certification, position, course, or education) -- this public dataset never includes saved-but-not-worked jobs or applications. This is SEMANTIC search ranked by relevance and capped at 10 results -- it is NOT exhaustive. For 'list every X' or 'how many X' questions, use list_by_type instead -- it returns the complete, uncapped set with no similarity ranking involved. Clearing the similarity floor means 'closest available match', not 'confirmed match' -- read each result's actual label/description/type before citing it as evidence for the specific topic queried. Each result also carries source_url/captured_at/provider (the real evidence behind it, when available) and source_note (explaining why not, when the underlying source has no link) -- use these to answer a disputed claim with actual backing evidence rather than just the description text. Embeddings can rank a topically-adjacent-but-wrong entry above the floor (e.g. a course on a different cloud data-warehouse tool, or a different framework in the same category) for a term it isn't actually about; if a result isn't genuinely on topic, treat the query as unmatched rather than reporting it as a match. For 'what else is connected to this' or 'what shares a skill/provider with this specific entry' questions, call related_entries with a result's id instead of re-querying by topic.

Input parameters:

- `topic` (string, required): A skill, technology, or topic to check, e.g. 'django' or 'aws'

### `list_by_type` (~107 tokens)

List know-how by type

Returns the COMPLETE, exact set of entries for one type, with no similarity ranking, no relevance cutoff, and no cap on count. Use this instead of query_knowhow whenever the question requires an exhaustive or countable answer ('list all my certifications', 'how many courses have I completed'). Deterministic ordering (sorted by label) -- repeated calls with the same type return the same list in the same order.

Input parameters:

- `type` (string, required): Exact entry type to list in full

### `related_entries` (~258 tokens)

Find related entries

Given an entry id (from a prior query_knowhow or list_by_type result), returns other entries that share at least one tag or the same content provider -- the only two relationships this corpus currently tracks (there is no 'led to' or 'used in' relationship here, only shared tag/provider). This is NOT a similarity or relevance judgment -- two entries sharing a broad tag (e.g. both tagged 'data-science') can be quite different in substance; read each related entry's own label/type before treating it as meaningful. Each group is capped at 15 entries, sorted by label, with the true total count shown separately so you know if results were truncated -- call list_by_type on that type if you need the full set. Useful for 'what else is connected to X' or 'what did they do that relates to this specific course/certification/endorsement' -- questions query_knowhow's independent similarity search can't reliably answer, since two entries can be genuinely related without their description text reading alike (e.g. a course title and an endorsement phrase for the same skill, worded completely differently).

Input parameters:

- `id` (string, required): An entry id from a prior query_knowhow or list_by_type result

### `skill_evidence` (~233 tokens)

Find skill evidence

Given an exact tag/skill (e.g. 'docker', 'gcp'), returns EVERY entry with that tag, uncapped, grouped by type with a real count per type. Unlike related_entries (capped at 15, requires a starting entry id) or query_knowhow (semantic, ranked, may over- or under-include), this is an EXACT tag match against every entry -- the right tool for 'how many X have I completed/done' or 'do I have any real evidence for X at all'. Tags are exact strings from a prior list_by_type/related_entries/query_knowhow result's tags array -- this is NOT semantic search; a tag never assigned during ingest returns found:false, try query_knowhow instead. Each type's entries sort by captured_at ascending (oldest first); entries with no captured_at are moved to the end and counted in undated_count, never silently sorted as if their date were known.

Input parameters:

- `tag` (string, required): An exact tag from a prior result's tags array, e.g. 'python', 'docker', 'gcp'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/georgi-petkov-personalknowhow/personalknowhow-demo#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 64
- 2026-09-17: 63
- 2026-09-16: 63
- 2026-09-15: 63
- 2026-09-14: 62
- 2026-09-13: 62
- 2026-09-12: 61
- 2026-09-11: 61
- 2026-09-10: 60
- 2026-09-09: 60
- 2026-09-08: 59
- 2026-09-07: 59

## Common questions

### What is the PersonalKnowHow MCP server?

PersonalKnowHow is an MCP server listed in the public MCP registry as io.github.Georgi-Petkov/personalknowhow. Live public demo: query one person's learning and work history as a knowledge graph via MCP. This page covers its hosted endpoint (https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp).

### Is the PersonalKnowHow MCP server safe to use?

PersonalKnowHow scores 65 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 PersonalKnowHow MCP server expose?

PersonalKnowHow exposes 4 tools: query_knowhow, list_by_type, related_entries, skill_evidence. Their descriptions and schemas cost roughly 953 tokens of context every time the server is loaded.

### Does the PersonalKnowHow MCP server require authentication?

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

### Is the PersonalKnowHow MCP server still maintained?

PersonalKnowHow 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://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp
- Repository: https://github.com/Georgi-Petkov/personalknowhow
- Website: https://personalknowhow.com/
- Changelog RSS feed: https://verifymcp.io/servers/georgi-petkov-personalknowhow/personalknowhow-demo.xml
- Changelog JSON feed: https://verifymcp.io/servers/georgi-petkov-personalknowhow/personalknowhow-demo.json
- HTML version of this page: https://verifymcp.io/servers/georgi-petkov-personalknowhow/personalknowhow-demo