Recorded Future MCP Overview

September 24, 2026 15:17

Recorded Future MCP is generally available from 28 September 2026.

Recorded Future MCP gives AI clients and agents direct, authenticated access to Recorded Future intelligence. You connect your client once, and your agents can query the Intelligence Graph, your own detections, your alerts, and your attack surface as tools — without you building or maintaining an API integration.

Server URL: https://mcp.recordedfuture.com/mcp

What Recorded Future MCP is

Recorded Future MCP is a remote MCP (Model Context Protocol) server. Any MCP-capable client that supports a modern authentication flow can connect to it and call Recorded Future tools directly.

Backed by the Intelligence Graph. Name an entity — an IP, domain, hash, CVE, company, threat actor, malware family — and the relevant intelligence comes back, along with the entities linked to it.
Entity disambiguation built in. Recorded Future resolves entities to Master IDs, so your agents work on the right entity rather than a name collision.
Efficient for agents. Tools return structured intelligence in one call where a general web search would need several, which reduces both tool calls and token spend.
Graph traversal, not repeated searching. Agents pivot from one entity to its related infrastructure, actors and vulnerabilities instead of re-searching for each one.
Non-attributable collection. Recorded Future performs the collection. Your agents' research activity stays off the sites and sources being queried.

What Recorded Future MCP is not

It is not a replacement for the Recorded Future APIs. Some tools expose capabilities that are not available through the APIs, but the APIs remain the right choice for bulk data delivery, risk list downloads, and feed ingestion.
It does not grant access to modules you do not own. See Tools are gated by entitlement.
It is not multi-organization aware. See Multi-organization support.

Who can use it

Recorded Future MCP is included at no additional cost if your package includes an unlimited number of integration users.

If your package does not include unlimited integration users, you can still connect to Recorded Future MCP with your individual portal user credentials until the end of 2026. You cannot create an integration user from the Integration Center.

If you are unsure of your package details, contact your Recorded Future account team.

Quotas, allowances, and entitlements are covered in a separate article: Recorded Future MCP: Quota and Entitlements.

How to connect

There are two connection paths. Make your selection based on whether your connection belongs to a person or to a system.

Path	Use it when	Guide
Integration user (recommended for enterprises)	Agents, automated workflows, backend services, anything running unattended	Generating Credentials for Recorded Future MCP (Integration Users)
Portal user	An individual connecting their own client, signing in with SSO	Connecting to Recorded Future MCP

The integration user path, in short:

Go to Integration Center in the Recorded Future portal and find the Recorded Future MCP tile.
Create an integration user and select the entitlements it should have.
Select the authentication type: Client ID/Secret (OAuth 2.0).
Enter those details in your client.

Your client secret is shown once, at creation. Store it securely — Recorded Future cannot retrieve it for you. If it is lost, revoke it and generate a new credential from the same tile.

Supported authentication methods

OAuth 2.0 client credentials (Client ID/Secret) — for integration users
OAuth 2.0 authorisation code flow via browser — for individual portal users, including SSO
Dynamic Client Registration (DCR)
Client ID Metadata Documents (CIMD)

Connecting specific platforms

Either of the above connection paths works with any MCP client that supports one of the authentication methods listed above. The following clients are verified to work with Recorded Future MCP:

Claude (web, desktop and Claude Code)
ChatGPT
Microsoft Copilot (via Copilot Studio)
GitHub Copilot
Gemini CLI
Cursor

Other MCP-capable clients will generally work if they support one of the listed authentication methods.

Finding Recorded Future in client marketplaces

Recorded Future MCP is not yet listed in the OpenAI or Anthropic connector marketplaces. Registration is in progress. Until then, add Recorded Future MCP manually in your client using the server URL: https://mcp.recordedfuture.com/mcp.

Tools are gated by entitlement

Every tool call is authenticated as the portal user or integration user that made it, and authorized based on that user's privileges. For example, a user without Vulnerability Intelligence will not see Vulnerability Intelligence tools; a user without Attack Surface Intelligence will not see ASI tools.

Note the following:

Scope integration users deliberately. Give each integration user only the entitlements its agent needs. This is the simplest way to control what your agents can reach.
Your tool list may be shorter than the published catalogue. The Recorded Future MCP: Available Tools includes everything available at GA. You will see the subset your entitlements cover.

