Is the Centrify Internal HubSpot Integrations MCP server down?

mcp-registry/io.github.centrify-internal/hubspot-integrations-mcp · v1.0.0

healthy
Last checked 2026-10-22 11:34 UTC · handshake 100ms

As of 2026-10-22 11:34 UTC, the Centrify Internal HubSpot Integrations MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 15 minutes.

uptime (30d checks)
100%
checks observed
4,286
outages (90d)
1
tools
2

MCP server for the HubSpot Integrations Center HubDB: search and retrieve integration data.

Install Centrify Internal HubSpot Integrations MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http centrify-internal-hubspot-integrations-m https://n6k96b1ql7.execute-api.us-west-2.amazonaws.com/prod/

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "centrify-internal-hubspot-integrations-m": {
      "type": "http",
      "url": "https://n6k96b1ql7.execute-api.us-west-2.amazonaws.com/prod/"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 2 tool(s); ~235 tokens of tool definitions.
Scores higher than 38% of 15,515 MCP servers Glimind has audited.
Its tool list costs an agent ~235 tokens per session — lighter than 99% of servers.
82 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (3)

2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_integration, search_integration

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.centrify-internal%2Fhubspot-integrations-mcp/fixes

get_integration 1 change
{
  "name": "get_integration",
  "description": "Retrieve a specific integration by its ID from the HubSpot Integrations Center. Returns the full integration details including title, summary, body, URL, categories, and last updated date.",
  "inputSchema": {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The integration ID to retrieve (format: display-name-product-name)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
search_integration 1 change
{
  "name": "search_integration",
  "description": "Search for integrations in the HubSpot Integrations Center by query string. Returns matching integrations with their details including title, summary, body, URL, categories, and last updated date.",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Search query to find integrations. Searches across title, summary, body, and categories."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.centrify-internal/hubspot-integrations-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.centrify-internal/hubspot-integrations-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.centrify-internal%2Fhubspot-integrations-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.centrify-internal%2Fhubspot-integrations-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.centrify-internal%2Fhubspot-integrations-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.centrify-internal%2Fhubspot-integrations-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.centrify-internal%2Fhubspot-integrations-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.centrify-internal%2Fhubspot-integrations-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b2b621624debfe9f…, first seen 2026-10-17, included at leaf 4230 of 45,678. Version history · verify what your client received.

Tools (2)

Compare: most reliable knowledge servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Centrify Internal HubSpot Integrations MCP server down right now?

As of 2026-10-22 11:34 UTC, the Centrify Internal HubSpot Integrations MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 15 minutes.

How many tools does Centrify Internal HubSpot Integrations MCP server provide?

Centrify Internal HubSpot Integrations MCP server advertises 2 tools, including get_integration, search_integration.

How do I install Centrify Internal HubSpot Integrations MCP server?

Point your MCP client at this streamable-http endpoint: https://n6k96b1ql7.execute-api.us-west-2.amazonaws.com/prod/

Is the Centrify Internal HubSpot Integrations MCP server safe to connect to an AI agent?

Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Centrify Internal HubSpot Integrations MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve