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

foxd-contract

v0.3.1

Published

The typed tool contract behind the FoxD trading API — one declaration generating the REST API, MCP server, TypeScript SDK and CLI for multi-chain memecoin trading.

Readme

foxd-contract — the tool schema behind the FoxD trading API

One typed declaration of every capability in FoxD — the multi-chain memecoin trading platform covering Solana, Ethereum, BNB Chain, Base, Arbitrum and HyperEVM — shared by the REST API, the MCP server, the SDK and the CLI.

Most people want foxd-sdk (typed client), foxd-cli (terminal) or foxd-mcp (Claude/Cursor/Codex). Install this directly only if you are generating your own client or need the zod schemas and JSON Schema for the 87 tools.

npm i foxd-contract

You rarely need this package directly — install foxd-sdk to make calls. Reach for it when you are building your own surface over FoxD: a router, a UI over the tool list, your own agent framework binding, or type-checking a payload before you send it.

import { TOOLS, getTool, matchRest, moduleSummary } from "foxd-contract";

getTool("market.trending")?.scopes;        // ["read"]
matchRest("GET", "/tokens/base/0x532f…");  // { tool, params }
TOOLS.filter((t) => t.mutates);            // everything that changes state

Each tool declares its name, description, module, required scopes, weighted cost, zod input and output schemas, REST binding and worked examples. The REST routes, the OpenAPI 3.1 document, the MCP tool list, the SDK methods and their types, and the CLI subcommands are all derived from it, so nothing about a tool is written twice and no surface can drift from another.

Schemas are zod v4, so z.toJSONSchema() gives you draft-2020-12 directly — which is what OpenAPI 3.1 and MCP inputSchema both want, with no converter in between.

import { z } from "zod";
import { getTool } from "foxd-contract";

const tool = getTool("trade.quote")!;
const parsed = tool.input.safeParse(userSupplied);   // validate before sending
const schema = z.toJSONSchema(tool.input, { io: "input" });

Also exported: the scope list and what each grants, the tier and quota tables, the cost-unit constants, and coerceArgs — the schema-directed query-string coercion the gateway uses, so a hosted copy behaves identically.

Links

MIT