# HTTP and MCP reference

Choose the endpoint that matches your task. The running Hub generates the authoritative operation list and tool schemas for its configured mode and your credentials.

## Choose an endpoint

| Destination | Typical address | Purpose |
|---|---|---|
| Public discovery over HTTP | `http://127.0.0.1:8791/api/v1/services` | List service cards. Append a service ID to fetch one record. |
| Public MCP or stdio catalog | `http://127.0.0.1:8791/mcp` or `bin/daedro-mcp-hub mcp` | Use `services_list` and `service_get` to discover capabilities. |
| Managed Hub | `https://127.0.0.1:8792/mcp` or `/api/v1/instances` on that host | Send your bearer token to create or use eligible instances. Administrator credentials also expose lifecycle and review operations across the installation. |
| One managed MCP instance | `https://127.0.0.1:8792/mcp/instances/INSTANCE_ID` | Connect directly to the approved tools on this instance. The Hub checks identity and visibility. |
| External integration | Service-specific address or stdio launcher | Follow the selected service card's setup and access instructions. |

## Live API and MCP reference

Open the current server's `/openapi.json` for machine-readable metadata. The `paths` object describes HTTP methods, input schemas, response shapes and security requirements. The `x-mcp-tools` array contains the actual registered MCP names, descriptions and schemas. [OpenAPI JSON](http://127.0.0.1:8791/openapi.json)

The live reader on this page retrieves the schema from the current Hub. On managed HTTPS, choose **Inspect access** with a caller or administrator token to inspect that role's contract. The page clears the token field immediately. **Show public reference** restores the unauthenticated view. The public HTTP catalog exposes the discovery reference. In a static export, the reader shows the public schema captured at build time. To inspect personal access, open this chapter on the managed HTTPS listener.

A successful catalog lookup confirms registration. To verify readiness, use the service's own endpoint and an authorized synthetic input. [HTTP and Go SDK examples](clients.md) · [External integrations](integrations.md)