General Tools
dealflow.fyi
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://dealflow.fyi/mcp
MCP server metadata
- Name
- dealflow-fyi
- Version
- 0.1.0
Read-only, keyless tools for dealflow.fyi, a living M&A data room and deal service. They return public information: pricing, capabilities, the ideal-customer profile, the machine-readable surfaces, and contact. The credentialed product operations (sync, docs.generate, ask) run only within an engagement using the seller's restricted, read-only credentials; they are described here, not executed.
Known tools 5
get_capabilitiesWhat dealflow.fyi does: live sync, buyer-specific document generation, data-room Q&A, and the AI agent-readiness report.
Inferred read-onlyget_icpIdeal-customer profile: who dealflow.fyi is for, who it is not for, and how to self-classify.
Inferred read-onlylist_surfacesEnumerate the public, keyless machine-readable surfaces of dealflow.fyi with their URLs.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.dealflow-fyi]
url = "https://dealflow.fyi/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dealflow-fyi": {
"type": "http",
"url": "https://dealflow.fyi/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dealflow-fyi
Remote MCP URL: https://dealflow.fyi/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"dealflow-fyi": {
"url": "https://dealflow.fyi/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dealflow-fyi": {
"type": "http",
"url": "https://dealflow.fyi/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dealflow-fyi",
"transport": "streamable-http",
"url": "https://dealflow.fyi/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.