Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Vulners (BYOK) icon

Vulners (BYOK)

Search the Vulners vulnerability database for CVEs, advisories and exploits, and read affected packages and CPE data per CVE, with your own API key

Unify Dynamics LLC

Tools7read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderVulnersunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which public exploits exist for CVE-2023-20198?
Tools called
search_bulletins
Give me the Vulners record for CVE-2024-3400
Tools called
get_bulletin
Which packages are affected by CVE-2021-44228?
Tools called
get_cve_affected_packages
Which CPE configurations does CVE-2021-44228 apply to?
Tools called
get_cve_affected_cpe
What is the CPE for Google Chrome?
Tools called
search_cpe
Which collections does Vulners hold?
Tools called
list_collections

About

Vulners (BYOK) lets an AI assistant read your own Vulners data through the Vulners API with a key you supply (Vulners API key). Read-only: 7 tools (search_bulletins, get_bulletin, get_cve_affected_packages, get_cve_affected_cpe, search_cpe, list_collections, get_bulletin_history). 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 vulners.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vulners. Vulners and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Vulners API (vulners.com) with a BYOK key; documentation: https://docs.vulners.com/docs/assets/openapi.yaml. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

7 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data7 tools
  • Search bulletinsSearch Vulners bulletins (CVEs, vendor advisories, exploits, scanner plugins) with a Lucene query.
  • Get bulletinGet one bulletin by id (a CVE id such as CVE-2024-3400, or an advisory, exploit or plugin id) with title, description, type, family, dates, CVSS…
  • Get cve affected packagesList the packages affected by one CVE across distributions and ecosystems: source advisory id, package name, vulnerable version range, registry…
  • Get cve affected cpeList the CPE applicability configurations of one CVE (vendor advisories and NVD), as nested AND/OR nodes with version bounds.
  • Search cpeFind CPE identifiers for a vendor and product (only CPEs that are linked to CVEs).
  • List collectionsList the datasets (collections) in Vulners, such as exploit databases and advisory feeds, with a description, record count and last update time.
  • Get bulletin historyGet the edit history of one bulletin: each change with the field, its value at that edition, edition number and time.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-vulners.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 7 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-vulners.connectorbay.com/mcp
RESTPOST https://byok-vulners.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-vulners.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Vulners API key in the X-Upstream-Key header (get one at docs.vulners.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Vulners connector: questions and answers

What is the Vulners connector?

Vulners (BYOK) lets an AI assistant read your own Vulners data through the Vulners API with a key you supply (Vulners API key). It is a hosted MCP server with 7 tools such as Search bulletins, Get bulletin, Get cve affected packages, Get cve affected cpe, Search cpe, List collections, published by Unify Dynamics LLC. It is independent and not affiliated with Vulners.

How do I connect Vulners to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-vulners.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-vulners.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-vulners.json.

Do I need a Vulners account or API key?

Yes: this is a bring-your-own-key connector. Create a Vulners API key at https://docs.vulners.com/docs/quickstart/authentication/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Vulners read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Vulners connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Boomi (BYOK)

Read your Boomi AtomSphere account, runtimes, processes, environments, deployments and execution history with your own API token (US platform)

Live · MCP + REST9 tools

Bordeaux Metropole Open Data (BYOK)

Browse and query the open datasets of the Bordeaux Metropole open data portal (Opendatasoft Explore API) with your own portal API key

Live · MCP + REST7 tools

Botify (BYOK)

Read your Botify SEO projects, crawl analyses, crawl statistics, sitemap reports, Search Console stats and jobs with your own API token

Live · MCP + REST10 tools

Box Admin (BYOK)

Read your Box enterprise groups and members, webhooks, terms of service, storage policies, workflows and Slack folder mappings with your own admin token

Live · MCP + REST10 tools

Box Governance (BYOK)

Read your Box retention policies, retention assignments, legal hold policies and file-version retention records with your own developer or OAuth token

Live · MCP + REST8 tools

Box Metadata (BYOK)

