npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@straitlink/mcp

v0.6.0

Published

Strait MCP server: create, search, pause and resume deep links, QR codes, analytics comparisons and top links, recent taps and events, custom domains, webhooks, App Links / Universal Links checks and the docs, from AI tools. Stdio command and a library fo

Readme

@straitlink/mcp (preview)

claude mcp add strait --env STRAIT_SECRET_KEY=st_live_your_key -- npx -y @straitlink/mcp

Use Strait from AI tools such as Claude Code, Cursor and Claude Desktop: create, find, pause and resume deep links, get their QR codes, read and compare analytics, see recent taps and conversion events, manage custom link domains, look after webhooks (list, deliveries, test, redeliver), check App Links / Universal Links files or any vendor's link, see where taps on a link go and search the Strait docs.

It is a local stdio server with 32 tools. Eleven of them write (create_link, batch_create_links, update_link, pause_link, resume_link, deactivate_link, record_event, add_domain, remove_domain, test_webhook, redeliver_webhook_delivery); the other twenty-one only read. check_app_links, check_link, search_docs and demo trace_tap work without a key; every other tool needs your secret key. Other deep-link vendors also ship MCP servers that can create links, so this README makes no "first" or "only" claim; it describes what this server does today.

iPhone is in beta. iPhone install matching (deferred deep linking on iOS) is in beta; Android uses the Play Install Referrer. On iPhone the workspace chooses the method in Dashboard → Settings → iPhone installs (device matching, paste handoff, both or neither), and the SDK reads that choice at runtime. Device matching is off for new workspaces. The tools report iPhone results the same way, but treat iPhone install attribution as beta.

Hosted server. The same tools are served at https://strait.link/mcp (Streamable HTTP, since 24 Oct 2026): claude mcp add --transport http strait https://strait.link/mcp --header "Authorization: Bearer st_live_your_key". It takes a secret key in the Authorization header (60 requests burst, then 1 a second, per key); OAuth sign-in is not there yet. The engine serves it with this package's createStraitServer() (library entry, 0.3.0).

Tools

A read-only secret key (Dashboard → Settings → Secret keys, access "Read only") is offered only the tools that read (0.5.1; the hosted server already did this). Full and links-only keys see every tool; the API still refuses anything outside the key's access.

| Tool | What it does | Key needed | |---|---|---| | create_link | Create one link and get its shortUrl | secret | | batch_create_links | Create up to 500 links in one call (safe to re-run: existing slugs are per-item 409s) | secret | | get_link | Read one link by slug | secret | | list_links | List links, one page at a time. status: "paused" lists turned-off links (0.2.1) | secret | | update_link | Change destination, title, tags or expiry, or isActive on its own (false pauses, true turns a paused link back on; 0.2.1). Asks for confirm: true: without it you get a preview and nothing changes | secret | | get_analytics | Taps, app opens, installs, conversions and revenue, by day / channel / link / platform (GET /v1/analytics). iPhone installs come from beta install matching | secret | | check_app_links | Check a domain's assetlinks.json and apple-app-site-association, with a fix for each problem | none | | simulate_tap | Dry-run one tap from one device or app (nothing recorded or billed) | secret | | trace_tap | Walk a link through WhatsApp, Instagram, Facebook, Chrome, Safari, iPad, computer and preview bots; or read a Live Tap Trace from the website demo | secret (link) / none (demo token) | | get_workspace | Who the key is: workspace, link domain, custom domains, plan, the key's access (full / links / read) and the saved QR styles (qrStyles, 0.6.0) (GET /v1/workspace; 0.5.0, needs engine with that route) | secret | | get_usage | This month's taps and new links against the plan, level (ok / warn / over) and new_links_paused (GET /v1/usage) | secret | | get_referrals | Referral report: taps and referred installs per code (GET /v1/referrals, a preview: says "not switched on yet" until it is) | secret | | list_webhook_deliveries | A webhook's deliveries (status, attempts, last HTTP status, next retry; no payloads). Without webhookId: the workspace's webhooks (id, receiver site, events) | secret | | test_webhook | Send one ping to a webhook now and see the receiver's status and time (not stored, not retried) | secret | | redeliver_webhook_delivery | Send a failed delivery again (same X-Strait-Delivery id). Asks for confirm: true | secret | | deactivate_link | Turn a link off: taps then get the "link not found" page. Asks for confirm: true; turn it back on with update_link isActive: true | secret | | pause_link | Pause a link (taps get the "link not found" page until it is resumed). Asks for confirm: true (0.3.0) | secret | | resume_link | Turn a paused link back on. Asks for confirm: true (0.3.0) | secret | | search_links | Find links by text in slug, title, destination, campaign or tags, or by exact tag or campaign; active, inactive or all (0.3.0) | secret (owner/admin) | | get_link_qr | A link's QR code as a PNG image or SVG, in the workspace's QR style or a saved style (preset, 0.6.0) (0.3.0) | secret | | get_campaign_qr_zip | Every live link of a campaign as QR codes in one ZIP (SVG, or PNG up to 1024 px), handed back as an embedded file; 3 a minute per workspace (GET /v1/qr.zip; 0.6.0) | secret | | compare_analytics | Two periods side by side (default: the one just before), totals and per channel / platform / link, with % change (0.3.0) | secret | | get_top_links | Top links by taps, app opens, installs or conversions, with each one's share (0.3.0) | secret | | list_taps | Recent taps, newest first, with where each was sent and the open/install it led to (default: last hour) (0.3.0) | secret (owner/admin) | | list_events | Recent conversion and revenue events, newest first (default: last 7 days) (0.3.0) | secret (owner/admin) | | record_event | Record a server-side conversion (POST /v1/event). Asks for confirm: true (0.3.0) | secret | | list_domains | Custom link domains with status and the DNS records to add (0.3.0) | secret | | add_domain | Add a custom link domain and get its DNS records (Scale and Enterprise). Asks for confirm: true (0.3.0) | secret | | remove_domain | Remove a custom link domain. Asks for confirm: true (0.3.0) | secret | | list_webhooks | The workspace's webhooks: id, receiver site (host only), events, on/off (0.3.0) | secret | | check_link | Check any vendor's deep link (Firebase page.link, Branch, Strait): where it goes and what to fix (0.3.0) | none | | search_docs | Search the Strait docs offline (bundled index) | none |

