Is the HubSpot MCP server down?
No. On 2026-11-02 14:02 PT, mcp.hubspot.com answered StackMCP's check with an auth challenge (HTTP 401) in 140 ms. That is the normal healthy response. 22 checks since Oct 15 were up.
- Status
- Up · auth
- HTTP
- 401
- Latency
- 140 ms
- Last check
- 2026-11-02 14:02 PT
- Uptime
- 100% (22 of 22)
- Transport
- Streamable HTTP
- Auth
- OAuth 2.1 with PKCE (MCP connector)
- Endpoint
https://mcp.hubspot.com
Get the weekly email
New MCP servers, auth changes and breakages. One email a week. This form does not send a separate alert for one tool.
What we checked
The scheduled check runs once a day, with no credentials and no API key. This log has 23 runs on 19 days, and 4 of those days have more than one run. Each run sends one MCP initialize request. HTTP 401 with an auth challenge means the server is up and wants a sign-in. That result is labeled Up · auth. HTTP 200 means the server answered without asking for a sign-in. A timeout, a 5xx response, or a 404 is a problem. Another code is labeled Unknown, because the check could not tell. The check only shows that the MCP endpoint answered. It does not show that HubSpot's app is working.
Bearer resource_metadata="https://mcp.hubspot.com/.well-known/oauth-protected-resource"
Resource metadata: https://mcp.hubspot.com/.well-known/oauth-protected-resourceLast 22 checks
22 stored checks, newest first. Times are Pacific Time.
| Checked | HTTP | ms | Result |
|---|---|---|---|
| 2026-11-02 14:02 PT | 401 | 140 | Up · auth |
| 2026-11-01 10:13 PT | 401 | 89 | Up · auth |
| 2026-10-31 10:28 PT | 401 | 100 | Up · auth |
| 2026-10-30 11:22 PT | 401 | 188 | Up · auth |
| 2026-10-29 11:45 PT | 401 | 160 | Up · auth |
| 2026-10-28 11:36 PT | 401 | 162 | Up · auth |
| 2026-10-27 11:30 PT | 401 | 170 | Up · auth |
| 2026-10-26 11:58 PT | 401 | 159 | Up · auth |
| 2026-10-25 09:55 PT | 401 | 174 | Up · auth |
| 2026-10-24 09:23 PT | 401 | 152 | Up · auth |
| 2026-10-23 10:38 PT | 401 | 88 | Up · auth |
| 2026-10-22 10:46 PT | 401 | 170 | Up · auth |
| 2026-10-21 10:48 PT | 401 | 177 | Up · auth |
| 2026-10-20 10:39 PT | 401 | 374 | Up · auth |
| 2026-10-19 11:56 PT | 401 | 145 | Up · auth |
| 2026-10-18 22:45 PT | 401 | 135 | Up · auth |
| 2026-10-18 09:15 PT | 401 | 65 | Up · auth |
| 2026-10-17 09:03 PT | 401 | 100 | Up · auth |
| 2026-10-16 10:06 PT | 401 | 173 | Up · auth |
| 2026-10-16 06:06 PT | 401 | 80 | Up · auth |
| 2026-10-15 23:24 PT | 401 | 114 | Up · auth |
| 2026-10-15 20:56 PT | 401 | 82 | Up · auth |
Last change
Up · auth since Oct 15. No later status change is stored.
Newest changelog entry for HubSpot, 2026-11-02: HubSpot plan line matches the help article.
Is HubSpot itself down?
HubSpot publishes its own status page: HubSpot Status. Checked 2026-11-02.
Our check only shows that the MCP endpoint answers. If HubSpot's app is down, your connector can fail even when this page says up.
Up here but your HubSpot connector still fails?
- Calls, emails, or notes are missing. Check whether Sensitive Data is on. If it is, those activity objects are blocked unless a Super Admin allows the public beta. Even then, the remote server can only read engagements. See the HubSpot page.
- Write tools never show up. HubSpot's Claude article says you need to disconnect and sign in again to get write access. The April 13 changelog says the same when new scopes appear. See the HubSpot page.
- HubSpot is not in the connector list. A Super Admin has to approve it first, unless you are a Super Admin or you have App Marketplace Access. See the HubSpot page.
- A custom client fails at sign-in. HubSpot requires PKCE, and the redirect URL in the client has to match the MCP connector. See the HubSpot page.
MCP status for other tools
- Is the Salesforce MCP server down?
- Is the Pipedrive MCP server down?
- Is the Gong MCP server down?
- Is the Stripe MCP server down?
- Is the Perplexity MCP server down?
- Is the Zapier MCP server down?
- All endpoint status
FAQ
Is the HubSpot MCP server down?
No. On 2026-11-02 14:02 PT, mcp.hubspot.com answered StackMCP's check with an auth challenge (HTTP 401) in 140 ms. That is the normal healthy response. 22 checks since Oct 15 were up.
What does "Up · auth" or HTTP 401 mean on an MCP status check?
It means the server is up. MCP servers that use OAuth answer an unauthenticated request with 401 and a pointer to their sign-in metadata, so a 401 with an auth challenge is the expected healthy response. It is not an error. A timeout, a 5xx error, or a 404 is what signals a problem. The check only proves the HubSpot MCP endpoint answers. It does not prove HubSpot's app is working, so also check the vendor status page when one is linked here. The check method is on the About page.
The HubSpot MCP server is up, but my connector won't work. What should I check?
Calls, emails, or notes are missing. Check whether Sensitive Data is on. If it is, those activity objects are blocked unless a Super Admin allows the public beta. Even then, the remote server can only read engagements. Write tools never show up. HubSpot's Claude article says you need to disconnect and sign in again to get write access. The April 13 changelog says the same when new scopes appear. HubSpot is not in the connector list. A Super Admin has to approve it first, unless you are a Super Admin or you have App Marketplace Access. A custom client fails at sign-in. HubSpot requires PKCE, and the redirect URL in the client has to match the MCP connector.
Get the weekly email
New MCP servers, auth changes and breakages. One email a week. This form does not send a separate alert for one tool.
The scheduled check runs once a day. The count above is every stored check, not one check per day. No credentials are sent. The runner region is not published. The method is on the About page. Setup: HubSpot.