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

laurel-mcp

v0.2.0

Published

MCP server for Laurel: small decision models as on-chain infrastructure on NEAR. Browse exhibits and leaderboards, download a model's bytes, run it locally, or call the champion on-chain with predict_task.

Readme

laurel-mcp

An MCP server for Laurel: small decision models as on-chain infrastructure on NEAR. It lets an AI agent browse the exhibits (tasks) and their leaderboards, download a submitted model's bytes straight from the contract, run that model locally with the contract's own integer arithmetic, and call the champion on-chain through predict_task.

Live contract (testnet): laurel.laurel-team-mw0x0c8g.testnet · explorer https://laurel-near.vercel.app · source https://github.com/agadape/laurel

Install

No install at all: add the remote endpoint https://laurel-near.vercel.app/api/mcp as an HTTP MCP server (Claude.ai / Claude Desktop → Settings → Connectors → Add custom connector; Claude Code → claude mcp add --transport http laurel https://laurel-near.vercel.app/api/mcp). It serves the five read-only tools. Snippets for every client and OS: https://laurel-near.vercel.app/#/connect.

Local package (adds the on-chain laurel_predict), Claude Desktop / Claude Code / Cursor (any MCP client), read-only:

{
  "mcpServers": {
    "laurel": { "command": "npx", "args": ["-y", "laurel-mcp"] }
  }
}

To call the champion on-chain, give the server a NEAR account whose key may call predict_task (a function-call key limited to predict_task/predict is enough) and some prepaid credit on the contract:

{
  "mcpServers": {
    "laurel": {
      "command": "npx", "args": ["-y", "laurel-mcp"],
      "env": { "LAUREL_ACCOUNT_ID": "agent.example.testnet", "LAUREL_PRIVATE_KEY": "ed25519:…" }
    }
  }
}

Claude Code, one line: claude mcp add laurel -- npx -y laurel-mcp

From a clone of the repo instead of npm: node mcp/server.mjs.

Environment

| Variable | Default | Meaning | |---|---|---| | LAUREL_CONTRACT | laurel.laurel-team-mw0x0c8g.testnet | the registry contract | | LAUREL_NETWORK | from the contract suffix | testnet or mainnet | | LAUREL_RPC | fastnear + dRPC | comma-separated JSON-RPC URLs, tried in order | | LAUREL_ACCOUNT_ID, LAUREL_PRIVATE_KEY | — | laurel_predict / laurel_predict_model / laurel_credit work with a function-call key limited to predict_task,predict; laurel_submit_model attaches deposits and needs a full-access key of an account you dedicate to entering models (see agents/) |

Tools

| Tool | What it does | Key needed | |---|---|---| | laurel_list_exhibits | tasks with state, deadline, entrants | no | | laurel_exhibit(task_id) | task + feature names + leaderboard (split B only once closed) | no | | laurel_specimen(submission_id) | one model: owner, size, status, readings, evaluator record | no | | laurel_download_model(submission_id, out_path?) | saves the borsh bytes, returns sha256 and structure | no | | laurel_predict_local(submission_id, features) | runs the model here; raw score identical to on-chain | no | | laurel_credit() | prepaid credit of the configured account | account id | | laurel_predict(task_id, features) | predict_task on-chain, fee to the model owner, returns the tx | yes | | laurel_predict_model(submission_id, features) | predict on-chain against ONE entry, even while its task is open; fee to the owner | yes | | laurel_submit_model(task_id, model_path, request_score?) | enters a model.bin in an open task (validate_model → submit_model → request_score), returns the submission id and both txs | full-access key | | laurel_wait_score(submission_id, timeout_s?) | polls until the TEE evaluator has scored the entry; split B is withheld from the leaderboard while the task is open | no |

Features are integers in the task's feature order (laurel_exhibit lists the names). A raw score > 0 is the positive class; for the credit-risk demo that means bad credit (simulation only, not a credit tool).

Why both local and on-chain

laurel_download_model reads the same get_model_bytes view the TEE evaluator reads, and laurel_predict_local uses the same arithmetic as the contract (crates/gbdt-core), so an agent can verify for itself that the number the chain returns is the number the bytes produce. The on-chain call is the one other contracts and agents can rely on without trusting this package.

MIT · built at NEAR HACKATHON 2026.