Every tool carries MCP annotations (readOnlyHint, destructiveHint, …) and the descriptions of the 0.2 and 0.3 tools start with "Read-only." or "Write.". update_link, pause_link, deactivate_link and remove_domain are destructive. Every write except create_link, batch_create_links and test_webhook shows a preview first and acts only with confirm: true. create_link and batch_create_links write new links but never change existing ones. There is no delete tool: a deactivated link keeps its history.

Prompts

Clients that show MCP prompts (Claude Code: type /) offer five starters. All but migrate_firebase_links only read:

| Prompt | What it does | |---|---| | weekly_review | This week against last week (totals and channels), the top links by installs, and anything down more than 30 % | | debug_link (slug) | Why a link opens the browser: App Links / Universal Links files, a trace per channel and its recent taps, with the fix | | setup_check | Usage, custom domains still waiting for DNS, webhooks with failed deliveries, and the App Links files | | migrate_firebase_links (old_domain, optional) | Maps your Firebase Dynamic Links (long links, export rows or short links checked with check_link) to Strait fields, shows the plan, and runs batch_create_links only after you answer yes. Re-running is safe: existing slugs come back as a per-item 409 | | why_not_open (slug; platform android / iphone and app browser / whatsapp / instagram / facebook, optional) | Why a link opened the store, browser or nothing: the link, the App Links / Universal Links files, the tap on that phone and app, its recent taps, and a pasted SDK doctor() report read by finding id (key.secret, host.file_missing, app.missing, cert.missing…) |

Keys

The server needs a secret key (st_live_…) from Dashboard → Settings → Secret keys. A secret key can change your links, so:

  • Create a separate key for your AI tools, so you can revoke it on its own.
  • Keep it in the MCP client's config or environment, never in app or website code.
  • A publishable key (st_pub_live_…) does not work here: it is for the SDKs in your apps.
  • The server sends the key only as an Authorization: Bearer header to STRAIT_API_URL, never logs it, and replaces anything shaped like a secret key in tool output or errors with st_…[redacted].

Without a key, check_app_links, search_docs and demo trace_tap still work.

| Variable | Meaning | |---|---| | STRAIT_SECRET_KEY | Your secret key (st_live_…) | | STRAIT_API_URL | Engine URL. Default https://strait.link. Use http://localhost:3000 for a local engine |

Install

Claude Code plugin (hosted server + setup skill)

/plugin install strait --marketplace strait-link/strait-mcp

(On older Claude Code: /plugin marketplace add strait-link/strait-mcp, then /plugin install strait@strait-link.) It asks for a secret key when you enable it and keeps it in your system's credential store. It connects to the hosted server https://strait.link/mcp and adds the strait-setup skill, which sets Strait up in an app. Privacy: https://straitlink.in/legal/privacy/

