MetaDefender Cloud (BYOK)

MetaDefender Cloud (BYOK) — connector documentation

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

What MetaDefender Cloud (BYOK) is for

MetaDefender Cloud (BYOK) lets an AI assistant read your own MetaDefender Cloud data through the MetaDefender Cloud API with a key you supply (MetaDefender Cloud API key). Read-only: 7 tools (lookup_hash, lookup_ip, lookup_domain, lookup_url, get_api_key_info, get_api_key_usage, get_api_key_remaining). 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.metadefender.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by MetaDefender Cloud. MetaDefender Cloud 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:

• "Is this file hash known as malware in MetaDefender Cloud?"
• "Is the IP address 8.8.8.8 flagged by MetaDefender Cloud?"
• "Is the domain example.com flagged by MetaDefender Cloud?"
• "Is the URL http://example.com/login flagged by MetaDefender Cloud?"
• "What are the limits of my MetaDefender Cloud API key?"
• "How many MetaDefender Cloud requests have I used?"

What it does

• lookup_hash: Look up the scan report of a file by MD5, SHA-1 or SHA-256 hash in MetaDefender Cloud (multi-engine verdicts). The official page lists this endpoint but not its answer fields, so the answer is returned as received (long answers are cut).
• lookup_ip: Look up the reputation of an IP address in MetaDefender Cloud. The official page lists this endpoint but not its answer fields, so the answer is returned as received (long answers are cut).
• lookup_domain: Look up the reputation of a domain in MetaDefender Cloud. The official page lists this endpoint but not its answer fields, so the answer is returned as received (long answers are cut).
• lookup_url: Look up the reputation of a URL in MetaDefender Cloud. The URL goes into the request path and is encoded for you. The official page lists this endpoint but not its answer fields, so the answer is returned as received (long answers are cut).
• get_api_key_info: Show the configured limits of the key: reputation, prevention, threat-intelligence, sandbox and feed limits, rate-limit, interval, expiry and nickname.
• get_api_key_usage: Show how much of each limit (reputation, prevention, threat-intelligence search, feed, download, sandbox) the key has used.
• get_api_key_remaining: Show how much of each limit the key has left, and the throttling limit.

BYOK key

You bring your own MetaDefender Cloud MetaDefender Cloud API key (https://metadefender.opswat.com/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 api.metadefender.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

• https://www.opswat.com/docs/mdcloud/metadefender-cloud-api-v4 (the API this connector calls, with a BYOK key)

Live from the MetaDefender Cloud API (api.metadefender.com) with a BYOK key; documentation: https://www.opswat.com/docs/mdcloud/metadefender-cloud-api-v4. 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 MetaDefender Cloud. MetaDefender Cloud 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 MetaDefender Cloud account.

Built for: Worldwide. Languages: English.

MetaDefender Cloud (BYOK) — Privacy Policy

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

What MetaDefender Cloud (BYOK) is. MetaDefender Cloud (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own MetaDefender Cloud data: Look up file hashes, IP addresses, domains and URLs in OPSWAT MetaDefender Cloud reputation data and check key limits with BYOK. You bring your own MetaDefender Cloud MetaDefender Cloud API key; the assistant sends it to us with each request.

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

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

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

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

MetaDefender Cloud (BYOK) — Terms of Service

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

1. The Service. MetaDefender Cloud (BYOK) provides: Look up file hashes, IP addresses, domains and URLs in OPSWAT MetaDefender Cloud reputation data and check key limits with BYOK. 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 MetaDefender Cloud credentials and only access data you are allowed to access. MetaDefender Cloud's terms apply to your use of MetaDefender Cloud; 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 MetaDefender Cloud. MetaDefender Cloud 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 MetaDefender Cloud returns, lightly trimmed; it may be incomplete, delayed or changed by MetaDefender Cloud. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your MetaDefender Cloud 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 MetaDefender Cloud'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; MetaDefender Cloud 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 MetaDefender Cloud 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 MetaDefender Cloud 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-metadefender

MetaDefender Cloud (BYOK) support

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

• MCP endpoint: https://byok-metadefender.connectorbay.com/mcp
• REST API: https://byok-metadefender.connectorbay.com/openapi.json
• Live status: https://byok-metadefender.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. MetaDefender Cloud (BYOK) never asks for them.