AIFACTORY-FEAT-028: McpServerRegistryService: thin delivery for the first outcome¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
A design artefact, not a tracker
This backlog is generated from model/backlog/ and validated against the architecture model. No work item exists in any tracker, and no item carries a date, an estimate or an assignee (ADR-0029).
Epic Tools & MCP Platform (PF-05) · Increment I1 Generate a microservice · State elaborated · Route backend-developer · Build order 67 of 185 (Factory code)
McpServerRegistryService is the service of bounded context BC-08 (Tool Execution). Registry of MCP servers the Factory consumes or exposes — transport, endpoint or connection, authentication (on by default), governance policy, discovered tools, resources and prompts bound to tool descriptors and knowledge sources, handshake health and the ModelOps-like lifecycle from registration to retirement (BC-08, ADR-0022). In this increment it is delivered thin: A static registry without MCP servers; every tool of the chain is native. Its own repository is ConnectSoft.AI.SoftwareFactory.McpServerRegistryService.
| Delivers | McpServerRegistryService (thin): A static registry without MCP servers; every tool of the chain is native. |
| Stubs | — |
| Realizes | adrs: ADR-0022, ADR-0015 |
| Requirements | FR-02, FR-05, FUX-02, NFR-02, NFR-13, XL-02, XL-10 |
| Depends on | — |
| Sources | model/services/tools-mcp/McpServerRegistryService.yaml |
Scenarios to trace (11, catalog): SCN-McpServerRegistryService-001 ✓, SCN-McpServerRegistryService-002, SCN-McpServerRegistryService-003, SCN-McpServerRegistryService-004, SCN-McpServerRegistryService-005, SCN-McpServerRegistryService-006, SCN-McpServerRegistryService-007 ✓, SCN-McpServerRegistryService-008 ✓, SCN-McpServerRegistryService-009, SCN-McpServerRegistryService-010, SCN-McpServerRegistryService-011
AIFACTORY-US-064: McpServerRegistryService answers the chain with its thin contract¶
behavior · persona asset-maintainer
As an asset maintainer, I want McpServerRegistryService to answer the calls of the first-outcome chain with a well-formed result of its thin scope, so that the Tool Execution context has one owner of MCP servers that the rest of the Factory calls through its contract.
This is the integration PBI of the thin delivery. Every tool the first outcome calls is native: the six workflow definitions of the chain and their nine agents name fifteen tools of the tool catalogue under model/tools, each of kind native, and no descriptor that ToolAdapterService activates in this increment names an mcpServerId. McpServerRegistryService is therefore delivered thin, and the thin scope the feature states is exactly this: a static registry without MCP servers. Static means that no operation of the delivery writes a server, a binding or an event. The service hosts the three read operations that do not address a server by its id: ListMcpServers (AIFACTORY-US-596) and the internal gRPC methods McpRegistry.ResolveTool and McpRegistry.ListCapabilities (AIFACTORY-US-597). They read the store mcp-server-registry-sql, whose four tables are migrated by this delivery and hold no row on a deployed instance. Nothing else is served. RegisterMcpServer, DiscoverMcpCapabilities, ActivateMcpServer, RetireMcpServer and GetMcpCapabilities, the three events of the McpServer aggregate, the workers HandshakeProbe and CapabilityDiscovery, the handlers of AssetReleasePublished, AssetReleaseRevoked and ConnectionStateChanged and the calls to IntegrationService, SecretBrokerService and PolicyEngineService arrive with feature mcp-server-registry-service-complete in I5. The handler of DeletionOrderIssued is built in I4 with RetentionResidencyService and is not registered here. The repository ConnectSoft.AI.SoftwareFactory.McpServerRegistryService is created and scaffolded in I0 by AIFACTORY-TASK-073 of feature repository-and-pipeline-conventions (D140) from the pinned base template package with UseFactoryProfile, and this feature starts from that scaffold, so token validation, the scope chain with its 401, 403 and 404 answers, the tenant row filter, health, readiness and the telemetry wiring come from the profile and are not written again; the messaging profile is the Orleans profile under the service name mcp-server-registry, and the thin delivery declares no published and no consumed event in it. The model names tool-invocation-v1 as the request and the reply descriptor of McpRegistry.ResolveTool and as the reply descriptor of McpRegistry.ListCapabilities. docs/reference/schemas/tool-invocation.schema.json describes a tool call: it requires the arguments, the policy decision and the idempotency key, which a resolution does not have, allows no additional property and holds mcpServerId but no member for a transport, a binding or an authentication. That conflict is an open point reported to the owner, and it concerns both directions: the delivery replaces the request descriptor of McpRegistry.ResolveTool too, by a message of tool id and tool version, beside the reply descriptor of both methods. The thin delivery makes its contract checkable without deciding the point: the proto fixes the request and reply messages of the two methods and the OpenAPI document fixes the list (AIFACTORY-TASK-075), and a contract test with golden files holds them. The golden files of the two gRPC messages are provisional until the owner names the request and reply descriptors; when the owner does, the messages change and ToolAdapterService, their one caller, follows them. No promise of an unchanged contract is made for them. The complete delivery adds its operations, its write paths and its events on the same tables, and only the shape of the list of ListMcpServers is meant to stay as this delivery fixes it. A caller without a token, without a workload identity or without the scope of the operation, and a workload call that forwards no tenant, is refused before any handler runs.
Acceptance criteria
| AC1 | Given the repository ConnectSoft.AI.SoftwareFactory.McpServerRegistryService created and scaffolded in I0 by AIFACTORY-TASK-073 of feature repository-and-pipeline-conventions with dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.McpServerRegistryService --UseFactoryProfile true from the pinned template package, when its pipeline runs, then the solution builds, the unit and acceptance tests pass with complete reports and a container image is published (ADR-0028, model/services/tools-mcp/McpServerRegistryService.yaml). |
| AC2 | Given the deployed thin service with its migrated and empty store, when a caller with factory.tools.read calls McpServerRegistryService/ListMcpServers and ToolAdapterService calls McpServerRegistryService/McpRegistry.ResolveTool and McpServerRegistryService/McpRegistry.ListCapabilities under a workload token that holds the service scope and forwards its tenant, then the list is empty and well formed, every resolution is answered NOT_FOUND and the capability list is empty, as AIFACTORY-US-596 and AIFACTORY-US-597 prove one by one (ADR-0022). |
| AC3 | Given the service descriptor of the thin delivery, when the contract test of the Factory profile compares it with the hosted surface, then exactly McpServerRegistryService/ListMcpServers, McpServerRegistryService/McpRegistry.ResolveTool and McpServerRegistryService/McpRegistry.ListCapabilities are hosted, no REST operation that writes a server answers, the OrleansMessaging section declares no published and no consumed event, and the test fails when an operation outside the thin scope stated in model/backlog/features/tools-mcp.yaml appears; the golden files of the two gRPC messages are marked provisional in the contract test, because the request and reply descriptors the model names (tool-invocation-v1) cannot carry a resolution and the owner has yet to name the descriptors. |
| AC4 | Given a call without a token, without a workload identity or without the scope of the operation, or a workload call that forwards no tenant, when it reaches one of the three operations, then it is refused before any handler runs and nothing is read (ADR-0015); given the service starts, when liveness and readiness are probed, then liveness answers and readiness is unready until mcp-server-registry-sql is migrated and the identity authority is reachable (model/services/tools-mcp/McpServerRegistryService.yaml). |
| Traces: services | McpServerRegistryService |
| Traces: apis | McpServerRegistryService/ListMcpServers, McpServerRegistryService/McpRegistry.ResolveTool, McpServerRegistryService/McpRegistry.ListCapabilities |
| Traces: descriptors | tool-invocation-v1, execution-scope-v1 |
| Traces: adrs | ADR-0015, ADR-0022, ADR-0028 |
| Depends on | AIFACTORY-US-596, AIFACTORY-US-597, feature:repository-and-pipeline-conventions, feature:component-base-template-factory-profile, feature:component-base-template-findings |
| Sources | model/services/tools-mcp/McpServerRegistryService.yaml, model/backlog/features/tools-mcp.yaml, docs/architecture/adr/0022-mcp-as-tool-protocol.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, docs/reference/schemas/tool-invocation.schema.json |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-075 Contract of the thin surface: service descriptor, OpenAPI document of ListMcpServers and proto of McpRegistry.ResolveTool and McpRegistry.ListCapabilities |
contract | The service descriptor file of the repository lists exactly ListMcpServers (GET /factory/mcp-servers, scope factory.tools.read, class read) and the internal gRPC methods McpRegistry.ResolveTool and McpRegistry.ListCapabilities (no streaming, class read). The OpenAPI document fixes the paged list with serverId, name, direction, transport, authentication, state and the binding counts of a server. The proto fixes the request message of ResolveTool (toolId and toolVersion), its reply message (serverId, transport, endpointRef or commandRef, authentication, governancePolicyRef, protocolVersion, toolName, schemaHash and declaredClass, and no credential value), the request message of ListCapabilities (the execution scope) and its reply message (tools, resources and prompts, each with its binding). A contract test with golden files holds the three shapes; it does not validate a reply against docs/reference/schemas/tool-invocation.schema.json, which describes a tool call and has no member for a transport, a binding or an authentication, and that difference is the open point the PBI reports. The golden files of the two gRPC messages are provisional until the owner names the request and reply descriptors of the two methods, the replaced request descriptor of ResolveTool included; only the shape of the list is meant to stay for the complete delivery. The contract test of the Factory profile compares the hosted endpoints with the service descriptor file in both directions, so callers run against this service without a fake. | ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |
AIFACTORY-TASK-790 Verify mcp-server-registry-service-thin-contract by running the declared command |
verification | Run dotnet build -c Release and dotnet test -c Release --no-build in the pipeline of the repository; a run that discovers no test counts as a failure; the runs pass and prove AC1 to AC4 of AIFACTORY-US-064, that is the scaffold, the three hosted operations answering on an empty store (SCN-McpServerRegistryService-001, SCN-McpServerRegistryService-007, SCN-McpServerRegistryService-008), the thin surface against the service descriptor, the golden files of the three shapes, readiness that stays unready until the store is migrated and the refusal of a caller without a token, a workload identity or the scope. |
ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |
AIFACTORY-US-596: List the MCP servers of the tenant from a static registry whose store holds no server¶
behavior · persona asset-maintainer
As an asset maintainer, I want to list the MCP servers registered for my tenant and see that none exists yet, so that I know that every tool of a run is native until a server is registered and activated through the complete registry.
A caller whose scope carries factory.tools.read lists the registered MCP servers through the gateway route of McpServerRegistryService/ListMcpServers; the roles of the model that read the registry are Asset maintainer, Operator, Platform admin and Observer. ToolExecutorHost forwards the user token unchanged, and the service validates it again, accepts the audience of its own gateway and takes the tenant from the token, never from a header or the query (ADR-0015 amendment D117). A server belongs to a tenant: the table McpServers has a tenant column and no project column, so the list is filtered by the tenant row filter of the Factory profile and by nothing else. The response is 200 with a paged list in which each server carries serverId, name, direction, transport, authentication, state and the counts of its tool, resource and prompt bindings, the bound and the unbound tools counted apart. The thin delivery migrates the four tables of the model in mcp-server-registry-sql, the store this service owns: McpServers with the index on tenant, state and direction, McpToolBindings, McpResourceBindings and McpPromptBindings, each with the tenant column. No column holds a credential value, because a consumed server names a connection reference in EndpointRef and its credentials are brokered. No operation of the thin delivery writes a row, so on a deployed instance the answer is an empty, well-formed list for every tenant, in the response shape the complete delivery fills. The read model itself is real and is proven as such: the acceptance suite inserts fixture rows of two tenants directly into the isolated test database, because no operation writes them, and the list returns the server of a tenant with its counts to that tenant and never to the other one. A call without a token is answered 401 and a token without factory.tools.read 403, each with a problem response; the list never confirms that a server of another tenant exists. Nothing is written by the read and no event is published. The metric connectsoft.factory.tools.mcp_servers is registered with its dimensions tenant, direction, state and authentication and records nothing, because it moves with a state change of a server and the thin delivery has none.
Acceptance criteria
| AC1 | Given a caller whose scope carries factory.tools.read and the deployed thin service with its empty store, when McpServerRegistryService/ListMcpServers is called, then the response is 200 with an empty paged list in the response shape of the OpenAPI document, nothing is written and no event is published (SCN-McpServerRegistryService-001). |
| AC2 | Given fixture rows inserted directly into the isolated test database, one McpServerRegistryService/McpServer of tenant A in state Active with two bound tool bindings and one unbound, when a caller of tenant A and a caller of tenant B each call McpServerRegistryService/ListMcpServers, then tenant A receives the server with serverId, name, direction, transport, authentication, state and the binding counts and tenant B receives an empty list that does not reveal the server (SCN-McpServerRegistryService-001, ADR-0015). |
| AC3 | Given a call without a token or a token without factory.tools.read, when McpServerRegistryService/ListMcpServers is called, then the response is 401 or 403 with a problem response, no row is read and no state changes (SCN-McpServerRegistryService-001, ADR-0015). |
| AC4 | Given the migrated mcp-server-registry-sql, when its schema is compared with model/services/tools-mcp/McpServerRegistryService.yaml, then the tables McpServers, McpToolBindings, McpResourceBindings and McpPromptBindings exist with their columns, keys and the index on tenant, state and direction, every table carries the tenant column under the row filter, no column holds a credential value, and no operation of the thin delivery writes a row (ADR-0022). |
| Traces: services | McpServerRegistryService |
| Traces: aggregates | McpServerRegistryService/McpServer |
| Traces: apis | McpServerRegistryService/ListMcpServers |
| Traces: adrs | ADR-0015, ADR-0022 |
| Traces: requirements | FR-05, FUX-02 |
| Traces: scenarios | SCN-McpServerRegistryService-001 |
| Depends on | feature:component-base-template-factory-profile |
| Sources | model/services/tools-mcp/McpServerRegistryService.yaml, model/backlog/features/tools-mcp.yaml, docs/planes/capability-tools/tools/services/mcp-server-registry-service/index.md#data-model-and-storage, docs/planes/capability-tools/tools/services/mcp-server-registry-service/index.md#apis |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-074 Migration and read mappings of McpServers, McpToolBindings, McpResourceBindings and McpPromptBindings in mcp-server-registry-sql |
migration | The four tables of model/services/tools-mcp/McpServerRegistryService.yaml exist with their columns, keys, foreign keys and the index IX_McpServers_Tenant_State; the read mappings carry the tenant row filter of the Factory profile; mapping tests run against an isolated test database, never a shared one. No write path exists in the thin delivery: the store of a deployed instance stays empty, which is the static registry without MCP servers the feature states, and the write paths of registration, discovery, activation and retirement are added by feature mcp-server-registry-service-complete on the same tables. | ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |
AIFACTORY-TASK-2401 ListMcpServers read model with the tenant row filter, paging and binding counts |
implementation | ListMcpServers returns the servers of the trusted tenant paged, each with serverId, name, direction, transport, authentication, state and the counts of bound tools, unbound tools, resources and prompts, takes the tenant from the validated token, answers 401 without a token and 403 without factory.tools.read through the policies of the Factory profile, writes nothing and returns an empty list when the tenant has no server; the meter connectsoft.factory.tools.mcp_servers is registered with its modelled dimensions. | ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |
AIFACTORY-TASK-2402 Verify the list of the static registry through the acceptance suite |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Scenario=SCN-McpServerRegistryService-001"; a zero-match filter counts as a failure; the tests prove AC1 to AC4 of AIFACTORY-US-596: the empty list of a deployed instance, the two-tenant fixture rows inserted directly into the isolated test database, the 401 and the 403, and the schema of the four tables compared with the model. |
ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |
AIFACTORY-US-597: Resolve a tool to its MCP server for the executor and list the capabilities of a scope, both answered from a registry without servers¶
behavior · persona operator
As an operator, I want the executor to learn from the registry, and from nowhere else, whether a tool is served by an MCP server, so that no tool call reaches an MCP server that the registry does not hold as registered and bound.
ToolAdapterService resolves a tool whose descriptor is of kind Mcp before it executes it: the internal gRPC method McpServerRegistryService/McpRegistry.ResolveTool turns a tool id and version into the server, the transport, the binding and the authentication the executor needs. The caller presents a workload token. Such a token carries service scopes and no tenant claim, so the service reads the tenant the caller forwards only when the token holds the service scope that names McpServerRegistryService (ADR-0015 amendment D114). The forwarded tenant travels in the gRPC metadata of the call, and the tenant row filter of both methods runs on it and on nothing in the request body. A workload call that forwards no tenant is refused with UNAUTHENTICATED by the Factory profile before any handler runs, as the profile answers 401 for it over REST. The request message names toolId and toolVersion. The lookup runs in McpToolBindings under the tenant row filter for a binding that is bound to that tool version and whose server is Active, and the reply message carries serverId, transport, endpointRef or commandRef, authentication, governancePolicyRef, protocolVersion, toolName, schemaHash and declaredClass. It never carries a credential: the registry stores no secret, and the executor obtains the credential of a consumed server through its connection and the Secret Broker (ADR-0022 decision 6). The method is of class read and writes nothing. In the thin delivery no server and no binding exists, so every resolution on a deployed instance is answered NOT_FOUND. That is the answer of the same contract for a tool without a bound, Active server, and it is also the answer for a binding of another tenant, which is never confirmed to exist. The executor calls the method only for a descriptor of kind Mcp, and none is active in this increment, so the fifteen native tools of the chain are never resolved here; what ToolAdapterService does with a NOT_FOUND is stated in its own feature. How an unbound binding and a Degraded server are answered belongs to the complete delivery, which owns discovery and the handshake probe. The second method, McpServerRegistryService/McpRegistry.ListCapabilities, returns the tools, resources and prompts visible to a scope, for the clients that connect to the MCP endpoint the Factory exposes. In I1 that endpoint serves only calls bound to a run, a step and an attempt; IDE clients and partner agents, for whom the model names this method, arrive with the complete McpServerRegistryService in I5 (D121). Its request is execution-scope-v1, the scope of the client whose list is built; the reply lists each capability with its binding under the tenant row filter of the forwarded tenant, an unbound tool listed as not invocable. The tenant in the request body never selects rows: an execution-scope-v1 whose tenantId differs from the forwarded tenant is refused with PERMISSION_DENIED and the reason scope-mismatch, and nothing is listed. In the thin delivery the reply is an empty, well-formed list for every scope, so the exposed endpoint lists no tool in this increment. Both methods refuse a call without a workload identity, and a workload call that forwards no tenant, with UNAUTHENTICATED, and a token without the service scope with PERMISSION_DENIED. INVALID_ARGUMENT is the answer for a request without a tool id and never for a missing or a differing tenant. When mcp-server-registry-sql is unavailable the call fails with UNAVAILABLE and no partial reply; the dependency is fail-fast for ToolAdapterService, which then executes no tool of kind Mcp. The found replies are proven with fixture rows inserted directly into the isolated test database, because no operation of the thin delivery writes them. The open point of the request and reply descriptors is the one AIFACTORY-US-064 records, and the two messages stay provisional until the owner names them.
Acceptance criteria
| AC1 | Given a fixture binding inserted directly into the isolated test database, a tool version bound to an Active McpServerRegistryService/McpServer of tenant A, when McpServerRegistryService/McpRegistry.ResolveTool is called with toolId and toolVersion under a workload token that holds the service scope and forwards tenant A, then the reply message carries serverId, transport, endpointRef, authentication, governancePolicyRef, protocolVersion, toolName, schemaHash and declaredClass, no credential value, and nothing is written (SCN-McpServerRegistryService-007, ADR-0022). |
| AC2 | Given the deployed thin service with its empty store, when McpServerRegistryService/McpRegistry.ResolveTool is called for each of the fifteen tool ids the chain names, then every call is answered NOT_FOUND; given the fixture binding of tenant A, when the call forwards tenant B, then the answer is NOT_FOUND exactly as for an unknown tool id and never confirms the binding (SCN-McpServerRegistryService-007, ADR-0015). |
| AC3 | Given a caller without a workload identity, a workload call that forwards no tenant in the gRPC metadata, a workload token without the service scope, a request of McpServerRegistryService/McpRegistry.ResolveTool without a tool id, or an unavailable mcp-server-registry-sql, when McpServerRegistryService/McpRegistry.ResolveTool or McpServerRegistryService/McpRegistry.ListCapabilities is called, then the call is refused with UNAUTHENTICATED, UNAUTHENTICATED, PERMISSION_DENIED, INVALID_ARGUMENT or UNAVAILABLE respectively, the two UNAUTHENTICATED answers come from the Factory profile before any handler runs, INVALID_ARGUMENT is never the answer for a missing tenant, no partial reply is returned and no state changes (SCN-McpServerRegistryService-007, SCN-McpServerRegistryService-008, ADR-0015, model/backlog/pbis/component-extensions/component-base-template-factory-profile.yaml). |
| AC4 | Given a workload token that holds the service scope and forwards tenant A on the deployed thin service, when McpServerRegistryService/McpRegistry.ListCapabilities is called with an execution-scope-v1 of tenant A, then the reply is an empty list of tools, resources and prompts; given fixture bindings of tenant A, when the call forwards tenant A, then they are listed with their binding and an unbound tool is marked as not invocable; when the call forwards tenant B with a scope of tenant B, then nothing of tenant A is listed; when the call forwards tenant B with an execution-scope-v1 that names tenant A, then it is refused with PERMISSION_DENIED and the reason scope-mismatch and nothing is listed; nothing is written in any case (SCN-McpServerRegistryService-008, ADR-0015). |
| Traces: services | McpServerRegistryService |
| Traces: aggregates | McpServerRegistryService/McpServer |
| Traces: apis | McpServerRegistryService/McpRegistry.ResolveTool, McpServerRegistryService/McpRegistry.ListCapabilities |
| Traces: descriptors | tool-invocation-v1, execution-scope-v1 |
| Traces: adrs | ADR-0015, ADR-0022 |
| Traces: requirements | FR-05, NFR-02 |
| Traces: scenarios | SCN-McpServerRegistryService-007, SCN-McpServerRegistryService-008 |
| Depends on | AIFACTORY-US-596, feature:component-base-template-factory-profile |
| Sources | model/services/tools-mcp/McpServerRegistryService.yaml, model/services/tools-mcp/ToolAdapterService.yaml, model/backlog/pbis/component-extensions/component-base-template-factory-profile.yaml, docs/reference/schemas/tool-invocation.schema.json, docs/planes/capability-tools/mcp.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-2403 McpRegistry.ResolveTool over the bindings with workload scope checks and the tenant row filter |
implementation | McpRegistry.ResolveTool takes the request message of AIFACTORY-TASK-075 (toolId and toolVersion), looks the bound binding of an Active server up under the tenant the caller forwards in the gRPC metadata and returns the reply message with serverId, transport, endpointRef or commandRef, authentication, governancePolicyRef, protocolVersion, toolName, schemaHash and declaredClass and no credential value; the tenant row filter runs on the forwarded tenant, which is read only under the service scope; a call that forwards no tenant is refused with UNAUTHENTICATED by the Factory profile before the handler; a token without the service scope is answered PERMISSION_DENIED; INVALID_ARGUMENT answers a missing tool id only; NOT_FOUND answers a tool without a bound binding of an Active server and a binding of another tenant alike (ADR-0015); an unavailable store is answered UNAVAILABLE; nothing is written. | ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |
AIFACTORY-TASK-2404 McpRegistry.ListCapabilities over the bindings of a scope |
implementation | McpRegistry.ListCapabilities takes an execution scope and returns the tools, resources and prompts of the tenant the caller forwards in the gRPC metadata with their bindings, an unbound tool marked as not invocable, and an empty well-formed list when the tenant has none; the tenant of the request body never selects rows, and an execution scope whose tenant differs from the forwarded tenant is refused with PERMISSION_DENIED and the reason scope-mismatch without listing anything; a call that forwards no tenant is refused with UNAUTHENTICATED by the Factory profile; the method applies the same workload scope checks as ResolveTool and writes nothing. | ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |
AIFACTORY-TASK-2405 Two-tenant fixture rows and workload tokens of the acceptance suite |
fixture | The acceptance suite holds a fixture that inserts one Active server of tenant A with a bound tool binding, an unbound tool binding, a resource binding and a prompt binding directly into the isolated test database, workload tokens with and without the service scope, a workload call that forwards no tenant, a request whose execution scope names another tenant than the forwarded one, a call without identity, and a switch that stops the store; the fixture is the only writer of the tables, because the thin delivery has no write path (model/services/tools-mcp/McpServerRegistryService.yaml). | ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |
AIFACTORY-TASK-2406 Verify the two registry methods through the acceptance suite |
verification | Run dotnet test -c Release --filter "Category=Acceptance&(Scenario=SCN-McpServerRegistryService-007\|Scenario=SCN-McpServerRegistryService-008)"; a zero-match filter counts as a failure; the tests prove AC1 to AC4 of AIFACTORY-US-597: the found reply on the fixture binding, NOT_FOUND for the fifteen tool ids of the chain on an empty store and for a binding of another tenant, the five refusals with UNAUTHENTICATED for a call that forwards no tenant, the empty and the fixture capability lists, and PERMISSION_DENIED with the reason scope-mismatch for an execution scope of another tenant than the forwarded one. |
ConnectSoft.AI.SoftwareFactory.McpServerRegistryService |