Integration

Connect Files.com to CVE.report

When something happens in Files.com, your agent does the next thing in CVE.report. Describe it and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want Files.com and CVE.report to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Files.com holds the files your security work produces, and CVE.report holds the record behind each CVE identifier. Joining them means that when a report, folder or share link shows up in Files.com, the matching CVE record is pulled from CVE.report and available for the next step, such as filing the report into a folder named for that CVE.

Example flows

What Files.com can start in CVE.report

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Files.com and CVE.report

Triggers and actions 7 triggers · 17 actions

Each app on its own

Reviews

What our customers say

More from Files.com

More into CVE.report

Questions

Files.com and CVE.report, answered

Can something in CVE.report start one of these setups?

No, CVE.report is only used for fetching a record, with the Get CVE record action. Every setup here starts from a Files.com event such as a new file upload, a deleted file, a new share link or a finished automation run.

What if the file name has no CVE identifier in it?

You can tell the agent to only look up a record on CVE.report when the Files.com path actually contains an identifier, and to leave the file alone otherwise. The agent tests every scenario, including files that carry no identifier at all.

What can start an automation from Files.com?

Any of Files.com's 7 triggers in the catalog, including Automation Run Completed, File Deleted, New File or Folder Created and New File Uploaded. Describe the moment in plain language and your agent picks the right one.

What can your agent do in CVE.report when something happens in Files.com?

Any of CVE.report's 1 action, including Get CVE record. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from CVE.report to Files.com?

CVE.report has no triggers in the catalog today, so automations start in Files.com. If you need the other direction, ask: your agent reads CVE.report's API documentation and adds it.

Do I have to build a connector for Files.com or CVE.report?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.