Would a small publisher-provided access manifest fit Firecrawl's server.json?

[YE-YI7]

I maintain Agent Service Manifest (ASM), an optional pre-call selection metadata layer. Firecrawl's documented keyless-versus-authenticated tool boundary looks like a useful concrete case: it can live under MCP Registry's publisher-provided _meta without changing MCP runtime or auth behavior.

I would keep the block sparse: documented tool/access boundaries and provenance only. Mutable plan limits or prices would stay behind source links rather than be frozen as scalar claims.

Would you be open to reviewing a minimal PR against the existing server.json? It would add only publisher-declared ASM metadata and a validation fixture; no runtime code or authentication flow would change.

Reference shape: https://github.com/YE-YI7/asm-spec/blob/main/docs/adoption/producer-guide.md