MCP, tools and skills

Planned. Native 0.0.1 has no MCP client, skill loader or operational tool installation manager. The atlas catalog contains research references and authored proposals; none becomes connected because its card exists.

Distinct lifecycle states

Discovery, source review, installation, enablement, authentication, connection, tool discovery and availability to a particular run are separate states. A successful protocol handshake does not prove that the model can call the tools correctly or that every requested side effect is authorized.

For each integration, retain source/provenance, immutable version, transport, actual endpoint or launch command, requirements, authentication method, permissions, last error and removal behavior. A planned adapter without a real endpoint must say so.

Local and remote transports

Owned stdio servers need explicit working directories, environment allowlists, hidden Windows child windows, timeouts, bounded output and tracked process trees. Imported configuration should be inert until its launch plan has been reviewed. Do not copy all host environment secrets into every child.

Remote servers require verified endpoint identity, scoped authentication, cancellation and error handling. Host-side secrets must not enter renderer state, shareable presets, diagnostic logs or generated examples. Tool schemas are untrusted input and need validation and bounds.

What is a skill?

A skill is reviewable instructions and supporting resources for a workflow. It does not create a new model capability or grant permissions. Track its source, version, intended tools, required resources and licensing. Instructions embedded in a skill, repository or external page cannot override the user’s policy or the broker’s effective role.

Catalog and Reges World

The atlas research catalog has 130 entries, including 73 MCP references/proposals, plus skills, agents, tools, bots and pets. Seven Reges World projects are grouped together: MotionVault, AnimatedWebs, TrustCertia, MyLittleBots, RegesCode, RegesCore and RegesTown. Existing endpoint evidence and proposed adapters remain distinguished. AnimatedWebs remains in the RegesARC catalog independently of any assistant connection setting.

The MCP specification and LM Studio’s MCP guide are primary protocol/product references. RegesARC qualification still requires native transport tests, real authentication, model tool-format evaluation, permission checks, cancellation and observable host effects.