networking-components MCP server

This repository inherits from the hardened Rust MCP fleet libraries at ORESoftware/mcp-rust-libs. The exact networking-components/networking-components-mcp-server.rs organization, repository, service, Zed package, and dependency identities are compile-time constants in src/spec.rs; the server cannot silently drift into a generic fleet wrapper.

The same final MCP 2025-11-25 surface works with Cursor, ChatGPT/OpenAI, Claude/Anthropic, Gemini, Grok, and Qwen. It is deliberately read-only and exposes 15 no-argument tools:

• org_identity — canonical organization, repository, package, version, and access mode;
• zed_dependency_graph — Zed-owned dependency intent and .vendor/.zed materialization policy;
• telemetry_status — non-sensitive ores-otel traces, metrics, logs, and structured-stderr initialization status;
• shared_auth_policy — the fail-closed identity/realm boundary and whether a public Shared Auth authority is configured, without accepting credentials;
• environment_policy — SOPS+age ciphertext and ignored-plaintext rules;
• security_baseline — mutation, output-bound, logging, auth, dependency, and secret-handling guarantees;
• github_posture — the exact networking-components repository and CI posture;
• aws_posture — the configured AWS account and bounded EKS inventory;
• gcp_posture — exact GCP project metadata and enabled services;
• supabase_posture — the configured networking-components Supabase health boundary;
• neon_posture — exact Neon organization/project and branch metadata;
• cloudflare_posture — the configured networking-components zone and DNS posture;
• k8s_posture — the exact networking-components namespace in the ORESoftware/k8s-cluster deployment plane;
• nats_posture — the networking-components service and dependency subjects; and
• organization_posture — one bounded, concurrent view of all eight providers.

Three generated resources describe the service catalog, provider catalog, and security policy. Three generated prompts guide deployment readiness, provider triage, and dependency-impact analysis without granting arbitrary execution. Every provider result has one of five honest states: ready, degraded, unauthorized, forbidden, or not_configured. Missing credentials or scope never becomes synthetic success.

ORESoftware/mcp-rust-libs is pinned to immutable revision f470ca5be6389bb20c2291acdfc3a382cb9b39b2. The server's honest MSRV is Rust 1.95.0, matching the provider-complete AWS SDK graph. Its organization-server crate pins ores-otel/ores-mcp-server-core-libs.rs to reviewed revision e559a76f869c2c2d9bf939b510d358a3924abd81 for JSON logs on stderr plus OTLP traces, metrics, and logs. MCP protocol frames own stdout.

Run

Enter the pinned Nix shell and run with a SOPS-encrypted environment profile:

nix develop
just run dev

Only env/enc/*.env.enc ciphertext is committed. just decrypt dev writes a mode-0600 ignored file to env/dec/dev.env; just encrypt dev updates the ciphertext. Private age identities never belong in this repository.

SHARED_AUTH_BASE_URL is optional for this public policy-only baseline. A local stdio process accepts no bearer token. The networking-components-mcp-http binary serves the same catalog at /mcp over Streamable HTTP and fails before binding unless ORE_MCP_PUBLIC_RESOURCE, SHARED_AUTH_ISSUER, and SHARED_AUTH_JWKS_URL are exact. It validates ES256/JWKS locally, pins the public resource as audience, requires the networking-components project realm, AAL2, mcp:read plus networking-components:inspect, and a networking-components_viewer or networking-components_operator role. It never forwards a caller token upstream. Exact client IDs, origins, and the loopback-default bind can be set with ORE_MCP_OAUTH_CLIENT_IDS, ORE_MCP_ALLOWED_ORIGINS, and ORE_MCP_HTTP_BIND.

Provider credent

... View full README on GitHub