Home / MCP registry index / io.github.macacoengenhocas/skoia-parts
SkoIA Parts
io.github.macacoengenhocas/skoia-parts in the official MCP registry.
Endpoint https://parts.skoia.me/mcp.
The registry describes it as: Resolve part problems, check compatibility and identify only the information still missing.
We read its 15 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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
understand_physical_problem get_next_observation generate_hypotheses search_candidates synthesize_physical_solution verify_solution generate_artifact get_verified_commerce_options search_parts resolve_problem get_product get_compatibility get_fit_guidance list_generation_options get_offers
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-macacoengenhocas-skoia-parts)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.