Read your Box metadata templates and their fields, security classifications, taxonomies and cascade policies with your own developer or OAuth token

Live · MCP + REST8 tools

Documentation

Back to top

Vulners (BYOK) — connector documentation

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

What Vulners (BYOK) is for

Vulners (BYOK) lets an AI assistant read your own Vulners data through the Vulners API with a key you supply (Vulners API key). Read-only: 7 tools (search_bulletins, get_bulletin, get_cve_affected_packages, get_cve_affected_cpe, search_cpe, list_collections, get_bulletin_history). 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 vulners.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vulners. Vulners 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 public exploits exist for CVE-2023-20198?"
  • "Give me the Vulners record for CVE-2024-3400"
  • "Which packages are affected by CVE-2021-44228?"
  • "Which CPE configurations does CVE-2021-44228 apply to?"
  • "What is the CPE for Google Chrome?"
  • "Which collections does Vulners hold?"

What it does

  • search_bulletins: Search Vulners bulletins (CVEs, vendor advisories, exploits, scanner plugins) with a Lucene query. Returns id, title, type, family, dates, CVSS, EPSS, CVE list and link per hit, plus the total hit count. Query examples: 'Fortinet AND RCE order:published', 'bulletinFamily:exploit AND "CVE-2023-20198"', 'type:cve AND cvss.score:[9 TO 10]'.
  • get_bulletin: Get one bulletin by id (a CVE id such as CVE-2024-3400, or an advisory, exploit or plugin id) with title, description, type, family, dates, CVSS score and vector, EPSS and CVE list. The answer is a map keyed by the requested id.
  • get_cve_affected_packages: List the packages affected by one CVE across distributions and ecosystems: source advisory id, package name, vulnerable version range, registry (deb, rpm, npm, maven ...) and distro scope.
  • get_cve_affected_cpe: List the CPE applicability configurations of one CVE (vendor advisories and NVD), as nested AND/OR nodes with version bounds. The answer can be large for widely affected products.
  • search_cpe: Find CPE identifiers for a vendor and product (only CPEs that are linked to CVEs). Returns the best match and further candidates.
  • list_collections: List the datasets (collections) in Vulners, such as exploit databases and advisory feeds, with a description, record count and last update time. Sorted by size, largest first.
  • get_bulletin_history: Get the edit history of one bulletin: each change with the field, its value at that edition, edition number and time. Long values can make the answer large.

BYOK key

You bring your own Vulners Vulners API key (https://docs.vulners.com/docs/quickstart/authentication/). 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 vulners.com 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

Live from the Vulners API (vulners.com) with a BYOK key; documentation: https://docs.vulners.com/docs/assets/openapi.yaml. 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 Vulners. Vulners 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 Vulners account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Vulners (BYOK) — Privacy Policy

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

What Vulners (BYOK) is. Vulners (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Vulners data: Search the Vulners vulnerability database for CVEs, advisories and exploits, and read affected packages and CPE data per CVE, with your own API key. You bring your own Vulners Vulners API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Vulners 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 vulners.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Vulners 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 Vulners receives. The request we make on your behalf, including the key and the arguments, under Vulners's own terms and privacy policy. Vulners acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Vulners 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 Vulners 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. Vulners (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 Vulners at any time to end all access.

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

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

Terms of service

Back to top

Vulners (BYOK) — Terms of Service

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

  1. The Service. Vulners (BYOK) provides: Search the Vulners vulnerability database for CVEs, advisories and exploits, and read affected packages and CPE data per CVE, with your own 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 Vulners credentials and only access data you are allowed to access. Vulners's terms apply to your use of Vulners; 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 Vulners. Vulners 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 Vulners returns, lightly trimmed; it may be incomplete, delayed or changed by Vulners. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Vulners 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 Vulners'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; Vulners 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 Vulners 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 Vulners 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-vulners

Vulners (BYOK) support

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

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. Vulners (BYOK) never asks for them.

Get Vulners (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Vulners Vulners API key. Create one at https://docs.vulners.com/docs/quickstart/authentication/, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Vulners. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Vulners.