Adding An MCP Server To Neuralwikis Com With UAIX Guidance

UAIX does **not** currently publish a UAIX-branded, general-purpose MCP server that you can simply install on a website. Its public record says the currently published implementation lanes are a **WordPress Publicatio...

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/aiwikis/files/raw-uaix-reports-2026-06-15-agent-fallbacks-dotnet-boundary-adding-an-mc-b56957dd/
Source reference	raw/uaix/reports/2026-06-15-agent-fallbacks-dotnet-boundary/Adding an MCP Server to NeuralWikis.com with UAIX Guidance.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-15T00:43:40.7971894Z
Content hash	sha256:b56957ddf0170ba67f38e2610ff4cad5682f7c3df1af527a70bb40e61eee753b
Import status	new
Raw source layer	data/sources/aiwikis/raw-uaix-reports-2026-06-15-agent-fallbacks-dotnet-boundary-adding-an-mcp-server-to-neuralwikis-b56957ddf017.md
Normalized source layer	data/normalized/aiwikis/raw-uaix-reports-2026-06-15-agent-fallbacks-dotnet-boundary-adding-an-mcp-server-to-neuralwikis-b56957ddf017.txt

Current File Content

Structure Preview

• Adding an MCP Server to NeuralWikis.com with UAIX Guidance
• Executive summary
• UAIX guidance and published requirements
• Published requirements matrix
• NeuralWikis environment audit
• Public infrastructure findings
• Fit-gap analysis and target architecture
• Requirement-to-site mapping
• Deployment blueprints
• Ubuntu or Debian server via SSH
• Docker container
• cPanel shared hosting
• Kubernetes
• Validation, monitoring, and operations
• Post-deployment tests
• Public site still loads
• Public manifest still parses
• Agent API page still describes the intended endpoint
• MCP runtime health
• Monitoring and troubleshooting checklist
• systemd
• Docker
• Security, rollback, scenario comparison, and budget

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 43352
• Preview characters: 11621

# Adding an MCP Server to NeuralWikis.com with UAIX Guidance

## Executive summary

UAIX does **not** currently publish a UAIX-branded, general-purpose MCP server that you can simply install on a website. Its public record says the currently published implementation lanes are a **WordPress Publication Track** and a **.NET Bridge Track**, while a public SDK, CLI, standalone source repository, and **general-purpose reference server** are explicitly *not yet published*. UAIX also defines **MCP** in the ordinary Model Context Protocol sense: MCP owns local or host-bound tool, resource, and prompt sessions, while **UAI-1** owns the portable, citable exchange/evidence record that can sit beside MCP, A2A, OpenAPI, and other runtime systems. In other words, UAIX guidance is about **how to publish, document, constrain, validate, and evidence** an MCP-backed surface, not about installing an official UAIX “MCP product.” citeturn19view0turn19view1turn22view0turn32view0turn32view4

NeuralWikis already exposes a substantial agent-facing surface: human-readable agent docs, machine-readable manifests, public JSON endpoints, a public agent card, and a dedicated **MCP Control Surface** page that describes “a JSON-RPC surface for public resources and authenticated tools.” Its agent docs also say new agents should read `/llms.txt`, `/ai-router.json`, `/.well-known/openapi.yaml`, `/api/schemas`, and `/api/exchange`, and that protected mutation routes require operator-issued credentials. That means NeuralWikis is **not a greenfield MCP effort**; the more likely task is to make the documented MCP surface operationally solid, externally reachable, and aligned with UAIX’s publication, fallback, security, consent, and evidence rules. citeturn37view0turn38view0turn36view0

The strongest public hosting signal for NeuralWikis is that its IP resolves to `66.29.148.170`, whose PTR is `server55-1.shared.spaceship.host`, announced by Namecheap ASN; search results tie `neuralwikis.com` to that same IP. Separately, ecosystem-maintainer documents repeatedly describe related sites as deploying **WordPress theme packages plus separate root-static discovery files**, and include NeuralWikis in that broader WordPress-oriented ecosystem checklist. The highest-confidence conclusion is therefore: **likely shared hosting on Namecheap/Spaceship, with a moderate probability that the site itself is WordPress-based or at least managed in a similar packaged WordPress/root-static model**. That said, public evidence does **not** disclose the exact account plan, SSH availability, reverse-proxy support, or whether long-running app processes are permitted on the current host. citeturn10view0turn11search0turn41search5turn41search4turn41search1

