The systems agents most need to reach are the ones enterprises already run: the CRM, the claims engine, the SaaS with a good HTTP API and no MCP server. Making them reachable is no longer the hard part — more than 10,000 MCP servers are reported in production and the protocol’s SDKs are downloaded upwards of 97 million times a month. What has not kept pace is the part enterprises are accountable for: knowing what a given MCP server exposes, which upstream operations its credential can reach, and whether either changed since the last review.
The unit that closes that gap is the capability — a business-shaped operation, declared once, that says what it does rather than how it does it. As Naftiko traced across three independent disciplines, the word arrived from business architecture in 2006, API design strategy and platform engineering in 2023, and context engineering in 2025. Agents did not invent these boundaries; they inherited them.
Today Naftiko is joining the Agentic AI Foundation (AAIF) as a Silver member — and, through it, the Linux Foundation — to work on that gap alongside the rest of the ecosystem.
Why the AAIF
The AAIF was formed in December 2025 as a neutral home for the plumbing of the agent era: Anthropic donated the Model Context Protocol, Block donated goose, and OpenAI donated AGENTS.md, with AWS, Bloomberg, Cloudflare, and Google joining at launch. Roadmaps are set by technical steering committees, not by whoever pays the most dues.
That model is why Naftiko is joining rather than simply consuming the standard. Naftiko’s product line assumes MCP is a neutral, durable protocol. When the 2026-07-28 revision landed — the largest breaking change since authorization — capabilities running on Naftiko’s engine absorbed it as a single image-tag upgrade, with no edits to any capability file. That outcome depends on the protocol evolving in the open.
What Naftiko Brings
Naftiko’s contribution is a practical one: the capability as a declarative and reviewable artifact.
The recurring problem is not missing policy. It is that you cannot enumerate, by reading general-purpose server code, the complete set of upstream operations a credential will ever authorize. Computed URLs and dynamic dispatch defeat static analysis, so reviewers certify one observed run instead of the thing that runs. A capability inverts that: one declarative file names every upstream operation it consumes and every credential binding it needs, then exposes one business-shaped surface — readable by a human, a linter, and a policy engine before anything deploys.
For developers, publishing an MCP server should not require writing and maintaining a server. With Ikanos, a capability is declared once in YAML over the APIs a team already owns, then served as MCP tools, resources, and prompts — alongside REST and Agent Skills — from one deployment. Protocol revisions arrive as engine upgrades, not migration projects.
For organizations, the same file is the review surface. Polychro, Naftiko’s deterministic linter, validates it through layered checks and runs both as a CLI in CI and as an MCP server. That linting extends to Markdown, with format profiles shipping today for AGENTS.md — the file OpenAI donated to the AAIF — plus SKILL.md, *.instructions.md, and *.prompt.md. A malformed AGENTS.md does not fail loudly; it silently changes how an agent behaves. One linter covers prose specs and capability YAML alike.
Naftiko will engage across the Identity & Trust, Security & Privacy, Observability & Traceability, and Governance, Risk & Regulatory Alignment working groups.
Sponsoring MCP Dev Summit Toronto
Naftiko will sponsor MCP Dev Summit Toronto on October 5-6, 2026, part of the AAIF’s global developer series. Naftiko’s team will be on site to talk through capability specifications, protocol migration, credential scoping, and what enterprise reviewers ask for before approving an agent-facing surface.
Quote from Naftiko
“MCP solved the connection problem so thoroughly that it exposed the next one. Any developer can stand up an MCP server over an existing API in an afternoon — and no reviewer can tell you, by reading it, what that server will do with the credential you gave it. That gap is where agent projects stall between demo and production.
The answer is not a new protocol. It is an older idea: a capability that declares what it does rather than how, in a file you can read before you run it. That belief is why Ikanos and Polychro are Apache 2.0 in every edition and will stay that way — governance you have to buy is not governance, it is a feature gate. We joined the AAIF to put that argument in front of the working groups and find out where the community proves us wrong.”
— Jerome Louvel, CEO & Co-Founder, Naftiko
Availability
Ikanos v1.0.0-beta5 (“Bark”) shipped today, continuing support for the 2026-07-28 MCP specification with no breaking schema change. The release hardens the supply chain — every published binary and Docker image is now automatically scanned before it ships, with SHA256 checksums and an SBOM on each artifact — and lands the project’s first fix from an external contributor.
- Learn about the AAIF: aaif.io
- Attend MCP Dev Summit Toronto: October 5-6, 2026
- Run Ikanos: github.com/naftiko/ikanos (Apache 2.0)
- Lint with Polychro: github.com/naftiko/polychro (Apache 2.0)
- Read the docs: shipyard.naftiko.io
About Naftiko
Naftiko reinvents API integration for the AI era. Its governed, spec-driven platform transforms the fragmented landscape of SaaS APIs, microservices, and AI tools into a unified capability Fleet — discoverable by humans and machines, governed by policy, and observable by design. Founded on the values of openness, sustainability, and responsible use, Naftiko is building the connective tissue between enterprise API investments and the AI-powered future. Naftiko operates from Philadelphia and Paris.
| Media Contact: press@naftiko.io | naftiko.io |
