Home / MCP registry index / ca.nikolajewdesign/portfolio-mcp
Portfolio MCP | Benjamin Nikolajew
ca.nikolajewdesign/portfolio-mcp in the official MCP registry.
Endpoint https://portfolio-mcp-dqj0.onrender.com/mcp.
The registry describes it as: Explore Benjamin Nikolajew's graphic design portfolio with natural language.
We read its 26 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_music list_portfolio_projects get_project_by_slug search_project_notes get_project_followup_detail get_project_artwork_gallery get_brand_kit get_professional_profile get_agent_capabilities get_career_timeline get_career_role_detail get_profile_fact_pack get_career_role_comparison get_download_documents get_download_assets get_career_certificates get_career_education get_changelog get_first_party_context search_first_party_context fetch_curated_page_context search_allowed_external_domains get_privacy_policy get_contact_email get_social_profiles get_about_resume
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ca-nikolajewdesign-portfolio-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.