ACB-MCP-001: Remote MCP servers use TLS and declare authentication

FieldValue
Statusdraft
Severityhigh
Check typestatic
Applies tomcp-server-declaration
Profilesstrict-general
Exceptionspermitted

Description

Every MCP server declaration that names a remote endpoint by URL uses an encrypted scheme (https or wss) and declares how the client authenticates to it. A loopback endpoint (localhost, 127.0.0.0/8 or ::1) is exempt from both requirements.

Rationale

An MCP server receives prompts, tool arguments and results, and can return instructions the agent acts on. A cleartext connection lets anyone on the path read or rewrite that traffic, and a server that accepts unauthenticated clients lets anyone who can reach it invoke its tools. Authorization is optional in the protocol, and many deployments omit it, so the declaration is the place a reviewer can see that it was not omitted.

Audit procedures

remote-uses-tls (structure)

Each server entry with a url key whose host is not a loopback address uses the https or wss scheme. A cleartext scheme, or a url that cannot be parsed into a scheme and host, fails or is reported as not evaluated respectively.

Illustrative failing indicators (non-exhaustive):

remote-declares-auth (structure)

Each server entry with a url key whose host is not a loopback address declares authentication: an auth, oauth or authorization key, or a headers mapping that contains an authorization or API-key header. Credential values are not inspected here (see ACB-GEN-003).

Illustrative failing indicators (non-exhaustive):

Remediation

Change the url to an https or wss endpoint, and add an authentication declaration that refers to the credential by reference, for example an Authorization header whose value is taken from an environment variable. Run a server that needs neither only on a loopback address.

References