Tools available at general availability

Recorded Future MCP exposes tools across the following capability areas:

Entity research — resolve names, aliases and free text to Master IDs; Intelligence Cards; graph pivots to related IOCs, malware, CVEs, and TTPs
Risk scoring — risk rules, score history, high-risk entities by type
Search and source evidence — search Recorded Future intelligence with the references behind it, recent reporting per entity, open web search, and URL retrieval
Insikt Group research — find, summarize and retrieve Insikt notes, including by Diamond Model
Your organization's analyst notes — search, read, publish and edit notes authored inside your organization
Threat maps and MITRE ATT&CK — threat actor and malware maps, date-to-date diffs, ATT&CK matrices and evidence
Malware and sandbox analysis — natural-language malware search, counts, and aggregations
Ransomware — victim references, ransomware metadata, actor and malware TTP evidence
Malicious Traffic Analysis — references derived from Insikt netflow collection
Collective Insights — your own detections: coverage checks, trends, top malware families, related IOCs, devices, actors, TTPs and CVEs, ATT&CK heat maps
Alerts and alert rules — search and retrieve your alerts, search your alert rules
Intelligence requirements — list your PIRs, SIRs, and EEIs
Watch Lists and custom lists — read list contents and membership, and update entries
Attack Surface Intelligence — projects, assets, exposures, tags, and investigation workflows
Third-Party Intelligence and vulnerabilities — vendor and product vulnerability exposure, and your portfolio's exposure to a given CVE
Connection context — confirm which identity and organization a credential is connected as

Every currently available tool, with a description of what it does, is listed in Recorded Future MCP: Available Tools.

Migrating from the MCP Pilot

If you used Recorded Future MCP during the Pilot program, the server URL does not change. https://mcp.recordedfuture.com/mcp now points to the GA gateway instead of the Pilot gateway.

You do need to reauthenticate. Your client may report that the connection has stopped working, or prompt you to sign in again. Reconnect and you are done. No configuration changes are required.

If your package does not include unlimited integration users, your Pilot access continues through portal users until the end of 2026.

Multi-organization support

Recorded Future MCP is not multi-organization aware at this time; a connection is scoped to a single organization. Multi-organization support is planned for Q4 2026.

Frequently asked questions

My MCP connection stopped working and asked me to sign in again.
This is expected at the GA cutover. The GA gateway has replaced the Pilot gateway at the same URL, so you need to reauthenticate. Nothing else changes.

Can my agent use tools from a module we do not own?
No. Tools are authorized against the privileges of the portal user or integration user making the call. Without Vulnerability Intelligence, for example, the Vulnerability Intelligence tools do not appear.

Which tools require which module?
This is currently enforced silently - any tool that requires a module for which you are not licensed will not be displayed in your client.

How many API calls does an MCP tool call use?
One tool call counts as one API call against your existing allowance, regardless of how many underlying calls the tool makes. You can find details in Recorded Future MCP: Quota and Entitlements.

Where can I see how much we are using?
In the Integration Center alongside the Recorded Future MCP tile.

Can I use both an integration user and my own portal user?
Yes. Use an integration user for anything running unattended, and a portal user for your own interactive client.

Can I restrict which tools an agent can call?
Scope the integration user's entitlements when you create it. Many clients also let you enable or disable individual tools on a connection.

Is Recorded Future MCP available in the OpenAI or Anthropic marketplaces?
Not yet. Registration is in progress. Add the server manually in the meantime.

Getting help

For connection and credential problems, contact Recorded Future support at support.recordedfuture.com.
For eligibility and packaging questions, contact your Recorded Future account team.

Recorded Future MCP: Available Tools for the full tool catalogue
Connecting to Recorded Future MCP for portal users and SSO
Generating Credentials for Recorded Future MCP (Integration Users) for integration users via the Integration Center
Connecting to Recorded Future MCP: Microsoft Copilot
Recorded Future MCP: Quota and Entitlements

This content is confidential. Do not distribute or download content in a manner that violates your Recorded Future license agreement. Sharing this content outside of licensed Recorded Future users constitutes a breach of the terms and/or agreement and shall be considered a breach by your organization.