Libraries.io (BYOK)

Libraries.io (BYOK) — connector documentation

• MCP endpoint: https://byok-librariesio.connectorbay.com/mcp
• REST API: POST https://byok-librariesio.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-librariesio.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Libraries.io Libraries.io API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-librariesio.connectorbay.com/health · Tool schemas: https://byok-librariesio.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-librariesio · agent@connectorbay.com

What Libraries.io (BYOK) is for

Libraries.io (BYOK) lets an AI assistant read your own Libraries.io data through the Libraries.io API with a key you supply (Libraries.io API key). Read-only: 11 tools (list_platforms, get_project, search_projects, list_project_dependents, list_project_contributors, get_project_sourcerank, get_repository, get_github_user, list_user_repositories, list_user_projects, list_subscriptions). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to libraries.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Libraries.io. Libraries.io and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which package managers does Libraries.io cover?"
• "How popular is the NPM package react and when was it last released?"
• "Find popular Rust packages for parsing JSON"
• "Which packages depend on the NPM package base62?"
• "Who contributes to the NPM package base62?"
• "What is the SourceRank breakdown of the NPM package base62?"

What it does

• list_platforms: List the package managers Libraries.io tracks with their project counts, homepage and default language.
• get_project: Get a package's description, license, stars, rank, latest release and dependent counts (the full version list is left out).
• search_projects: Search packages across package managers by text, with optional filters for platform, language, license and keyword, and sort order.
• list_project_dependents: List packages that have at least one version depending on a package, 30 per page by default.
• list_project_contributors: List the GitHub contributors of a package's repository with login, name, company and location.
• get_project_sourcerank: Get the SourceRank score breakdown of a package: documentation, license, releases, dependents, stars and maintenance signals.
• get_repository: Get a GitHub repository as Libraries.io tracks it: description, language, stars, forks, license, rank and last push.
• get_github_user: Get a GitHub user or organization as Libraries.io tracks it: name, company, location, followers and type.
• list_user_repositories: List the repositories owned by a GitHub user or organization with language, stars, forks, license and last push.
• list_user_projects: List the packages published from a GitHub user's or organization's repositories with release, stars and dependent counts.
• list_subscriptions: List the packages you subscribe to for release notifications, with latest release and prerelease preference.

BYOK key

You bring your own Libraries.io Libraries.io API key (https://libraries.io/account). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to libraries.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://libraries.io/api (the API this connector calls, with a BYOK key)

Live from the Libraries.io API (libraries.io) with a BYOK key; documentation: https://libraries.io/api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Libraries.io. Libraries.io and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Libraries.io account.

Built for: Worldwide. Languages: English.

Libraries.io (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Libraries.io (BYOK) is. Libraries.io (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Libraries.io data: Look up open-source packages across package managers, their dependents, contributors and SourceRank, and your subscriptions, with your own Libraries.io API key. You bring your own Libraries.io Libraries.io API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Libraries.io call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to libraries.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Libraries.io rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Libraries.io receives. The request we make on your behalf, including the key and the arguments, under Libraries.io's own terms and privacy policy. Libraries.io acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Libraries.io gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Libraries.io data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Libraries.io (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Libraries.io at any time to end all access.

Children. Libraries.io (BYOK) is a general-audience service operated by the adult using the assistant, under Libraries.io's own age rules.

Changes. We will post changes here with a new effective date.

Libraries.io (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Libraries.io (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Libraries.io (BYOK) provides: Look up open-source packages across package managers, their dependents, contributors and SourceRank, and your subscriptions, with your own Libraries.io API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Libraries.io credentials and only access data you are allowed to access. Libraries.io's terms apply to your use of Libraries.io; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Libraries.io. Libraries.io and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Libraries.io returns, lightly trimmed; it may be incomplete, delayed or changed by Libraries.io. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Libraries.io account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Libraries.io's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Libraries.io may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Libraries.io key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Libraries.io takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-librariesio

Libraries.io (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-librariesio.connectorbay.com/mcp
• REST API: https://byok-librariesio.connectorbay.com/openapi.json
• Live status: https://byok-librariesio.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Libraries.io (BYOK) never asks for them.