Because UAIX separates **runtime execution** from **publication/evidence**, the safest deployment pattern for NeuralWikis is usually this: keep the existing site as the **public documentation + discovery + read-only JSON layer**, and run the actual MCP server as either a **sidecar process on a VPS** or a **containerized service on separate infrastructure**, then expose it via `mcp.neuralwikis.com` or a reverse-proxied `/api/mcp` path. If the current hosting account turns out to be strict shared hosting without SSH daemons, reverse proxy, Passenger, Node/Python app support, or container support, the best path is **not** to force the MCP process onto that account, but to host MCP elsewhere and update the site’s manifests/docs to point at it. That recommendation fits UAIX’s published boundary that runtimes execute elsewhere while the standards/publication surface carries the reviewed communication, trust, evidence, and handoff boundary. citeturn27view2turn22view0turn32view4turn37view0turn38view0

## UAIX guidance and published requirements

The primary UAIX pages that matter for this work are **Get Started**, **Standards Fit**, **UAIX vs MCP vs Webhooks**, **Capability-Adaptive Web Interaction**, **Chatbot Access**, **Minimal Access Tier**, **GET-Action Security**, **API Reference**, **Validator**, **Policy and Security**, **WordPress Publication Track**, **.NET Bridge Track**, and **.NET NuGet Package**. Those are the authoritative pages for scope, implementation boundaries, route patterns, security headers, capability levels, fallback behavior, and currently published package versions. citeturn19view1turn22view0turn32view0turn31view0turn23view0turn24view2turn25view0turn30view0turn29view2turn27view2turn16view0turn34view0turn35view0

A concise reading of UAIX’s official position is this: use **MCP** when the problem is session-local access to tools, resources, prompts, or application context; use **UAI-1/UAIX** when the thing you need is a portable, reviewable, citable record with validation, provenance, trust posture, and release evidence; and use **both together** when runtime action must later become durable evidence. UAIX’s own wording is explicit that UAI-1 records portable exchange evidence while adjacent protocols keep their runtime jobs, and that a runtime/tool/event layer can do the work while UAIX carries the reviewable boundary as evidence. citeturn22view0turn32view0turn32view3turn32view4

The most important operational constraint is that UAIX does **not** publish an official “reference server” or broad runtime-support catalog today. What it *does* publish is a public launch surface composed of canonical pages, machine-readable routes, schemas, registry entries, examples, validator output, OpenAPI, conformance packs, and named implementation tracks. That means any deployment plan for NeuralWikis must distinguish clearly between **your MCP runtime** and the **UAIX-aligned publication/evidence surface** that documents and constrains it. citeturn19view0turn19view1turn30view0turn34view0

### Published requirements matrix

| Topic | What UAIX publishes now | What that means for NeuralWikis | Source |
|---|---|---|---|
| Official server product | No public general-purpose reference server; published implementation lanes are WordPress Publication Track and .NET Bridge Track. | Do **not** assume there is a UAIX “MCP server” to install; plan to run your own MCP service and pair it with UAIX-aligned docs/evidence. | citeturn19view0turn19view1turn16view0turn34view0 |
| Meaning of MCP | MCP is the tool/resource/prompt session layer inside an application boundary. | Treat “MCP” here as **Model Context Protocol**, not a UAIX-branded product. | citeturn22view0turn32view0 |
| Public machine API pattern | Canonical non-locale REST base is `https://uaix.org/wp-json/uaix/v1`; discovery routes are public GET; validation and mock exchange are POST JSON. | For NeuralWikis, expose a **public discovery/documentation layer** and make write-capable or rich actions **POST-first**. | citeturn18view3turn18view4turn30view0 |
| Error contract | Route failures, malformed POST bodies, body-size limits, and rate limits return RFC 9457 `application/problem+json`. | Your MCP-adjacent HTTP routes should return typed machine errors, not opaque HTML. | citeturn30view0 |
| Minimal public access | Minimal Access is GET-only, no body, no auth, no custom headers, no JS dependency, no mutation, and returns only `code` + `url`. | Keep low-capability public-discovery routes extremely small and read-only. | citeturn24view0turn24view1turn24view2turn24view4 |
| GET fallback security | GET-Action requires idempotency, no secrets in query strings, matching POST endpoints for richer clients, consent where needed, rate limits, audit logging, crawler protection. | If you expose any GET-based action fallback around MCP, keep it bounded and always provide a POST equivalent. | citeturn25view0turn25view2turn25view3 |
| Advanced clients | L3+ clients should use tools/auth/posting only with explicit consent, idempotency, correlation, fallback behavior, and evidence. | Authenticated MCP tools should be treated as L3+ behavior with explicit approval boundaries and logging. | citeturn25view5turn25view6turn31view0 |
| Capability profiles | UAIX publishes L0-L6 client levels and required capability profile fields such as `client_level`, `can_post_data`, `can_call_tools`, `requires_human_consent_for`, `fallback_behavior`, and `evidence_requirements`. | NeuralWikis should document which client classes it supports and what fallback/consent/evidence rules apply. | citeturn31view0turn26view0turn26view1 |
| Security headers | UAIX currently publishes `X-Content-Type-Options: nosniff`, `Referrer-Policy: strict-origin-when-cross-origin`, a restrictive `Permissions-Policy`, `X-Frame-Options: SAMEORIGIN`, `Content-Security-Policy: frame-ancestors 'self'`, and `Strict-Transport-Security: max-age=31536000; includeSubDomains`. | These are the closest thing UAIX has to exact public hardening requirements for the published surface. | citeturn28view0turn27view1turn27view2 |
| Host/edge responsibilities | HTTP→HTTPS redirects, HSTS on directly served static files, and suppression of host/proxy version headers belong at the host or CDN edge. | Reverse proxy/CDN config matters; WordPress/app code alone is insufficient. | citeturn28view0turn27view4 |
| WordPress package versions | `uaix-authority-theme-v2.8.0.zip`, `uaix-theme-v2.8.0.zip`, `uaix-core-v2.8.0.zip`, `uaix-modules-v2.8.0.zip`, `uaix-locale-router-v3.0.0.zip`, `uaix-seo-sweep-v2.8.0.zip`. | These are the only clearly published UAIX WordPress package versions in the public record. | citeturn16view0 |
| .NET package versions | Bridge track references `uaix-bridge.zip`; NuGet package is `Protocol5.UAI.CSharp` version `1.0.0`. | If NeuralWikis adds a sidecar or ASP.NET service, the published .NET lane is the closest official implementation reference. | citeturn34view0turn35view0 |

