_ registry / mcp http-sse · checked 5h ago

whichlib

https://whichlib.com

Registry code: 141fb1751c5b295a

api record

whichlib ranks open-source libraries with live GitHub, npm and PyPI data: a 0-100 health score, downloads, a one-line verdict and the install name. Call recommend_repos before adding a dependency the project does not use yet, when the user asks which library to use, or when you are not sure a package exists or is still maintained. Describe the need in plain words, not a library name. Call compare_repos to choose between candidates you already have (owner/repo names) or to check a dependency the project already uses. Install the package with the name shown on the Install line of a result…

endpoint
https://whichlib.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is whichlib live?
Yes — it answered the hub's last check (checked 5h ago). It answered 99% of checks over the last 30 days.
Is whichlib free to use?
Yes — the hub reached it with no key and no payment.
What tools does whichlib have?
3 tools: recommend_repos, compare_repos, trending_repos.
Is whichlib safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.5%

90 days 99.1%· all time 99.1%

latency
299ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 324 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • recommend an open-source library for a need
  • compare github repositories
  • list trending github repositories
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • trending_repos reads open 24h ago

    Discover projects: the most-starred GitHub repositories created in the last day, week or month, or with period "rising" repositories of any age that gained the most stars this week (like GitHub Trending; risingRank keeps that order). Optionally one language; each scored and returned sorted by score (starsRank keeps the stars order). Each result has a 0-100 score (momentum 40% (stars gained per week; without history, lifetime stars per week scaled by the npm/PyPI download trend), maintenance 25%, adoption incl. npm/PyPI weekly downloads 25%, license 10%), a tier (Strong >=75, Solid >=50, Watch >=25, Avoid <25; New for repos under 30 days old, too new to judge), a one-line verdict and the full breakdown. Not the right tool for picking a dependency, since new repositories have little maintenance history; use recommend_repos for that. One GitHub search (rising: one download of the daily list from raw.githubusercontent.com instead), plus one npm/PyPI lookup per repository when withDownloads is true. Hosted: 50 free tool calls per day per user; send header X-GitHub-Token with your own GitHub token for unlimited use, or run the npm package locally (npx -y whichlib).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 100,
          "minimum": 1,
          "description": "How many repositories to return, 1-100."
        },
        "period": {
          "enum": [
            "day",
            "week",
            "month",
            "rising"
          ],
          "type": "string",
          "default": "week",
          "description": "\"day\", \"week\" or \"month\": repos created in the last 24 hours, 7 days or 30 days. \"rising\": repos of any age by stars gained this week (the top 1,000 repos per language plus new ones are tracked)."
        },
        "language": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1,
          "description": "GitHub language name, e.g. \"TypeScript\", \"Python\", \"Rust\". Matches that language only. Omit for all languages."
        },
        "withDownloads": {
          "type": "boolean",
          "default": false,
          "description": "Also look up npm/PyPI weekly downloads for each repository. Slower: one registry lookup per repository."
        }
      }
    }
    arguments 35 lines
  • recommend_repos reads unknown 24h ago

    Find the best open-source library for a need before adding a dependency. Give the need in plain words and get up to `limit` GitHub repositories ranked by fit = score x relevance to the need. Each result has a 0-100 score (momentum 40% (stars gained per week; without history, lifetime stars per week scaled by the npm/PyPI download trend), maintenance 25%, adoption incl. npm/PyPI weekly downloads 25%, license 10%), a tier (Strong >=75, Solid >=50, Watch >=25, Avoid <25; New for repos under 30 days old, too new to judge), a one-line verdict and the full breakdown. Use this when you do not yet have candidates; use compare_repos when you already have names. Makes 3 GitHub searches plus npm/PyPI lookups for the shortlist. Hosted: 50 free tool calls per day per user; send header X-GitHub-Token with your own GitHub token for unlimited use, or run the npm package locally (npx -y whichlib).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "need"
      ],
      "properties": {
        "need": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "The need in plain words, e.g. \"python pdf parser\", \"react state management\". Name the task, not a library."
        },
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 10,
          "minimum": 1,
          "description": "How many repositories to return, 1-10."
        },
        "language": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1,
          "description": "GitHub language name, e.g. \"TypeScript\", \"Python\", \"Rust\", \"C++\". JavaScript also matches TypeScript repositories and the reverse; Python also matches Jupyter Notebook. Omit to search all languages."
        }
      }
    }
    arguments 28 lines
  • compare_repos reads unknown 24h ago

    Compare 2-10 known GitHub repositories side by side, best score first: score and tier, stars, forks, open issues, last push, license, npm/PyPI weekly downloads (only when the registry links back to the repository) and a verdict. Each result has a 0-100 score (momentum 40% (stars gained per week; without history, lifetime stars per week scaled by the npm/PyPI download trend), maintenance 25%, adoption incl. npm/PyPI weekly downloads 25%, license 10%), a tier (Strong >=75, Solid >=50, Watch >=25, Avoid <25; New for repos under 30 days old, too new to judge), a one-line verdict and the full breakdown. Use this to choose between candidates you already have (for example zod vs valibot) or to check a dependency the project already uses; use recommend_repos to find candidates. One GitHub API call per repository plus npm/PyPI lookups. A repository that does not exist is listed under notFound and the rest are still compared; the call fails only if none can be fetched, or when GitHub's rate limit is reached or the token is rejected. Hosted: 50 free tool calls per day per user; send header X-GitHub-Token with your own GitHub token for unlimited use, or run the npm package locally (npx -y whichlib).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "repos"
      ],
      "properties": {
        "repos": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 140,
            "minLength": 3
          },
          "maxItems": 10,
          "minItems": 2,
          "description": "Repository names as owner/repo, e.g. [\"colinhacks/zod\", \"fabian-hiller/valibot\"]. Not URLs or npm/PyPI package names."
        }
      }
    }
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 141fb1751c5b295a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/141fb1751c5b295a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/141fb1751c5b295a/badge.svg)](https://brick.blue/agent/141fb1751c5b295a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.