Phoenix by HG Insights

Query B2B technographic, firmographic, intent and federal contracting data.

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

What the Phoenix by HG Insights connector does

The Phoenix MCP server connects HG Insights' B2B intelligence platform to Claude, ChatGPT and any MCP-compatible agent. It answers questions about what technology a company runs, what it spends, which buying signals it shows and which federal contracts it holds. Anthropic lists 15 tools; HG Insights documents 43. Sign-in is OAuth 2.1 or an API key.

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.

Phoenix by HG Insights tools (15)

  • company_technographic
  • company_firmographic
  • company_search
  • company_intent
  • company_spend
  • company_cloud_spend
  • company_contracts
  • company_fai
  • company_operating_signals
  • company_install_time_series
  • company_gov_opportunities
  • company_gov_relationships
  • contact_search
  • contact_enrich
  • web_search

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Anthropic's tool list is 28 names short and one name wrong. The directory's 15 omit the warehouse, SEC, product-research, agent-invocation and administrative families entirely, and its company_search matches nothing in the vendor's authoritative lists.
  • The tool surface is per-key and cannot be enumerated from outside. Admin tools are hidden from tools/list for user-scoped keys, and several families appear only when the matching integration is configured. Two tools — get_product_information and get_product_reviews — are composed dynamically by an aggregator and exist only when TrustRadius is connected.
  • HG Insights' own two lists disagree by ten names. Its narrative catalog says 29 native tools plus 2 aggregated; its generated billing table names 43. We treat the generated table as authoritative because it is produced from the billing schedule.
  • The documented rate limit is stated twice, inconsistently. The tools overview says 1,000 tool calls per minute per API key; the admin documentation says all admin endpoints share a 500-per-minute limit. Both pages were live on 2026-08-22. Assume the lower figure.
  • Most tools cost credits, and some cost per result. hg_data_query bills 1 credit per row returned and company_install_time_series 3 per product, so an unbounded query is an unbounded bill. company_research and hg_query have no flat rate at all and are metered separately.
  • The licence forbids system-of-record use. HG Insights states MCP data is licensed for agentic workflows and not for populating a CRM, MDM or data warehouse on a schedule or per record.
  • Personal email addresses cannot sign up. A corporate domain is required.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so parameter-level detail here comes from HG Insights' documentation rather than from the wire.
  • Contract data is narrower than the tool name suggests. HG Insights warns that company_contracts returns ICT contracts outsourced through global system integrators, not individual product contracts or vendor renewal dates.
  • Responses are cached, so freshness lags. HG Insights documents 1 hour for company data, 24 hours for product catalogs and 15 minutes for search results.

Frequently asked questions

How many tools does the Phoenix MCP server actually have?

Far more than the 15 Anthropic lists. HG Insights publishes a generated billing table naming 43 tools on 2026-08-22, and a separate admin family of nine on top of that. The directory entry is a stale subset that omits SQL warehouse queries, SEC filings, product research, agent invocation and every administrative operation.

Can the Phoenix connector send email to someone?

Yes, with an admin-scoped key. HG Insights documents admin_invite_user as sending a SendGrid magic-link invitation to any address you name, and it writes an audit row on success. That tool is absent from Anthropic's 15, so a reader working from the directory listing alone would conclude the connector has no outbound path.

What OAuth scopes does the Phoenix MCP server request?

Three, and they draw a real line. The server's own RFC 9728 descriptor advertised mcp:read, mcp:tools and offline_access on 2026-08-22. Reading company data and executing tools are separable at consent, which is more boundary than most connectors offer. Admin privilege is not among them — it rides on the API key instead.

Why does the directory list company_search when the docs call it search_companies?

Because the directory carries a stale name. HG Insights uses search_companies in its tool catalog, its category lists and its generated credit table. The old company_search survives only in older example snippets on the same site. Nothing in the vendor's authoritative lists matches the directory's spelling, so treat it as a rename the listing missed.

Do I need a paid Phoenix account to use the MCP server?

Yes, and a corporate email address. HG Insights states Phoenix requires a work address at signup and rejects Gmail, Outlook, Yahoo and similar personal domains, because it configures your workspace from the company domain. Tool calls then consume AI Credits on a published per-tool schedule, and several tools additionally require a paid integration.

Which Phoenix tools cost the most credits per call?

The per-result ones, not the flat-rate ones. HG Insights bills company_install_time_series at 3 credits per product returned, hg_data_query at 1 credit per row, and contact_enrich at 2 per revealed phone number. A warehouse query returning ten thousand rows therefore costs ten thousand credits, so bound your queries before running them.

Can Phoenix write data back into my CRM or data warehouse?

No, and HG Insights forbids it by licence. Its documentation states MCP data is licensed for agentic workflows only and is not licensed for populating or maintaining a system of record. Scheduled or per-record writes into a CRM, MDM or warehouse must go through the HG Insights API or SaaS application instead.

Does connecting Snowflake give Phoenix write access to my data?

Not if you follow the documented setup. HG Insights recommends a dedicated Snowflake service user granted only USAGE and SELECT, and its two customer-data tools are named explore and query. Read-only is a privilege you grant in Snowflake, though, not something the connector enforces for you.

Sources

Use it in an agent

Put Phoenix by HG Insights to work.

Connect Phoenix by HG Insights once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.