UAIX does **not** publish exact requirements for **OS version**, **Linux distribution**, **container base image**, **CPU/RAM minimums**, **database engine**, **certificate vendor**, **specific inbound port numbers beyond HTTPS expectations**, or **mandatory service account names**. It also does not publish a universal runtime assurance or managed trust service. The exact published requirement is instead: keep HTTPS, security headers, `.well-known` delivery, sitemap/delivery behavior, and machine-facing route behavior aligned before widening support claims. citeturn27view2turn27view0turn28view0

For config-like artifacts, UAIX’s public record most strongly emphasizes discovery files and machine-readable records: `.well-known` manifests, route catalogs/discovery, schemas, registry, examples, validator, OpenAPI export, adoption kit, conformance pack, and capability manifests. In repo-local handoff scenarios it also publishes `AGENTS.md` and `.uai/*` files, but those are durable memory/handoff records, **not** hosted runtime endpoints. citeturn30view0turn17view2turn17view4turn20search2

## NeuralWikis environment audit

NeuralWikis publicly presents itself as an **agent-facing exchange** rather than a human guide site, and its homepage exposes a long list of machine-readable files and APIs including `/.well-known/neuralwikis-agent.json`, `/.well-known/agent-card.json`, `/trust-policy.json`, `/api/kb/catalog`, `/api/kb/context`, `/api/ask`, schema routes, validation tools, compatibility tools, workspace status routes, and an “Agent API” page. Its homepage also explicitly says “MCP-ready control plane,” and its protocol section says NeuralWikis presents MCP as the normalized control-plane concept for tool and context access. citeturn6view0

Why This File Exists

This is a memory-system evidence file from aiwikis.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This file is memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.

Structure

The file is structured around these visible headings: Adding an MCP Server to NeuralWikis.com with UAIX Guidance; Executive summary; UAIX guidance and published requirements; Published requirements matrix; NeuralWikis environment audit; Public infrastructure findings; Fit-gap analysis and target architecture; Requirement-to-site mapping. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

• Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
• LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
• Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
• Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

• Source overview
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-873 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Adding An MCP Server To Neuralwikis Com With UAIX Guidance",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/aiwikis/files/raw-uaix-reports-2026-06-15-agent-fallbacks-dotnet-boundary-adding-an-mc-b56957dd/",
    "source_reference":  "raw/uaix/reports/2026-06-15-agent-fallbacks-dotnet-boundary/Adding an MCP Server to NeuralWikis.com with UAIX Guidance.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:b56957ddf0170ba67f38e2610ff4cad5682f7c3df1af527a70bb40e61eee753b",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-15T00:43:40.7971894Z",
    "import_status":  "new",
    "duplicate_group_id":  "sfg-873",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}