Rail SCC Knowledge Service

A Model Context Protocol (MCP) server providing structured access to the Rail Safety Critical Communications regulatory knowledge model. This service is provider-neutral — it returns structured data only; reasoning is the client’s responsibility.

MCP Tools

Resources

Documents

Assertions

Decision Nodes

Getting Access

API key required. To connect to this service you need an API key issued by the service administrator. Each user or team receives their own key for usage tracking and access control. Contact the administrator to request a key.

Connect

Claude Desktop (Web Connector)

Settings → Connectors → Create, enter https://scc-mcp.rcnx.io/mcp. OAuth 2.1 discovery is automatic. You will be prompted to authenticate on first use.

Claude Desktop (config file)

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "rail-scc": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://scc-mcp.rcnx.io/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

ChatGPT

Settings → Connectors → Create, enter https://scc-mcp.rcnx.io/mcp. OAuth 2.1 discovery is automatic. No API key needed — authentication is handled via OAuth.

OpenAI Responses API

tools=[{
    "type": "mcp",
    "server_url": "https://scc-mcp.rcnx.io/mcp",
    "server_label": "rail-scc",
    "authorization_token": "YOUR_API_KEY"
}]

MCP Endpoint

POST /mcp — Streamable HTTP transport (requires Authorization: Bearer header or OAuth 2.1 token)

Tools — Read (10)

Tool	Description	Scope
`search_players`	Search SCC ecosystem players by name or role	scc:read
`get_player`	Get detailed info about a specific player	scc:read
`search_documents`	Search document registry by ref, title, or function	scc:read
`get_document`	Get details for a specific document reference	scc:read
`search_assertions`	Search knowledge assertions by topic or classification	scc:read
`get_decision_path`	Get decision/escalation path for a topic	scc:read
`assemble_question_context`	Assemble full structured context for a question (no reasoning)	scc:read
`list_active_documents`	List all currently active SCC documents	scc:read
`list_superseded_documents`	List all superseded SCC documents	scc:read
`explain_relationship`	Explain the relationship between two entities	scc:read

Tools — Admin (6)

Admin tools require scc:admin scope. When Entra SSO is enabled, admin access requires Microsoft Entra ID authentication.

Tool	Description	Scope
`propose_knowledge_update`	Propose an update to the knowledge model (validated against guardrails)	scc:admin
`review_pending_updates`	Review all pending knowledge update proposals	scc:admin
`approve_update`	Approve a pending knowledge update proposal	scc:admin
`reject_update`	Reject a pending knowledge update proposal	scc:admin
`apply_knowledge_update`	Apply an approved knowledge update to the live model	scc:admin
`rebuild_compiled_knowledge`	Reload knowledge from canonical JSON files	scc:admin

Admin Workflow

Knowledge updates follow a governed lifecycle: propose → review → approve/reject → apply. All mutations are audit-logged with actor, timestamp, and evidence basis.

Proposals are validated against policy guardrails before acceptance:

5-tier canonical artefact precedence (SCC > NR standards > RAIB > RSSB > other)
Evidence classification enforcement (fact requires Tier 1/2 sources)
Payload validation against Pydantic entity models
Precedence conflict detection against existing knowledge

Resources

URI	Description
`scc://overview`	Service overview and capabilities
`scc://players`	SCC ecosystem players registry
`scc://documents`	Document registry (active and superseded)
`scc://decision-path`	Decision and escalation path graph
`scc://assertions`	Knowledge assertions with evidence classification
`scc://open-questions`	Identified knowledge gaps
`scc://sources/{ref}`	Detail for a specific source document

Authentication

OAuth 2.1

Endpoint	Purpose
`/.well-known/oauth-authorization-server`	Authorization server metadata
`/.well-known/oauth-protected-resource/mcp`	Protected resource metadata
`/register`	Dynamic client registration (RFC 7591)
`/authorize`	Authorization endpoint (PKCE required)
`/token`	Token endpoint
`/revoke`	Token revocation

Static Bearer Token

Each user or team is issued an API key by the service administrator. Pass it via Authorization: Bearer YOUR_API_KEY header. This works alongside OAuth 2.1. All tool calls are logged per key for usage monitoring.

Microsoft Entra ID SSO

Admin scope (scc:admin) can be delegated to Microsoft Entra ID for single sign-on. When enabled, admin authorization redirects to your organisation’s Entra login page. Group membership restrictions are supported.

Ops

Endpoint	Purpose
`GET /health`	Health check
`GET /ready`	Readiness check

Rail SCC Knowledge Service v0.1.0 — provider-neutral, no reasoning, no LLM coupling. Every tool response declares reasoning_provider: "none".