Scope and prerequisites
Prepare a reachable public HTTPS MCP endpoint, authorized account, and controlled acceptance tool. The endpoint excludes userinfo, query, and fragment; supply credentials separately. authentication accepts none, bearer, or header. Header mode uses header_name, defaulting to x-api-key. Explicitly select none for public services rather than inventing a Token. This interface does not expose stdio, local process launch, resources/prompts subscriptions, sampling, or elicitation. It does not automatically register arbitrary OAuth clients or refresh Tokens. OAuth-only services need an externally obtained suitable Bearer Token and manual renewal. MCP support does not imply every extension.Discover, select, and enable
Prepare a tool returning known content in a controlled service and set MCP_TOOL_NAME to its exact name. These examples retain approval=true. Review discovered names, descriptions, and schemas before saving selection. External descriptions are data, not instructions to expand access. The examples use local management clients with private configuration; see self-hosting for hosted initialization. Each execution creates a connection; save/reuse its ID.Invoke from a Session
Follow Tools, binding connection.id astools: {research: connection_id} with a Tools-capable Harness, then preflight. Required Tools are checked for authorization during initialization; optional Tools still require authorization when used.
Submit a precise task reading a dedicated test object through the selected tool and reporting its known content. With approval=true, inspect the pending approval and follow approval handling. Confirm rejection produces no actual remote call. Read-only annotations do not disable approval automatically; an administrator explicitly reviews that policy.
Inspect Tool call records and actual content, not only the final natural-language answer. Handle changed/expired credentials through authorization. Original Tokens remain in the control plane, not Sandbox environment.
Interpret results and changes
An MCP call can return a valid result withisError: true. Hexagon records the call as completed because a result was obtained; inspect is_error in Tool call records and the actual result instead of equating completed with business success. A valid Tool error differs from a lost response after dispatch, where the remote outcome may remain unknown.
Keep the selected tool definition as a reviewed snapshot. Adding a new remote tool does not authorize an existing Session to call it. A name, description or schema change to a selected tool requires rediscovery and review; do not bypass drift detection by editing a local hash key to resemble the old tool. Approval policy and remote read-only annotations are distinct: annotations are not permission to remove human consent.
Network and retry boundaries
Socket-time DNS checks reject private/mixed addresses. Redirects and cross-origin SSE POST targets are rejected. Fake-IP DNS may fail validation; do not disable checks for convenience. Operators can configure the existing trusted egress proxy/exact-host mechanism described in networking. Definitions are checked before invocation. One connection retry is allowed before tools/call begins; after dispatch, a lost response is never automatically replayed, including read-only-annotated tools. All MCP operations have replay=never. A remote write may complete before its response disappears. Retain the original call/hash, verify remotely, and record the conclusion through reconciliation. Cancellation does not undo writes. Rediscovery does not resolve unknown side effects; do not issue a new call to test whether the old one succeeded.A concrete discovery-to-call example
The historical public-service example useshttps://mcp.deepwiki.com/mcp, authentication: none, Streamable HTTP, and the selected remote name read_wiki_structure. The requested repository was modelcontextprotocol/typescript-sdk. For a public service, omit the credential rather than using the bearer example unchanged; keep the discovered key when selecting the tool. Your administrator must review the discovered schema and approval policy before enabling it.
The November 18 record used one TypeScript Session with Vercel/Pi 1.5.2 and one Python Session with Vercel/OpenCode 1.2.27, both with the configured SiliconFlow international DeepSeek-V4-Flash model. It checked an actual completed call and returned documentation topics, then confirmed cleanup. The operator explicitly disabled approval for that selected read; this does not prove the approval-rejection branch or a remote write. It also does not establish today’s service availability.
The dependency is
@modelcontextprotocol/sdk 1.32.2 in this repository. A fixture’s selected protocol version must not be copied into the public service’s evidence. An SDK version and a negotiated protocol version are different fields.