GP Intel
REMOTE · WWW.GP-INTEL.COM
Verified European PE ownership: who owns a company, GP portfolios, exits by year. Hand-checked.
Available components
Last scanned (22 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Oct 26 0
- Tool “search_companies” rewrote its description, which is the text the model reads security
- Tool “search_deals” rewrote its description, which is the text the model reads security
- Tool “search_exits” rewrote its description, which is the text the model reads security
- Tool “search_gps” rewrote its description, which is the text the model reads security
- Tool “who_owns” rewrote its description, which is the text the model reads security
- “search_exits” reworded the description of “buyer” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 13 Aug 26 0
- Tool “search_exits” rewrote its description, which is the text the model reads security
- “search_exits” reworded the description of “exit_type” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://www.gp-intel.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.gp-intel.com | CN=YR1,O=Let's Encrypt,C=US | 28 Aug 2026 | 26 Nov 2026 | RSA 2048 | SHA256-RSA | 54605f71e28bc1bca7ce71d802c294375c0 |
| SANs: www.gp-intel.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.gp-intel.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| gp-intel.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.gp-intel.com/api/mcp | HTTP error | 404 | |
| http (plaintext) | http://www.gp-intel.com/api/mcp | HTTPS enforced | 308 | https://www.gp-intel.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
gp_exits PE firm exits by year ~87
List the exits (realised divestments) of a private equity firm, optionally for a specific year. The query AI search cannot answer reliably: 'what did GP X sell in YEAR'. Returns company, exit year, exit route, hold period.
| Name | Type | Req | Description |
|---|---|---|---|
| gp | string | yes | PE firm name |
| year | integer | – | Exit year filter, e.g. 2024 |
No output schema declared.
No examples provided.
gp_portfolio PE firm portfolio ~88
List the portfolio companies of a private equity firm (GP), optionally filtered to active holdings or exited positions. Returns company, sector, geography, entry year, exit year/type, fund and vintage.
| Name | Type | Req | Description |
|---|---|---|---|
| gp | string | yes | PE firm name, e.g. 'Ardian' or 'PAI Partners' |
| status | string | – | Filter: only active holdings or only exited positions |
No output schema declared.
No examples provided.
search_companies Search PE-backed companies ~44
Search the 34,000+ PE-backed companies tracked on GP Intel by name.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Company name or fragment |
No output schema declared.
No examples provided.
search_deals Search PE investments across all firms ~256
Cross-firm investment search across ALL European PE firms: filter portfolio companies by entry year (or range), sector, geography and status (active/exited). Set group_by to count instead of list, e.g. answers 'how many French healthcare companies were PE-backed in 2024 across all firms'. Buyer names and MOIC are included.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Company geography filter, e.g. 'France' (exact, case-insensitive) |
| gp | string | – | Optional: restrict to one PE firm by name |
| group_by | string | – | Return counts grouped by this dimension instead of a list of deals |
| limit | integer | – | Page size for list mode (max 50) |
| offset | integer | – | Pagination offset for list mode |
| sector | string | – | Sector filter, e.g. 'Healthcare' (exact, case-insensitive) |
| status | string | – | Filter: only active holdings or only exited positions |
| year | integer | – | Exact entry year, e.g. 2024 |
| year_from | integer | – | Entry year range start (ignored if year is set) |
| year_to | integer | – | Entry year range end (ignored if year is set) |
No output schema declared.
No examples provided.
search_exits Search PE exits across all firms ~320
Cross-firm exit search the per-firm tools cannot do: filter REALISED exits across ALL European PE firms by year (or range), exit route, sector and geography. Set group_by to count instead of list, e.g. group_by='exit_type' with year=2026 answers 'how many continuation-vehicle exits in 2026 across Europe'. exit_type 'Continuation Vehicle' covers continuation funds, strip sales and GP-led tender offers. Buyer names and MOIC are included.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | – | Filter exits to a specific buyer (acquirer), e.g. 'RadNet'. |
| exit_type | string | – | Exit route. 'Continuation Vehicle' = continuation funds / strip sales / GP-led tender offers |
| geo | string | – | Company geography filter, e.g. 'France' (exact, case-insensitive) |
| gp | string | – | Optional: restrict to one PE firm by name |
| group_by | string | – | Return counts grouped by this dimension instead of a list of exits |
| limit | integer | – | Page size for list mode (max 50) |
| offset | integer | – | Pagination offset for list mode |
| sector | string | – | Sector filter, e.g. 'Healthcare' (exact, case-insensitive) |
| year | integer | – | Exact exit year, e.g. 2026 |
| year_from | integer | – | Exit year range start (ignored if year is set) |
| year_to | integer | – | Exit year range end (ignored if year is set) |
No output schema declared.
No examples provided.
search_gps Search PE firms ~57
Search the 1,200+ European private equity firms (GPs) tracked on GP Intel by name. Returns country, AUM and strategies.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | GP name or fragment |
No output schema declared.
No examples provided.
who_owns Who owns a company ~99
Find who owns a company: its current private equity owner(s) and the full ownership history (entry years, exits with year and route). Covers 34,000+ companies held by European PE firms, hand-verified. Use for questions like 'who owns X' or 'X parent company'.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or gp-intel.com company slug, e.g. 'Bark.com' or 'bark-com' |
No output schema declared.
No examples provided.
How do I install the GP Intel MCP server?
GP Intel is a hosted endpoint at https://www.gp-intel.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.gp-intel.com
claude mcp add --transport http gparientee-gp-intel 'https://www.gp-intel.com/api/mcp'
What is the GP Intel MCP server?
GP Intel is an MCP server listed in the public MCP registry as io.github.gparientee/gp-intel. Verified European PE ownership: who owns a company, GP portfolios, exits by year. Hand-checked. This page covers its hosted endpoint (https://www.gp-intel.com/api/mcp).
Is the GP Intel MCP server safe to use?
GP Intel scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GP Intel MCP server expose?
GP Intel exposes 7 tools: who_owns, gp_portfolio, gp_exits, search_companies, search_gps, and 2 more. Their descriptions and schemas cost roughly 951 tokens of context every time the server is loaded.
Does the GP Intel MCP server require authentication?
Its publisher declares no required credentials for GP Intel. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the GP Intel MCP server still maintained?
GP Intel is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the GP Intel MCP server?
VerifyMCP ran 5 checks on GP Intel, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about GP Intel: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.