Access the website through ANP MCP and PAP
The website's service example exposes the same protocol documents and text-message
submission through three protocols. Deploy the TypeScript service alongside the
static website using the instructions in server/README.md in this repository.
| Protocol | Discovery or connection | Client authentication |
|---|---|---|
| ANP | /.well-known/agent-descriptions | DID HTTP request signatures |
| MCP | /mcp | CIMD machine OAuth |
| PAP 0.3 | /.well-known/poppy.json | Signed-out PAP Session |
After discovery, follow the advertised document and interface URLs. The ANP
description requires a signature from the client's DID; the service does not
require its own DID. DSH clients use the open-source
dsh-anp plugin with their
existing local shared identity.
The operations are protocol_list, protocol_get and message_create. Specify
the version, document ID and language when reading a protocol. For example,protocol_get with version: "1.1", document: "white-paper" and language: "en"
returns the English ANP 1.1 Markdown. Missing documents return an error instead of
substituting the latest version. Messages contain one message string and return
the stored ID and creation time.
MCP scopes are protocol.read and message.write. PAP uses no browser or account
login for these operations. Each protocol uses the same stored content and message
service, implemented by service-agent.