MCP posture — Naftiko generates MCP servers, operates none
Naftiko is an MCP server GENERATOR, not an MCP server operator, and this file exists to hold that distinction rather than blur it. The Ikanos engine reads one capability YAML and serves it simultaneously over MCP, Agent Skill, REST and a Control port — MCP is a first-class exposure adapter in the published capability schema, with full tool, resource and prompt coverage. But the server that results is YOUR server: it runs on your infrastructure, and its tool list is whatever your capability YAML declares. Naftiko operates no hosted MCP endpoint of its own, so there is no URL an agent can POST tools/list to today. The one Naftiko-operated HTTP host found anywhere in this pass, mocks.naftiko.net, is a Microcks REST mock service and answers 401 on every path.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.