mc8yp 2.7.0 → 2.7.1

package/README.md

@@ -61,10 +61,46 @@ Behaviour worth knowing:
 - **The agent is told which namespaces are external.** `codemode.describe()` labels them `EXTERNAL MCP server at <url> — configured for this connection, NOT part of this tenant`, and the per-method describe repeats it. Whether a tenant namespace is backed by OpenAPI or MCP stays hidden (an implementation detail the agent cannot act on); tenant-vs-third-party is a data boundary it must be able to report on.
 - **Tool lists are fetched on first use and cached per MCP session**, then dropped 15 minutes after last use or immediately when the client closes its session cleanly. Rotating a token or changing a URL mid-session re-handshakes.
 - **A malformed entry fails the request** (HTTP 400 in server mode, a startup error in CLI) rather than silently leaving the agent without a namespace it was supposed to have. A well-formed but _unreachable_ server is reported in the `codemode.describe()` overview and retried on the next call.
-- **The tenant wins name collisions.** An external entry whose `name` matches a tenant namespace is skipped, so a header cannot shadow a real service.
+- **The tenant wins name collisions.** An external entry whose `name` matches a tenant namespace is skipped, so a header cannot shadow a real service. That skip is silent to the caller — use `POST /resolve-mcp-servers` (below) to catch it while configuring rather than discovering it as a missing namespace at run time.
 - **Egress is unrestricted by design.** The URL is used as given — any host, no allowlist, no private-range filtering. The header is part of the connection's trusted configuration (the sandbox cannot set it), but the consequence is that whoever can set headers on the deployed microservice can make it issue requests to any address it can reach, including tenant-internal ones. Front the deployment accordingly.
 - Path-based restriction/allow rules do **not** apply to these namespaces, same as for tenant-discovered MCP tools (see [Access policy](#access-policy)).
 
+#### Checking a configuration before you store it — `POST /resolve-mcp-servers`
+
+Whoever builds that header — a tenant admin UI, a deployment script — cannot answer three things on its own: which namespace an entry gets, whether that namespace is free, and whether the server actually answers with its credentials. This route answers all three in one call, so no consumer has to reimplement mc8yp's namespace rules or its MCP handshake:
+
+```http
+POST /service/mc8yp-server/resolve-mcp-servers
+Content-Type: application/json
+
+{ "servers": [{ "name": "MaStR registry", "url": "https://mastr.example/mcp", "token": "…" }] }
+```
+
+```jsonc
+{
+  "tenantUrl": "https://…cumulocity.com",
+  "tenantId": "t123",
+  "tenantNamespaces": ["c8y", "dtm", "knowledge_base_ms"], // null = the check could not run, see `warnings`
+  "warnings": [],
+  "servers": [
+    {
+      "name": "MaStR registry",
+      "namespace": "MaStR_registry", // derived — store THIS and send it in the header from now on
+      "status": "ok",                // ok | invalid | namespace-taken | unreachable
+      "server": { "name": "mastr-mcp", "version": "1.0.0" },
+      "tools": [{ "name": "search_units", "description": "…" }]
+    }
+  ]
+}
+```
+
+- **`name` may be free-form here.** It is sanitized into the namespace exactly as a contextPath is (`MaStR registry` → `MaStR_registry`, the same rule that makes `knowledge-base-ms` into `knowledge_base_ms`). An identifier passes through unchanged.
+- **`status` is the field to branch on**, and `namespace-taken` is the interesting one: reserved name, a namespace this tenant already holds, or a duplicate inside the same request. That is the collision that would otherwise be a silent skip at run time — `namespaceTakenBy` says who holds it. Tools are still reported for a taken entry, so renaming is the only fix needed.
+- **The header contract does not change.** Derivation is a configure-time convenience: resolve once, store the `namespace` you got back, keep sending it verbatim. The agent-visible namespace stays stable even if the derivation is refined later.
+- **Validation is the header's own**, so this route cannot green-light an entry the header would then 400.
+- **Nothing is persisted, and nothing is cached.** mc8yp holds no external server configuration of its own, and the handshake bypasses the per-session tool-list cache so the answer always reflects the credentials as sent.
+- Requires user auth (Authorization header or session cookie), like `POST /refresh-apis`.
+
 ## Two ways to run it
 
 - **Microservice mode** (recommended for production) — deploy inside Cumulocity IoT, expose `/mcp`, integrate with [AI Agent Manager](https://cumulocity.com/docs/ai/aim-introduction/). Auth comes from the request and the service user.

package/dist/cli.mjs

@@ -1546,7 +1546,7 @@ const consola = createConsola();
 //#endregion
 //#region package.json
 var name = "mc8yp";
-var version = "2.7.0";
+var version = "2.7.1";
 var description$1 = "Cumulocity IoT MCP Server - Model Context Protocol integration for IoT device management";
 //#endregion
 //#region \0virtual:core-openapi
@@ -78260,7 +78260,7 @@ function parseExternalMcpServers(sources) {
 			continue;
 		}
 		for (const candidate of Array.isArray(parsed) ? parsed : [parsed]) {
-			const result = validateEntry(candidate, usedNames);
+			const result = validateExternalMcpEntry(candidate, usedNames);
 			if ("reason" in result) {
 				failedEntries.push({
 					entry: typeof candidate === "object" ? JSON.stringify(candidate) : String(candidate),
@@ -78277,7 +78277,14 @@ function parseExternalMcpServers(sources) {
 		failedEntries
 	};
 }
-function validateEntry(candidate, usedNames) {
+/**
+* Validate one entry, exported so the resolve route can answer with the exact
+* verdict the header path would reach — a route that green-lights a server the
+* header then rejects is worse than no route at all.
+* @param candidate Parsed JSON entry.
+* @param usedNames Namespaces already taken by earlier entries in the same batch.
+*/
+function validateExternalMcpEntry(candidate, usedNames) {
 	if (typeof candidate !== "object" || candidate === null || Array.isArray(candidate)) return { reason: "Entry must be a JSON object with \"name\" and \"url\"." };
 	const entry = candidate;
 	if (typeof entry.name !== "string" || entry.name === "") return { reason: "\"name\" is required and must be a non-empty string — it becomes the sandbox namespace." };
@@ -78358,7 +78365,18 @@ function armIdleTimer(sessionKey) {
 	session.timer = setTimeout(() => evictExternalMcpSession(sessionKey, "idle-timeout"), IDLE_TTL_MS);
 	session.timer.unref?.();
 }
-async function listExternalTools(config) {
+/**
+* Handshake one external server and read its tool list, bypassing the session
+* cache entirely.
+*
+* Exported for configuration checks (`POST /resolve-mcp-servers`): an operator
+* asking "does this URL and token work" must not be answered from a tool list
+* cached up to 15 minutes ago, and a candidate that may never be saved must not
+* seed the cache either. Runtime resolution goes through
+* {@link resolveExternalMcpServers}, which is where caching belongs.
+* @param config One external server config.
+*/
+async function probeExternalMcpServer(config) {
 	const client = new McpHttpClient({
 		url: config.url,
 		fetch: createExternalMcpFetch(config)
@@ -78370,7 +78388,9 @@ async function listExternalTools(config) {
 		return {
 			config,
 			tools,
-			instructions: info.instructions
+			instructions: info.instructions,
+			serverName: info.serverName,
+			serverVersion: info.serverVersion
 		};
 	} finally {
 		await client.close();
@@ -78400,7 +78420,7 @@ async function resolveExternalMcpServers(sessionKey, configs) {
 		const key = configKey(config);
 		let pending = session.servers.get(key);
 		if (!pending) {
-			pending = listExternalTools(config);
+			pending = probeExternalMcpServer(config);
 			session.servers.set(key, pending);
 			pending.catch(() => {
 				if (session.servers.get(key) === pending) session.servers.delete(key);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mc8yp",
-  "version": "2.7.0",
+  "version": "2.7.1",
   "type": "module",
   "description": "Cumulocity IoT MCP Server - Model Context Protocol integration for IoT device management",
   "keywords": [