Vassiliy Lakhonin Profile
REMOTE · VASSILIY-LAKHONIN-MCP.VASSILIY-LAKHONIN.WORKERS.DEV · 2 COMPONENTS · SCANNED AUG 3
Read-only MCP profile server: CV, case studies, claim-to-evidence map, and role matching.
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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
Schema Quality & AI Usability67
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 772 tokens (~22/item across 35 items; 16 tools + 19 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev
claude mcp add --transport http vassiliylakhonin-profile-mcp https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse
[mcp_servers.vassiliylakhonin-profile-mcp] url = "https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vassiliylakhonin-profile-mcp": {
"type": "remote",
"url": "https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse",
"enabled": true
}
}
} openclaw mcp add vassiliylakhonin-profile-mcp --url https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse --transport streamable-http
mcp_servers:
vassiliylakhonin-profile-mcp:
url: "https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse" {
"mcpServers": {
"vassiliylakhonin-profile-mcp": {
"type": "http",
"url": "https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 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.
- 1 Aug 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.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 49
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 3 Aug 2026 · Probed https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vassiliy-lakhonin.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 20 Jul 2026 | 18 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 53f05463b7d0ca06ed34859b580a03368fb |
| SANs: *.vassiliy-lakhonin.workers.dev, vassiliy-lakhonin.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 | 404 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse | Verified | 200 | |
| http (plaintext) | http://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse | Served over HTTP | 200 |
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.
generate_cover_letter ~32
Generate concise evidence-backed cover letter draft.
| Name | Type | Req | Description |
|---|---|---|---|
| job_text | string | yes | — |
| tone | string | — | — |
No output schema declared.
No examples provided.
generate_pitch ~36
Generate outreach pitch. format: dm_short|email|proposal_intro
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | — |
| format | string | — | — |
No output schema declared.
No examples provided.
get_agent_card ~23
Return A2A-style agent card for capability discovery in agent workflows.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_availability ~22
Return current availability, preferred roles, locations, and notice period.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_capabilities ~17
Return machine-readable capability and service profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_case_study ~38
Return case study markdown. format: full|short|bullets
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | — | — |
| name | string | yes | — |
No output schema declared.
No examples provided.
get_engage ~24
Return structured outreach intake schema (engage.v2) for initiating engagement.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_evidence ~25
Return claim-to-evidence map: each key metric backed by source/proof.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_metrics ~17
Return normalized achievements list for scoring/automation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_profile ~29
Return profile in short or full mode. mode: short|full
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | — | — |
No output schema declared.
No examples provided.
get_resume ~22
Return full JSON Resume — work history, education, skills, links.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_skills ~23
Return machine-readable skill graph (domain, tools, methods, intent).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_verification ~18
Return cross-source identity and credential verification map.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_resources ~16
List all available resources and their URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
match_job ~38
Score fit against job text and return strengths/gaps/positioning.
| Name | Type | Req | Description |
|---|---|---|---|
| job_text | string | yes | — |
| role_target | string | — | — |
No output schema declared.
No examples provided.
search_profile ~22
Keyword search across profile + resume.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | — |
No output schema declared.
No examples provided.