# Private MEOK MCP service and the public research lab

**Guide reviewed 11 November 2026.** The public static lab is not an MCP server. Its inference runs in the visitor's browser. The existing private MEOK application exposes its own MCP tools at:

```
https://nicholastempleman-meok-hf-runtime.hf.space/gradio_api/mcp/
```

Use an authorised Hugging Face credential through the MCP client's protected secret facility. Do not paste it into the public lab, a report, an issue or a downloaded receipt. Installing the Hugging Face discovery plugin does not automatically install this private custom server into every AI client.

## Dated acceptance, not a timeless capability claim

`evidence/live-mcp.json` is the original v0.2 acceptance record: it found ten advertised tools and exercised the process predictor and compact-root tool. Later receiver acceptance discovered twenty tools and checked the categorical receiver. Those counts describe their exact historical source revisions, not the current server's discovery response. Read the [receiver acceptance](integration-specialist-review/presentation-v1/mcp-after.json) and its [scope](integration-specialist-review/presentation-v1/CONSOLIDATION.md).

The 11 November pass keeps the private application unchanged. Its initial source/serving readback was `4bcd42b2e9dcb579e973e59219c6548c5d1fec44`; this includes later work by the existing runtime owner. Availability and metadata observations do not certify untested conversations, saved-copy storage, model quality or every tool.

## Different tools, different meanings

`meok_hf_runtime_predict_process` executes the small synthetic continuous-state predictor. The categorical artifact receiver checks compatible labelled prediction records; it must not relabel those continuous vectors as categorical evidence. The compact-root tool produces an index of supplied records, not durable storage of every referenced original.

Receiver events remain PARTIAL/null/unsigned and non-authorising. Account-authenticated transport does not prove that caller-supplied pins or source context are authentic. Human identity, trusted current source state and approval-to-effect require separate checks.

## Publication and privacy

Public browser receipts are unsigned and remain in the browser unless exported. An exported checksum is not a digital signature or an inference proof. This public-quality pass does not read or publish private conversation or bucket contents, change storage configuration, or start provider inference.