MCP Servers
Where to document Skyfire token requirements in an MCP server: a dedicated resource, and per-tool descriptions.
If you're integrating Skyfire tokens into your MCP server, document token requirements in two places.
Create an MCP Server Resource that explains which token types are required (kya, pay, and/or kya-pay), how tokens must be passed (the kyapay-token header), and when a payment token is required versus identity only. This gives buyer agents structured guidance on how to authenticate and pay correctly.
For every applicable tool, include clear instructions: whether a kya token is required, whether a pay or kya-pay token is required, what claims are validated (sub, hid, etc.), and what happens if a token is missing or invalid. This gives buyer agents the context to automatically attach the correct tokens.
Example tool description
Requires a valid Skyfire token in the `kyapay-token` header.
Accepted token types include `kya`, `pay`, or `kya-pay`.Older integrations may reference the
skyfire-pay-idheader instead ofkyapay-token. It is deprecated and being replaced.
Updated 4 days ago