The GitHub MCP Registry exists. It is a real piece of infrastructure now — vendors publish into it, enterprises mirror it, IDEs are starting to point at it for discovery.

The problem with the registry today, as a developer, is that it is a webpage you scroll. Your agent reads it badly. Your security team queries it manually. Your platform automation cannot really call it as a tool because it does not look like one — it looks like a JSON catalog of metadata, with search-as-keyword.

This post is the engineering version of the argument: wrap the registry as a Naftiko capability, expose three surfaces from one spec, and turn it into something every consumer (humans, agents, pipelines) can call the same way.

The shape of a Naftiko capability

A Naftiko capability YAML is a single artifact that declares two things:

consumes — what upstream APIs the capability calls

exposes — what surfaces the capability serves outward (REST, MCP, Agent Skills)

The Naftiko Engine runs the spec.…