https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp ↗
Live public demo: query one person's learning and work history as a knowledge graph via MCP.
PersonalKnowHow is a remote MCP server published at personalknowhow-demo.kxtwrdzt6g.workers.dev. It has been probed 7 times since 9/12/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 391 ms, placing it among the faster endpoints. It offers a narrow, focused set of 4 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
query_knowhow — Description cut off mid-sentence, missing critical details about datasetlist_by_type — Truncated explanation of use cases and limitationsskill_evidence — Incomplete description of exact tag matching capabilitiesrelated_entries — Unclear relationship definitions due to incomplete textRisk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
query_knowhowSearch 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. Eac
topicstringrequiredlist_by_typeReturns 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.
typestringrequiredrelated_entriesGiven 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 speci
idstringrequiredskill_evidenceGiven 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 sort
tagstringrequiredDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-georgi-petkov-personalknowhow)<a href="https://mcpmetrics.io/servers/io-github-georgi-petkov-personalknowhow"><img src="https://mcpmetrics.io/badge/io.github.Georgi-Petkov/personalknowhow/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Anonymous read-only access to source-backed public SHAR Production knowledge.
Mochii work graph: projects, tasks, meetings. Stiki OAuth. Not Nexus memory.
Search Vascue's public healthcare-ops, insurance-claims and booking docs. Public content only.
Architecture-grounded query for AI agents. Governance constraints, evidence-linked answers.
Read-only Arabic and English Taxi Rido product knowledge and taxi operations guides.
Dutch vehicle model knowledge, terminology, comparisons and cited sources for AI clients.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 04:35:29 | Dual-era | 200 | 281 | 200 | 271 | 2026-07-28 |
| 2026-09-13 01:33:33 | Dual-era | 200 | 251 | 200 | 278 | 2026-07-28 |
| 2026-09-12 23:31:36 | Dual-era | 200 | 283 | 200 | 379 | 2026-07-28 |
| 2026-09-12 21:29:15 | Dual-era | 200 | 389 | 200 | 436 | 2026-07-28 |
| 2026-09-12 19:27:29 | Dual-era | 200 | 1517 | 200 | 1504 | 2026-07-28 |
| 2026-09-12 17:24:09 | Dual-era | 200 | 509 | 200 | 391 | 2026-07-28 |
| 2026-09-12 15:21:42 | Dual-era | 200 | 676 | 200 | 525 | 2026-07-28 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.