@chaindaddy/mcp 0.6.11 → 0.6.12

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 +3 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@chaindaddy/mcp",
3
- "version": "0.6.11",
3
+ "version": "0.6.12",
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
@@ -27,7 +27,7 @@ Use discovery: `https://api.chaindaddy.io/.well-known/openid-configuration`
27
27
 
28
28
  Any site can sign people in without registering anything.
29
29
 
30
- Replace `YOUR_SITE` with the site's host, such as `example.com`. Nothing is registered with Chain Daddy. The site must be public, on https: Chain Daddy's server fetches `client.json`, so `localhost` cannot be your own client id. To build on `http://localhost` first with nothing hosted, use the built-in development client: skip `client.json`, set the button's `client-id` to `chaindaddy-dev` and its `redirect-uri` to `http://localhost:3000/callback.html`, and set the server's `audience` to `'chaindaddy-dev'`. It asks every time, its `sub` matches no real site's, and it answers nothing about holdings or crowns, so put your own values back before you ship. To try your real `client.json` or a coin gate before the site is live, use a tunnel such as `cloudflared tunnel --url http://localhost:3000`, which needs no account, or a preview deployment.
30
+ Replace `YOUR_SITE` with the site's host, such as `example.com`. Nothing is registered with Chain Daddy. **Start on `http://localhost` with nothing hosted**, using the built-in development client: skip `client.json` (step 1), set the button's `client-id` to `chaindaddy-dev` and its `redirect-uri` to `http://localhost:3000/callback.html`, and set the server's `audience` to `'chaindaddy-dev'`. `GET https://api.chaindaddy.io/api/v2/oauth/snippet?origin=http://localhost:3000` (the `get_sign_in_snippet` tool) returns those three pieces filled in. The development client asks every time, its `sub` matches no real site's, and it answers nothing about holdings or crowns, so a holders-only route refuses everyone there; put your own values back before you ship. The live site must be public, on https: Chain Daddy's server fetches `client.json`, so `localhost` cannot be your own client id. To try your real `client.json` or a coin gate before the site is live, use a tunnel such as `cloudflared tunnel --url http://localhost:3000`, which needs no account, or a preview deployment.
31
31
 
32
32
  1. Host this at `https://YOUR_SITE/client.json` (served 200, no redirect; `client_id` must equal its own URL):
33
33
 
@@ -185,8 +185,8 @@ The token address is `tokenAddress` in `GET https://api.chaindaddy.io/api/v2/pub
185
185
 
186
186
  ## 1b. Or register a client (the human does this)
187
187
 
188
- Only needed for a **server client with a secret**, the consent screen's **Verified** mark for a coin's own
189
- site, or `http://localhost` redirects during development. Needs Developer Beta Program membership (any paid
188
+ Only needed for a **server client with a secret** or the consent screen's **Verified** mark for a coin's own
189
+ site. Trying sign-in on `http://localhost` needs no registration (the development client above). Needs Developer Beta Program membership (any paid
190
190
  plan and the signed agreement; a client costs nothing more). Easiest: the developer portal,
191
191
  https://chaindaddy.io/_developer → **Sign-in** → **New client**. Or:
192
192