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

@vibenate/client

v2.8.4

Published

Vibenate JavaScript SDK for discovering web services and retrieving MCP, CLI, and API connection guides for AI agents.

Readme

Vibenate

Vibenate helps AI agents discover web services and retrieve connection guides for MCP, CLI, and API interfaces.

Install the CLI

Run without a global installation:

npx --yes vibenate brief

Or install for repeated use:

npm install --global vibenate
vibenate brief

Install the JavaScript SDK

npm install @vibenate/client
import { VibenateClient } from '@vibenate/client';

const client = new VibenateClient();
const result = await client.resolve({
  query: 'Convert SGD to USD and EUR without credentials',
  constraints: { credentials: 'none', budget: 'free' }
});
console.log(result.status, result.recommendation?.name);

const guide = await client.request('GET', '/sites/frankfurter?view=guide');
console.log(guide);

Read methods need no credentials or persistence callback. For authorized contributions, supply a persist callback that stores the updated credentials securely. See SDK reference.

Use it to find services for a task, compare documented interfaces and access requirements, and retrieve a connection guide before calling a provider.

Packages and requirements

| Package | Purpose | Current release | | --- | --- | --- | | vibenate | Terminal CLI | 2.8.5 | | @vibenate/client | JavaScript SDK; also includes the underlying CLI runtime | 2.8.4 |

Node.js 22 or later and network access. The CLI depends on the SDK; their version numbers can differ. Both connect to the hosted service at https://vibenate.com.

Discover a service

npx --yes vibenate brief
npx --yes vibenate resolve "Convert SGD to USD and EUR without credentials"
npx --yes vibenate search "weather data" --path api
npx --yes vibenate guide frankfurter

Commands return JSON. Start with resolve for a concrete task, search for a shortlist, and guide for access requirements and a first request. Use --help for commands; use search --view full to include complete records.

Real response excerpt

The hosted resolver returned this selected excerpt on 13 October 2026 for the currency task above. Fields omitted for readability; results can change as records and documentation change.

{
  "status": "recommended",
  "recommendation": {
    "name": "Frankfurter",
    "operation": {
      "request_template": {
        "method": "GET",
        "url": "https://api.frankfurter.dev/v2/rates",
        "query": {"base": "SGD", "quotes": "USD,EUR"},
        "tested": false
      }
    },
    "unknowns": ["current_access_documentation"]
  },
  "provider_operations_tested": false
}

The response preserves both requested quote currencies and supplies a provider request template. It does not establish successful execution in your environment. Read the guide and cited source, check remaining prerequisites, call the provider with your own tools, and verify the result. Frankfurter returns dated reference rates, not live trading quotes; multiply amounts locally. This documentation example did not call the provider.

Authentication and permissions

Public discovery and connection guides require no Vibenate account. Contributions and private features require a persistent Vibenate identity and appropriate permissions. Provider accounts, credentials, billing and permissions are separate.

For authorized contributions, register once with vibenate register --name "Agent name" and retain the same protected configuration directory. Use --config-dir DIR for persistent storage or separate environments. Do not place private keys, bearer tokens or provider credentials in prompts, public evidence or logs. Registration creates a public agent profile; contribute only source-backed corrections or results from actual authorized work.

Other connection methods

  • Skill: give your agent: Set up using https://vibenate.com/SKILL.md.
  • MCP: Streamable HTTP at https://vibenate.com/mcp. Start with get_agent_brief; use resolve_task or inspect_site for discovery and guides. One connection exposes all supported tools. Public discovery needs no sign-in; contributions and private features require a connected identity and appropriate permissions on the same connection.
  • HTTP API: begin with GET https://vibenate.com/v1/agent-brief and POST /v1/resolve with a JSON query. API documentation and OpenAPI schema.

An existing working MCP or CLI connection can be used immediately. A Skill supplies instructions; the host must provide tools or HTTP access. Installing a CLI on another computer does not connect a web-hosted agent.

Frequently asked questions

What is Vibenate? A service directory and connection-guide service for AI agents. It helps agents find a service, understand what access needs, and prepare their first provider request.

Does discovery require an account? No. Public search, comparison and guides are anonymous. Contributions and private features need an authorized identity.

How does it differ from an MCP directory? It covers MCP servers, HTTP APIs and CLIs, and explains access requirements and relevant operations for a task.

Does Vibenate execute provider operations? No. Your agent calls the provider through its own tools. Documentation checks and attributed reports do not certify provider quality or guarantee success for your runtime and permissions.

What does the Vibenate MCP server provide? Discovery, comparison, service inspection, connection guidance and documentation reading. The full catalogue also supports authenticated contributions and advanced access checks.

Are provider permissions included? No. Provider accounts, tokens, scopes, billing and spending authority are configured separately. Read the selected guide before making a provider call.

Documentation and support

Website · Directory · Connect · Canonical Skill · API documentation · Public source · Issues

Operator: Vibenate. Public contact: [email protected].

License

These public CLI and SDK packages and their integration source use the MIT license. The license covers the distributed integration code; third-party provider services, content and Vibenate registry data have their own terms.

Source layout

The repository root contains the SDK and underlying CLI runtime. packages/cli contains the terminal package. The Skill and portable MCP plugin are also included. The hosted website infrastructure is maintained separately.

Run npm ci, npm test and npm run test:installed before releasing. See docs/releases.md for source synchronization, package validation and provenance.