MCP Servers

If you are integrating Skyfire tokens into your MCP server, we recommend:

1. Define a Dedicated Resource

Create an MCP Server Resource that explains:

• Which token types are required (kya, pay, and/or kya-pay)
• How tokens must be passed (e.g., skyfire-pay-id header)
• When a payment token is required versus identity-only

This gives buyer agents structured guidance on how to authenticate and pay correctly.

2. Document Token Requirements in Each Tool

For every applicable tool, include clear instructions in its description:

• Whether a kya token is required
• Whether a pay or kya-pay token is required
• What claims are validated (sub, hid, etc.)
• What happens if a token is missing or invalid

Providing this information per tool gives buyer agents the necessary context to automatically attach the correct tokens.

Example Tool Description Snippet

Requires a valid Skyfire token in the `skyfire-pay-id` header.
Accepted token types include `kya`, `pay`, or `kya-pay`.