Claude Code

claude mcp add strait --env STRAIT_SECRET_KEY=st_live_your_key -- npx -y @straitlink/mcp

Cursor

~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project; don't commit a key):

{
  "mcpServers": {
    "strait": {
      "command": "npx",
      "args": ["-y", "@straitlink/mcp"],
      "env": { "STRAIT_SECRET_KEY": "st_live_your_key" }
    }
  }
}

Claude Desktop

Settings → Developer → Edit config, then add the same "strait" entry under mcpServers and restart.

From a checkout

cd mcp-server && npm ci && npm run build
claude mcp add strait --env STRAIT_SECRET_KEY=st_live_your_key -- node "$PWD/dist/stdio.js"

In Cursor or Claude Desktop use "command": "node", "args": ["/absolute/path/to/mcp-server/dist/stdio.js"].

Try it

  • "Create a Strait link summer to https://shop.hilltop.example/summer with the title Summer sale."
  • "Which channel brought the most installs last month?"
  • "My links open the browser instead of the app. Check hilltop.strait.link and shop.hilltop.example."
  • "What happens when someone taps summer inside Instagram on an iPhone?"
  • "How do I receive links in Expo Router?"
  • "How much of this month's plan have we used?"
  • "My webhook stopped firing. Show me its last deliveries, send it a test, and resend the failed ones."
  • "Turn off the spring-sale link." (you'll see a preview first)
  • "Which referral codes brought the most installs in October?"
  • "How did this week do against last week, by channel?"
  • "Which links point at /summer? Pause the old ones."
  • "Did my test tap on summer just now get recorded, and did it open the app?"
  • "Give me a QR code for summer in dark grey."
  • "Is links.hilltop.example set up yet? Which DNS records are missing?"
  • "Check https://hilltop.page.link/abc before we migrate it."

Hilltop Shoes (hilltop.strait.link, *.hilltop.example) is a made-up shop used in examples.

MCP registry listing (drafted, not published)

server.json and the mcpName field in package.json are drafts for the official MCP registry. The registry checks that mcpName in the published npm package matches server.json name (package types).

  • Namespace in.straitlink/mcp (recommended). Reverse-DNS of straitlink.in, so the listing carries the product's own domain. It needs DNS authentication: the Strait team adds a TXT record on the apex straitlink.in (v=MCPv1; k=ed25519; p=<public key>) and runs mcp-publisher login dns --domain straitlink.in --private-key … (authentication). Keep the private key out of the repo.
  • Alternative io.github.<owner>/strait-mcp. Uses GitHub OAuth (mcp-publisher login github) and needs no DNS change, but the name shows a personal GitHub account rather than the product domain, and it requires the public GitHub repo (strait-link/strait-mcp). To switch, change name in server.json and mcpName in package.json together (a test checks they match).
  • remotes lists the hosted server https://strait.link/mcp (Streamable HTTP, Authorization: Bearer secret key, live since 24 Oct 2026), and repository points at github.com/strait-link/strait-mcp. The OAuth Worker (mcp.strait.link) is not listed until it is deployed.
  • Order when the Strait team is ready: create the repo, publish @straitlink/mcp to npm (done: 0.1.0 on 15 Oct, mcpName matches), add the TXT record, then run the MCP registry workflow (.github/workflows/registry.yml). Without the MCP_DNS_PRIVATE_KEY secret it only validates server.json (schema, name, version, npm) and stops.

Founder steps (about 10 minutes, after the GitHub repo exists)

  1. Claude makes a key pair on the Mac (openssl genpkey -algorithm ed25519) and shows you only the public part.
  2. In the DNS settings for straitlink.in, add a TXT record on the root (@) with the value v=MCPv1; k=ed25519; p=<public key>. Save. It can take up to an hour to appear.
  3. In GitHub, repo strait-mcp → Settings → Secrets → Actions, add MCP_DNS_PRIVATE_KEY with the private key (Claude puts it there if you allow secret writes).
  4. Actions → MCP registry → Run workflow. When it's green, search "Strait" on registry.modelcontextprotocol.io: that's how you know it worked.

Licence

MIT. See LICENSE.

OAuth remote server (built, not deployed)

The hosted server above (strait.link/mcp) needs a key in a header. This Worker is the later, OAuth version.

src/worker.ts is a Cloudflare Worker serving MCP over Streamable HTTP at https://mcp.strait.link/mcp. It answers 404 everywhere unless REMOTE_MCP=on (only env.production in wrangler.jsonc turns it on).

  • Bearer-key mode: Authorization: Bearer st_live_… on /mcp, for clients that take a header.
  • OAuth (@cloudflare/workers-oauth-provider): dynamic client registration (/register), /authorize, /token, authorization-server metadata and RFC 9728 protected-resource metadata (/.well-known/oauth-protected-resource/mcp). PKCE, registered redirect URIs only.
    • The consent page asks for a secret key, checks it with GET /v1/links?limit=1, and keeps it only inside the grant, which the provider encrypts with the token (a test checks that KV never holds the key in plain text). It shows where the user is sent back to, has a Cancel button (access_denied back to the client), and sends X-Frame-Options: DENY, a strict CSP and Cache-Control: no-store.
    • Access tokens last 1 hour; refresh tokens 30 days.
    • Next step before a wide launch: replace the paste-a-key page with dashboard sign-in that mints a scoped key.
  • /healthz returns { ok, service, version, mcp } with no upstream call, for the post-deploy check.

Try it locally

cp .dev.vars.example .dev.vars        # REMOTE_MCP=on, STRAIT_API_URL=http://localhost:3000
npm run dev:remote                    # wrangler dev on http://localhost:8787 (local KV, nothing leaves the machine)
curl http://localhost:8787/healthz
npx -y @modelcontextprotocol/[email protected]   # connect to http://localhost:8787/mcp

Deploy the remote server (Strait team only)

Agents prepare this; only the Strait team deploys. Needs the Cloudflare account that holds the strait.link zone (CLOUDFLARE_API_TOKEN / CLOUDFLARE_ACCOUNT_ID from redirect-engine/.env work). The bundle is about 1.9 MB (360 KB gzipped), inside the free plan's size limit; Workers Paid (already planned) is recommended for its higher CPU time per request.

cd mcp-server && npm ci
npm run typecheck && npx vitest run            # all green
# 1. Create the OAuth store once and paste its id into env.production.kv_namespaces in wrangler.jsonc
npx -y wrangler@4 kv namespace create OAUTH_KV --env production
npm run deploy:preflight                       # exit 0 = config ready (fails while the id is a placeholder)
npm run deploy:check                           # wrangler dry run, nothing uploaded
# 2. Deploy. The custom domain creates the mcp.strait.link DNS record and certificate.
npx -y wrangler@4 deploy --env production
# 3. Check it
curl -s https://mcp.strait.link/healthz                                     # {"ok":true,...}
curl -s https://mcp.strait.link/.well-known/oauth-protected-resource/mcp    # resource: https://mcp.strait.link/mcp
curl -s -o /dev/null -w '%{http_code}\n' -X POST https://mcp.strait.link/mcp  # 401 (needs a token)
claude mcp add --transport http strait https://mcp.strait.link/mcp          # then /mcp in Claude Code to sign in

Roll back with npx -y wrangler@4 rollback --env production, or switch it off by setting REMOTE_MCP to "off" in env.production.vars and deploying again (every route then answers 404). Revoking the secret key a user pasted cuts that connection off at the API.

Claude Code skill

skills/strait-setup/SKILL.md teaches Claude Code how to add Strait to an app (React Native / Expo, Flutter, Android, iOS, Unity, Capacitor, web, and a Node server). Copy the folder into ~/.claude/skills/ or a project's .claude/skills/, or download it from https://straitlink.in/ai/strait-setup/SKILL.md.

The site repo owns it (site/lib/skill.mjs, fed by site.config.json, so install lines and versions match the docs). Don't edit this copy by hand: run npm run skill:sync (needs ../site or SITE_DIR). The site's tests fail when this copy drifts.

Develop

npm ci
npm run typecheck     # Node, tests and the Worker
npm test              # unit, protocol, Worker and an end-to-end test against a local engine
npm run build
npm run inspect       # MCP Inspector CLI: lists the tools
npm run docs-index    # rebuild src/docs-index.json from ../site/content/docs
npm run skill:sync    # regenerate skills/strait-setup/SKILL.md from ../site
npm run deploy:check  # wrangler dry run of the production Worker (nothing uploaded)

The end-to-end test (test/integration.test.ts) starts the real engine from ../redirect-engine (or ENGINE_DIR) with its in-memory store, runs this server over stdio as a child process, creates a link and reads it back. It is skipped when no engine checkout with installed dependencies is next to this repo.

Docs and support