Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Query private-equity fund performance and portfolio-company metrics.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Chronograph MCP server connects a private-capital portfolio monitoring platform — fund performance, commitment history and portfolio-company metrics — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists seven tools, all reads, and records the connector's permissions as Read. Sign-in is OAuth through Chronograph's Auth0 tenant.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
scopes_supported. Nothing at the OAuth grant separates one fund from the whole portfolio, or the help centre from the financials — entitlement comes from your Chronograph account instead.investment-metrics needs a discovery call first. Anthropic's tutorial directs users to call it with query: {help: true} to enumerate available metric types before running a real query, so the first useful answer costs two round trips.No. All seven tools are reads, Anthropic's directory records the connector's permissions as Read, and Chronograph's own plugin documentation describes the skills as reading your private Chronograph data. No tool name carries create, update, upload, delete or approve, and the platform's valuation-approval and document-collection workflows have no counterpart in this listing.
No. Anthropic's tutorial states plainly that Claude cannot access documents, custom fields, or metrics requiring a Primary Metric Type label. Chronograph's document vault of LPAs, capital account statements and AGM materials is reachable through its in-platform ChronoAI interface, not through this connector. The MCP surface returns structured metrics only.
Structured fund and company performance figures. Anthropic documents NAV, Called, Distributed, Unfunded, Net IRR, Net MOIC and Commitment Amount across commitment history, plus company exposures by status and per-investment metrics. Chronograph's own skills reference gross invested, realized and unrealized values per portfolio company, which is material non-public information about private businesses.
No. Chronograph's public plugin repository describes it as a generic query tool covering core entity attributes, and names the fields it returns: fund name, fund type, vintage year, reporting currency, geographic focus, final reporting date and general partner. It is a fixed metadata reader over a named field list, not a query forwarder.
None that narrow anything. The Auth0 tenant behind the connector advertised 14 scopes on 2026-08-23 and every one is an OpenID identity claim such as openid, profile, email and phone. The connector's own metadata document omits scopes entirely. Your entitlements come from your Chronograph account, not from the OAuth grant.
Chronograph does not answer that publicly, and neither can we. Its privacy policy covers personal information only and predates the connector. The published terms govern the marketing website, not the platform, and defer to a non-public subscription agreement. Confidentiality of fund data sits in that contract and in your LPAs. Ask your legal team first.
Yes. Chronograph's published sub-processor list names Anthropic, PBC for AI-powered product features, located in the United States. That is a genuine first-party disclosure and a useful diligence input, though the page carries a 2021 date, so confirm it is current for the connector rather than reading it as a live warranty.
Chronograph publishes no per-call rate, no credit balance and no quota. Access is gated commercially instead: you need an active Chronograph account and a paid Claude subscription. No tool among the seven can report usage, balance or spend, so an agent cannot check its consumption from inside the surface before querying.
robots.txt permits it. The capability enumeration, the setup steps, the query: {help: true} discovery step, and the negative enumeration all come from here. · retrieved 2026-08-23run-query description, the net-versus-gross split, the read-only phrasing and the drift warning; the MCP data map is at skills/chronograph-cashflow-forecast/references/chronograph-mcp-map.md. · retrieved 2026-08-23https://ai.chronograph.pe/mcp returned HTTP 401 with a Bearer challenge naming missing_auth_header. The RFC 9728 descriptor is genuinely absent — /.well-known/oauth-protected-resource and /.well-known/oauth-protected-resource/mcp both 404 with body hashes distinct from each other and matching an invented-path control. Authorization-server metadata at https://ai.chronograph.pe/.well-known/oauth-authorization-server returned 200 and omits scopes_supported; the upstream tenant at https://login.chronograph.pe/.well-known/openid-configuration advertises 14 scopes, all identity claims. · retrieved 2026-08-23llms.txt, llms-full.txt and the .md suffix — plus robots.txt, sitemap.xml and a deliberately invented path returned byte-identical 86,012-byte bodies under one MD5: an Auth0-gated application shell, not a help article. The same shell answers the gp-help, api and developer hosts on that domain. No embedded payload was present — no Next.js flight chunks, no __NEXT_DATA__, no __NUXT__, no JSON script block — so this is a login wall, not a parser failure. help.chronograph.pe 307-redirects into the GitBook editor application, which is noindex and authenticated; docs, support and lp-docs on the domain each serve Disallow: / and were not fetched beyond robots.txt. Chronograph's sub-processor list names Help Scout for support documentation, consistent with the legacy article-number URL shape. No public mirror exists, so the connector documentation on this page comes from Anthropic's tutorial and Chronograph's public repositories instead. · retrieved 2026-08-23Connect Chronograph once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.