@chaindaddy/mcp 0.6.4 → 0.6.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/sign-in-with-chain-daddy/SKILL.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@chaindaddy/mcp",
3
- "version": "0.6.4",
3
+ "version": "0.6.5",
4
4
  "description": "MCP server for Chain Daddy: search tickers, launch a token or verify ownership of one, and run its creator store",
5
5
  "mcpName": "io.chaindaddy/mcp",
6
6
  "homepage": "https://docs.chaindaddy.io/developer/store-and-rewards#tools-for-agents",
package/skills/sign-in-with-chain-daddy/SKILL.md CHANGED
@@ -93,7 +93,7 @@ export async function verifyChainDaddy(idToken: string) {
93
93
  }
94
94
  ```
95
95
 
96
- To require a coin, add `claims='{"id_token":{"holdings":{"tokens":[{"chain":"base","address":"0xTOKEN","min":"100"}]}}}'` to the button. That request passes through the visitor's browser, which can change the coin or the minimum, and the ID token answers whatever was asked. So the server never reads `payload.holdings[0].held`: it matches each answer against its own constants first.
96
+ To require a coin, add `"chaindaddy_claims": {"id_token":{"holdings":{"tokens":[{"chain":"base","address":"0xTOKEN","min":"100"}]}}}` to `client.json`. Chain Daddy then answers that request and no other, and refuses a sign-in that asks for anything else; the button needs no `claims`. The server still never reads `payload.holdings[0].held`: it matches each answer against its own constants first.
97
97
 
98
98
  ```ts
99
99
  // What this site gates on, as the ID token writes it: token lowercase for an EVM address, min "0" if none was asked.