Hi - I am working on Agent Service Manifest (ASM), an optional value-metadata layer for MCP servers.
I am not asking you to change runtime behaviour. The small integration would be one publisher-provided metadata block under MCP Registry server.json _meta:
_meta.io.modelcontextprotocol.registry/publisher-provided.asm
Browserbase MCP seems like a strong fit because browser automation has real pre-call operational constraints: hosted/session pricing, quotas, rate limits, side effects, and approval/risk boundaries for actions like navigation, extraction, and page interaction.
The ASM block could expose metadata such as:
- pricing/free-tier assumptions or a link to canonical pricing
- quota/rate-limit envelope for hosted sessions
- operational risk class and side effects (
external_api_call, browser_session, network_access)
- approval boundaries for high-risk actions
- provenance for the claims
Example shape:
https://github.com/calebguo007/asm-spec/blob/main/examples/mcp-server-json/operational-envelope-with-asm.server.json
Producer guide:
https://github.com/calebguo007/asm-spec/blob/main/docs/adoption/producer-guide.md
Would you be open to reviewing a minimal PR adding optional ASM metadata to server.json? It would not affect MCP invocation, and MCP clients that do not understand ASM would ignore it.
Hi - I am working on Agent Service Manifest (ASM), an optional value-metadata layer for MCP servers.
I am not asking you to change runtime behaviour. The small integration would be one publisher-provided metadata block under MCP Registry
server.json_meta:_meta.io.modelcontextprotocol.registry/publisher-provided.asmBrowserbase MCP seems like a strong fit because browser automation has real pre-call operational constraints: hosted/session pricing, quotas, rate limits, side effects, and approval/risk boundaries for actions like navigation, extraction, and page interaction.
The ASM block could expose metadata such as:
external_api_call,browser_session,network_access)Example shape:
https://github.com/calebguo007/asm-spec/blob/main/examples/mcp-server-json/operational-envelope-with-asm.server.json
Producer guide:
https://github.com/calebguo007/asm-spec/blob/main/docs/adoption/producer-guide.md
Would you be open to reviewing a minimal PR adding optional ASM metadata to
server.json? It would not affect MCP invocation, and MCP clients that do not understand ASM would ignore it.