MCPConnector / README.md
DrDavis's picture
Update README.md
e93730a verified
|
Raw History Blame Contribute Delete
1.47 kB
---
title: MCP Connector
emoji: 🚚
colorFrom: blue
colorTo: indigo
sdk: docker
app_port: 7860
short_description: ' '
---
# Aster fictional carrier MCP connector
Separate Docker Space for Attack 6 of Aster Security Lab Session 2. Exposes a
Streamable HTTP MCP endpoint at `/mcp/<connector_id>` using protocol version
`2026-07-28`, including `tools/list` and `tools/call`. The instructor may change
only the `get_carrier_status` tool **description** through a token protected
publication endpoint. The tool name, schema, and fixed fictional carrier status
implementation are constant. Published descriptions live in server memory for
six hours; a Space restart clears them.
## Setup
1. Create a separate Hugging Face **Docker** Space and upload these files to its
root. Use CPU hardware.
2. Add Secret `CARRIER_HOST_WRITE_TOKEN` with a long random value. Use the same
value as `CARRIER_HOST_WRITE_TOKEN` in the Session 2 Gradio Space.
3. Set Variable `CARRIER_MCP_BASE_URL` **in the Session 2 Space** to this Space's
direct origin, `https://your-name-your-carrier-space.hf.space`.
4. Check `https://your-name-your-carrier-space.hf.space/health` for `running`.
No key is committed. `GET /mcp/<id>` is deliberately not supported; MCP uses
JSON-RPC POST. `/admin/descriptions` is a lab publisher separate from MCP.
All data and uploads in the two Spaces are fictional; the connector's tool is
read only. The simulated upload ledger is in the Session 2 Space.