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

ucp-check

v0.1.0

Published

Is this domain verified for the Universal Commerce Protocol? A CLI and CI gate over the UCP Checker API.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

pactmodepactmode

Keywords

ucpuniversal-commerce-protocolagentic-commerceagent-readinessvalidatorcicliucpchecker

Readme

ucp-check

Is this domain verified for the Universal Commerce Protocol? One command, from your terminal or CI.

npx ucp-check example.com
  example.com  verified · UCP 2026-08-25
  manifest   https://example.com/.well-known/ucp
  observed   2026-09-13T10:00:00+00:00 (live)
  report     https://ucpchecker.com/status/example.com

ucp-check is a thin client over the UCP Checker REST API. No account, no API key, no dependencies, Node 18+. It renders the verdict the API returns and turns it into an exit code. It never inspects the manifest itself and never scores anything locally, so what you see here is exactly what ucpchecker.com/status/example.com shows.

Usage

ucp-check <domain> [options]

  --cached            Read the last observed state instead of running a live check
  --json              Print the API response as JSON, exactly as served
  --quiet             No output; exit code only
  --base-url <url>    API origin (default https://ucpchecker.com, or UCP_CHECK_BASE_URL)
  --timeout <s>       Seconds to wait for the API (default 60)

A live check fetches the domain's /.well-known/ucp from the UCP Checker crawler, validates it against the current spec, and records the observation. --cached skips the crawl and returns the last observed state, which is what you want on every push when the manifest has not changed.

Exit codes

Exit codes are the contract; everything else is display.

| Code | Meaning | |---|---| | 0 | verified | | 1 | not verified: not_detected, invalid, blocked, unreachable or pending | | 2 | usage error: bad flags, malformed domain | | 3 | API unreachable, timed out, or rate limit exhausted |

CI gate

- name: UCP manifest verifies
  run: npx ucp-check your-store.com --quiet

The job fails when the live manifest does not verify. The API allows 30 live checks a minute and 200 a day per IP; cached reads are 60 a minute and 1,000 a day. A pipeline that checks on every push stays inside that by using --cached on pushes and a live check on deploy.

Rate limits and the observed flag

A store's edge can rate-limit the crawler. When that happens the API still answers 200 with the last observed state and observed: false; the CLI says so and the exit code reflects that last state. Retry after the number of seconds it prints.

What it does not do

It does not validate a manifest from disk, run a local server, or compute a score. Those live on the server so that a check from CI, from the website and from an agent's MCP call all say the same thing. For the score, methodology and the machine-readable versions of both, see the API docs.

Related

License

MIT