Server data from the Official MCP Registry
Read-only MCP profile server: CV, case studies, claim-to-evidence map, and role matching.
Read-only MCP profile server: CV, case studies, claim-to-evidence map, and role matching.
Remote endpoints: streamable-http: https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/mcp sse: https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/sse
This is a legitimate personal portfolio MCP server for a professional profile with appropriate read-only permissions. The code fetches public profile data from GitHub Pages with no authentication, credential handling, or dangerous operations. Minor code quality observations around broad exception handling and input validation do not significantly impact security posture. Supply chain analysis found 10 known vulnerabilities in dependencies (0 critical, 5 high severity).
5 files analyzed · 15 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
Personal portfolio site of Vassiliy Lakhonin — I build evidence-discipline tooling for strategic-risk AI agents (Agenda Intelligence: an open-source skill portfolio plus deployed A2A workers and a public CIS counterparty EDD browser demo), grounded in donor compliance, audit readiness, and cross-border program delivery.
This repository is two things at once:
llms.txt, agent-card.json), recruiter routing, and an MCP server.It is not a fork-and-go starter template — the content is personal. Other people are welcome to study the architecture and adapt it for their own profile.
Recent research on AI self-preferencing in algorithmic hiring suggests that LLM evaluators can favor resume text that resembles their own outputs, even when candidate quality is controlled. This repo treats that as a design constraint: publish multiple verified surfaces so humans, ATS systems, and recruiter agents can compare claims, evidence, role fit, and contact details instead of relying on one polished resume style.
See AGENTS.md for the canonical rules any AI agent (Claude Code, Codex, recruiter LLMs) should follow when reading or editing this repo.
This site is the distribution surface for two workflow products awaiting external validation and a separately maintained four-repository strategic-risk stack.
Workflow products:
.docx / .xlsx / ZIP exports. Two delivery paths — an operated pilot, or MCP / HTTP interfaces for teams embedding the workflow. Being tested case by case; the API and hosted demo are not demand evidence.Strategic-risk stack:
check_evidence_packet, with create_brief and append_evidence for contract-aware assembly. Older HTTP / A2A and vertical-worker surfaces remain available for compatibility; they are not the primary product narrative.The three reasoning repos now use the same handoff into Agenda Intelligence MD: memo → externally checkable claims + declared source IDs + supplied source text + optional verbatim quotes → deterministic packet check → human review. Each repo ships a synthetic packet, a local validator, and a CI check. Historical analyze / MCP evals remain compatibility evidence rather than proof of the current linter.
index.md, for-recruiters.md, profile.md, role snapshots in role-*.md, case studies in case-study-*.md.resume.json, skills.json, capabilities.json, availability.json, verification.json, recruiter.json, engage.json, evidence.json.agent-card.json, agent-discovery.md, llms.txt (short routing index) and llms-full.txt (complete inventory).connect.md — MCP install commands per client, the A2A call pattern, and what each surface may claim.candidate-match.json, agent-match.md, for-recruiters.md.mcp/server.py (runnable locally) plus a remote deployment live on Cloudflare Workers at https://vassiliy-lakhonin-mcp.vassiliy-lakhonin.workers.dev/mcp (streamable HTTP) — see mcp-status.json. Both implementations expose 16 tools, 19 attachable resources, and 5 prompts (screen_for_role, check_claim, route_my_problem, brief_before_call, draft_outreach). Worker source: mcp/cloudflare-worker/.freshness.json, provenance.json, readiness.json, evals.json, authority.json. Values are self-reported snapshots, not validated benchmarks.docs/analytics-measurement-plan.md.flowchart LR
A[Markdown and JSON profile source] --> B[GitHub Pages site]
A --> C[Machine-readable endpoints]
C --> D[AI search and retrieval]
C --> E[MCP Server]
E --> F[Recruiter and agent clients]
A --> G[CI audits and observability]
.
├── AGENTS.md
├── index.md
├── for-recruiters.md
├── profile.md
├── resume.json
├── capabilities.json
├── evidence.json
├── availability.json
├── skills.json
├── verification.json
├── agent-card.json
├── agent-discovery.md
├── llms.txt
├── mcp/
│ ├── server.py
│ ├── cloudflare-worker/
│ ├── README.md
│ └── requirements.txt
├── scripts/
└── .github/workflows/
If you want to reuse the pattern (not the content):
AGENTS.md and docs/AI_HIRING_READINESS.md to understand the model.scripts/.python3 scripts/geo_quick_audit.py
python3 scripts/schema_audit.py
python3 scripts/build_readiness_report.py
python3 scripts/build_freshness_report.py
python3 scripts/build_evals_report.py
python3 scripts/build_provenance_report.py
Optional CIS EDD source-freshness snapshot:
python3 scripts/sanctions_source_snapshot.py
Optional CIS EDD static sanctions-name index for the browser-side preview:
python3 scripts/sanctions_name_index.py
The name index supports public-list string matching only. It is not identity verification, ownership resolution, a 50% rule determination, or legal / compliance advice.
bundle exec jekyll serve
python3 -m pip install -r mcp/requirements.txt
python3 mcp/server.py --http
# then: http://localhost:8000/health / http://localhost:8000/sse
MIT — applies to the code and architecture. Personal content (CV, case studies, claims about Vassiliy Lakhonin) is not licensed for reuse.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.