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

Interlynk (BYOK)

Read your Interlynk SBOM products, versions, components, vulnerabilities and VEX statuses with your own security token

Unify Dynamics LLC

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

Try asking

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

Which Interlynk organization does my token belong to?
Tools called
get_organization
Which products and SBOM versions do I have in Interlynk?
Tools called
list_products
Find the payments product in Interlynk
Tools called
find_product
Has Interlynk finished scanning this SBOM version?
Tools called
get_version_scan_status
Which components are in this Interlynk SBOM version?
Tools called
list_version_components
What vulnerabilities does this Interlynk SBOM version have?
Tools called
list_version_vulnerabilities

About

Interlynk (BYOK) lets an AI assistant read your own Interlynk data through the Interlynk API with a key you supply (Interlynk security token (personal or service token)). Read-only: 8 tools (get_organization, list_products, find_product, get_version_scan_status, list_version_components, list_version_vulnerabilities, get_vulnerability, list_vex_statuses). 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 api.interlynk.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Interlynk. Interlynk and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Interlynk API (api.interlynk.io) with a BYOK key; documentation: https://docs.interlynk.io/api/interlynk-api.md. 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

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

OpenAPI
Read your data8 tools
  • Get organizationShow the id and name of the Interlynk organization the token belongs to.
  • List productsList products with their environments and SBOM versions (id, version, vulnerability scan status, primary component).
  • Find productFind products whose name partly matches a text (case-insensitive) and list their environments and versions.
  • Get version scan statusShow a version's vulnerability scan status and the status of its automation, vulnerability scan and policy scan stages.
  • List version componentsList the components (dependencies) of one SBOM version with name, version and package URL.
  • List version vulnerabilitiesList the vulnerabilities found in one SBOM version with advisory id, source, severity, CVSS score, affected component and VEX status.
  • Get vulnerabilityGet a global vulnerability record by its Interlynk UUID: advisory id, CVE alias, severity, CVSS, description, KEV flag and EPSS score.
  • List vex statusesList the valid VEX status names and ids of the organization (for example In Triage, Not Affected, Affected, Fixed).

Information

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

Connect it to your agent

Three ways in, the same 8 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-interlynk.connectorbay.com/mcp
RESTPOST https://byok-interlynk.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-interlynk.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 Interlynk security token (personal or service token) in the X-Upstream-Key header (get one at docs.interlynk.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

Interlynk connector: questions and answers

What is the Interlynk connector?

Interlynk (BYOK) lets an AI assistant read your own Interlynk data through the Interlynk API with a key you supply (Interlynk security token… It is a hosted MCP server with 8 tools such as Get organization, List products, Find product, Get version scan status, List version components, List version vulnerabilities, published by Unify Dynamics LLC. It is independent and not affiliated with Interlynk.

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

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

Do I need a Interlynk account or API key?

Yes: this is a bring-your-own-key connector. Create a Interlynk security token (personal or service token) at https://docs.interlynk.io/api/getting-started/authentication.md 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 Interlynk read-only?

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

Is the Interlynk 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

Prefect Cloud (BYOK)

Read your Prefect Cloud workspaces, flows, deployments, flow runs, work pools and usage with BYOK

Live · MCP + REST8 tools

Prefect Cloud Ops (BYOK)

Read Prefect Cloud work queues, workers, task runs, automations, concurrency limits, block types, artifacts and variable names, plus single flow runs and deployments, with your own API key

Live · MCP + REST11 tools

Prime Intellect (BYOK)

Read your Prime Intellect GPU pods, disks, container images, teams and wallet balance, and browse live GPU availability and prices, with your own API key

Live · MCP + REST9 tools

Prisma Postgres (BYOK)

Read your Prisma Postgres workspaces, projects, databases, backups, usage and regions through the Management API with your own service token

Live · MCP + REST10 tools

Prismic Content (BYOK)

Read the published documents, tags, languages and content refs of your Prismic repository through its Content API with your own access token

Live · MCP + REST5 tools

Prismic Models (BYOK)

Read the custom types, shared slices and media library of your Prismic repository with your own write token and repository ID

Live · MCP + REST5 tools

Documentation

Back to top

Interlynk (BYOK) — connector documentation

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

What Interlynk (BYOK) is for

Interlynk (BYOK) lets an AI assistant read your own Interlynk data through the Interlynk API with a key you supply (Interlynk security token (personal or service token)). Read-only: 8 tools (get_organization, list_products, find_product, get_version_scan_status, list_version_components, list_version_vulnerabilities, get_vulnerability, list_vex_statuses). 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 api.interlynk.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Interlynk. Interlynk 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 Interlynk organization does my token belong to?"
  • "Which products and SBOM versions do I have in Interlynk?"
  • "Find the payments product in Interlynk"
  • "Has Interlynk finished scanning this SBOM version?"
  • "Which components are in this Interlynk SBOM version?"
  • "What vulnerabilities does this Interlynk SBOM version have?"

What it does

  • get_organization: Show the id and name of the Interlynk organization the token belongs to.
  • list_products: List products with their environments and SBOM versions (id, version, vulnerability scan status, primary component). Cursor paged.
  • find_product: Find products whose name partly matches a text (case-insensitive) and list their environments and versions.
  • get_version_scan_status: Show a version's vulnerability scan status and the status of its automation, vulnerability scan and policy scan stages.
  • list_version_components: List the components (dependencies) of one SBOM version with name, version and package URL. Cursor paged; optional name search.
  • list_version_vulnerabilities: List the vulnerabilities found in one SBOM version with advisory id, source, severity, CVSS score, affected component and VEX status. Cursor paged.
  • get_vulnerability: Get a global vulnerability record by its Interlynk UUID: advisory id, CVE alias, severity, CVSS, description, KEV flag and EPSS score.
  • list_vex_statuses: List the valid VEX status names and ids of the organization (for example In Triage, Not Affected, Affected, Fixed).

BYOK key

You bring your own Interlynk Interlynk security token (personal or service token) (https://docs.interlynk.io/api/getting-started/authentication.md). 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 api.interlynk.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

Live from the Interlynk API (api.interlynk.io) with a BYOK key; documentation: https://docs.interlynk.io/api/interlynk-api.md. 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 Interlynk. Interlynk 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 Interlynk account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Interlynk (BYOK) — Privacy Policy

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

What Interlynk (BYOK) is. Interlynk (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Interlynk data: Read your Interlynk SBOM products, versions, components, vulnerabilities and VEX statuses with your own security token. You bring your own Interlynk Interlynk security token (personal or service token); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Interlynk 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 api.interlynk.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 Interlynk 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 Interlynk receives. The request we make on your behalf, including the key and the arguments, under Interlynk's own terms and privacy policy. Interlynk acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

Terms of service

Back to top

Interlynk (BYOK) — Terms of Service

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

  1. The Service. Interlynk (BYOK) provides: Read your Interlynk SBOM products, versions, components, vulnerabilities and VEX statuses with your own security token. 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 Interlynk credentials and only access data you are allowed to access. Interlynk's terms apply to your use of Interlynk; 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 Interlynk. Interlynk 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 Interlynk returns, lightly trimmed; it may be incomplete, delayed or changed by Interlynk. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Interlynk 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 Interlynk'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; Interlynk 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 Interlynk 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 Interlynk 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-interlynk

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

Get Interlynk (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Interlynk Interlynk security token (personal or service token). Create one at https://docs.interlynk.io/api/getting-started/authentication.md, 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 Interlynk. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Interlynk.