hyperping 1.4.0__tar.gz → 1.4.1__tar.gz

{hyperping-1.4.0 → hyperping-1.4.1}/CHANGELOG.md

@@ -5,6 +5,87 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.4.1] - 2026-04-20
+
+### Fixed
+
+- HTTP 403 from MCP server now correctly raises `HyperpingAuthError` (was
+  `HyperpingAPIError`). The Hyperping MCP server returns 403 for invalid API keys;
+  the transport only handled 401. Now matches REST client behavior.
+- `MCP_URL` defined in single location (`endpoints.py`); removed duplicate in
+  `_mcp_transport.py`.
+- MCP handshake version string uses `__version__` instead of hardcoded `"1.4.0"`.
+
+## [1.4.0] - 2026-04-19
+
+### Added
+
+- **`HyperpingMcpClient`** -- new client for Hyperping MCP server features not available
+  via the REST API. Uses JSON-RPC 2.0 over HTTP at `/v1/mcp` with the same Bearer token
+  API key. Provides 16 typed methods: `get_status_summary`, `get_monitor_response_time`,
+  `get_monitor_mtta`, `get_monitor_mttr`, `get_monitor_anomalies`, `get_monitor_http_logs`,
+  `list_recent_alerts`, `list_on_call_schedules`, `get_on_call_schedule`,
+  `list_escalation_policies`, `get_escalation_policy`, `list_team_members`,
+  `list_integrations`, `get_integration`, `get_outage_timeline`, `search_monitors_by_name`.
+- **`McpTransport`** -- low-level JSON-RPC 2.0 transport with auto-initialization handshake,
+  double-parse response extraction, and error mapping to existing SDK exception types.
+- **`MCP_URL`** constant exported from `hyperping` top-level.
+- **Sync outage methods** -- `create_outage`, `delete_outage`, `get_outage`,
+  `unacknowledge_outage` added to `OutagesMixin` (were only in async client).
+- **Verification script** -- `scripts/verify_endpoints.py` for testing endpoints against
+  the live API.
+
+### Changed
+
+- **Maintenance update** uses `model_dump(include=...)` instead of hard-coded field list.
+- **Incident update error handling** -- `add_incident_update` now provides context when
+  the POST succeeds but the follow-up GET fails.
+
+### Removed
+
+- **Speculative REST methods** -- 12 methods that called nonexistent REST endpoints
+  (on-call, alerts, anomalies, integrations, probe logs, response time, MTTA, status
+  summary, outage timeline, monitor search) removed from `HyperpingClient` and
+  `AsyncHyperpingClient`. These features are MCP-only; use `HyperpingMcpClient` instead.
+- **8 speculative mixin files** (sync + async) deleted.
+- **8 speculative Endpoint enum entries** removed from `endpoints.py`.
+
+### Fixed
+
+- HTTP 403 from MCP server now correctly raises `HyperpingAuthError` (was
+  `HyperpingAPIError`). Matches REST client behavior.
+- `MCP_URL` defined in single location (`endpoints.py`), not duplicated.
+- MCP handshake version uses `__version__` instead of hardcoded string.
+- `pytest` bumped to 9.0.3 (CVE-2025-71176).
+
+## [1.3.0] - 2026-04-18 [YANKED]
+
+v1.3.0 added 18 speculative REST methods for MCP-discovered features (reporting,
+observability, on-call, integrations). All 12 endpoint paths were guessed from MCP
+tool names and **none of them work via the REST API** (verified: 10x 404, 2x 401).
+These features are only accessible through the MCP server (JSON-RPC 2.0). Superseded
+by v1.4.0 which replaces the broken REST methods with a proper `HyperpingMcpClient`.
+
+## [1.2.1] - 2026-04-17
+
+### Fixed
+
+- Bump `pytest` to 9.0.3 (CVE-2025-71176).
+
+## [1.2.0] - 2026-04-17
+
+### Added
+
+- **Sync outage methods** -- `create_outage`, `delete_outage`, `get_outage`,
+  `unacknowledge_outage` added to `OutagesMixin` for feature parity with async client.
+
+### Changed
+
+- **Maintenance update** uses `model_dump(include=...)` instead of hard-coded field
+  enumeration for robustness.
+- **Incident update error handling** -- `add_incident_update` now provides context when
+  the POST succeeds but the follow-up GET fails.
+
 ## [1.1.0] - 2026-04-09
 
 ### Added
@@ -30,6 +111,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **`collect_all_pages` / `collect_all_pages_async`** helpers in `_utils.py` for
   transparent multi-page result aggregation.
 
+## [1.0.1] - 2026-04-05
+
+### Fixed
+
+- Fix version string in `pyproject.toml` (was out of sync with `_version.py`).
+- Fix package metadata: incorrect email address in project config.
+
 ## [1.0.0] - 2026-04-05
 
 First stable release. The public API is production-ready and covered by semver

{hyperping-1.4.0 → hyperping-1.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hyperping
-Version: 1.4.0
+Version: 1.4.1
 Summary: Python SDK for the Hyperping uptime monitoring and incident management API
 Project-URL: Homepage, https://github.com/develeap/hyperping-python
 Project-URL: Documentation, https://github.com/develeap/hyperping-python#readme
@@ -181,6 +181,43 @@ sub  = client.add_subscriber("sp_uuid", "user@example.com")
 client.remove_subscriber("sp_uuid", sub.id)
 ```
 
+### MCP Client (on-call, alerts, anomalies, integrations)
+
+Some Hyperping features are only available via the MCP server (JSON-RPC 2.0),
+not the REST API. Use `HyperpingMcpClient` for these:
+
+```python
+from hyperping import HyperpingMcpClient
+
+with HyperpingMcpClient(api_key="sk_...") as mcp:
+    # Status & reporting
+    summary = mcp.get_status_summary()
+    mtta = mcp.get_monitor_mtta("mon_uuid")
+    mttr = mcp.get_monitor_mttr("mon_uuid")
+    response_time = mcp.get_monitor_response_time("mon_uuid")
+
+    # On-call & escalation
+    schedules = mcp.list_on_call_schedules()
+    policies = mcp.list_escalation_policies()
+    members = mcp.list_team_members()
+
+    # Observability
+    anomalies = mcp.get_monitor_anomalies("mon_uuid")
+    logs = mcp.get_monitor_http_logs("mon_uuid")
+    alerts = mcp.list_recent_alerts()
+
+    # Integrations
+    integrations = mcp.list_integrations()
+
+    # Outage timeline & monitor search
+    timeline = mcp.get_outage_timeline("out_uuid")
+    results = mcp.search_monitors_by_name("api")
+```
+
+The MCP client uses the same API key as `HyperpingClient`. All methods return
+plain dicts/lists; use the exported Pydantic models (e.g., `OnCallSchedule`,
+`EscalationPolicy`) for validation if needed.
+
 ### Healthchecks
 
 ```python

{hyperping-1.4.0 → hyperping-1.4.1}/README.md

@@ -144,6 +144,43 @@ sub  = client.add_subscriber("sp_uuid", "user@example.com")
 client.remove_subscriber("sp_uuid", sub.id)
 ```
 
+### MCP Client (on-call, alerts, anomalies, integrations)
+
+Some Hyperping features are only available via the MCP server (JSON-RPC 2.0),
+not the REST API. Use `HyperpingMcpClient` for these:
+
+```python
+from hyperping import HyperpingMcpClient
+
+with HyperpingMcpClient(api_key="sk_...") as mcp:
+    # Status & reporting
+    summary = mcp.get_status_summary()
+    mtta = mcp.get_monitor_mtta("mon_uuid")
+    mttr = mcp.get_monitor_mttr("mon_uuid")
+    response_time = mcp.get_monitor_response_time("mon_uuid")
+
+    # On-call & escalation
+    schedules = mcp.list_on_call_schedules()
+    policies = mcp.list_escalation_policies()
+    members = mcp.list_team_members()
+
+    # Observability
+    anomalies = mcp.get_monitor_anomalies("mon_uuid")
+    logs = mcp.get_monitor_http_logs("mon_uuid")
+    alerts = mcp.list_recent_alerts()
+
+    # Integrations
+    integrations = mcp.list_integrations()
+
+    # Outage timeline & monitor search
+    timeline = mcp.get_outage_timeline("out_uuid")
+    results = mcp.search_monitors_by_name("api")
+```
+
+The MCP client uses the same API key as `HyperpingClient`. All methods return
+plain dicts/lists; use the exported Pydantic models (e.g., `OnCallSchedule`,
+`EscalationPolicy`) for validation if needed.
+
 ### Healthchecks
 
 ```python

{hyperping-1.4.0 → hyperping-1.4.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "hyperping"
-version = "1.4.0"
+version = "1.4.1"
 description = "Python SDK for the Hyperping uptime monitoring and incident management API"
 readme = {file = "README.md", content-type = "text/markdown"}
 license = {text = "MIT"}

{hyperping-1.4.0 → hyperping-1.4.1}/src/hyperping/__init__.py

@@ -15,7 +15,6 @@ Quick start::
 """
 
 from hyperping._async_client import AsyncHyperpingClient
-from hyperping._mcp_transport import MCP_URL
 from hyperping._version import __version__
 from hyperping.client import (
     CircuitBreaker,
@@ -26,6 +25,7 @@ from hyperping.client import (
 )
 from hyperping.endpoints import (
     API_BASE,
+    MCP_URL,
     APIVersion,
     Endpoint,
 )

{hyperping-1.4.0 → hyperping-1.4.1}/src/hyperping/_mcp_transport.py

@@ -8,9 +8,10 @@ from typing import Any
 import httpx
 from pydantic import SecretStr
 
+from hyperping._version import __version__
+from hyperping.endpoints import MCP_URL
 from hyperping.exceptions import HyperpingAPIError, HyperpingAuthError
 
-MCP_URL = "https://api.hyperping.io/v1/mcp"
 _PROTOCOL_VERSION = "2025-03-26"
 
 
@@ -61,7 +62,7 @@ class McpTransport:
 
         resp = self._client.post(self._url, content=json.dumps(payload))
 
-        if resp.status_code == 401:
+        if resp.status_code in (401, 403):
             raise HyperpingAuthError("Invalid or expired API key")
         if resp.status_code == 202:
             return None  # Notification accepted
@@ -91,7 +92,7 @@ class McpTransport:
             {
                 "protocolVersion": _PROTOCOL_VERSION,
                 "capabilities": {},
-                "clientInfo": {"name": "hyperping-python", "version": "1.4.0"},
+                "clientInfo": {"name": "hyperping-python", "version": __version__},
             },
         )
         self._send_rpc("notifications/initialized", is_notification=True)

hyperping-1.4.1/src/hyperping/_version.py

@@ -0,0 +1 @@
+__version__ = "1.4.1"

{hyperping-1.4.0 → hyperping-1.4.1}/src/hyperping/mcp_client.py

@@ -18,7 +18,8 @@ from typing import Any
 
 from pydantic import SecretStr
 
-from hyperping._mcp_transport import MCP_URL, McpTransport
+from hyperping._mcp_transport import McpTransport
+from hyperping.endpoints import MCP_URL
 
 
 class HyperpingMcpClient:

{hyperping-1.4.0 → hyperping-1.4.1}/tests/unit/test_mcp_transport.py

@@ -76,6 +76,17 @@ def test_call_tool_http_401():
     transport.close()
 
 
+@respx.mock
+def test_call_tool_http_403():
+    """MCP server returns 403 (not 401) for invalid API keys."""
+    respx.post(MCP_URL).mock(return_value=httpx.Response(403, text="Forbidden"))
+    transport = McpTransport(api_key="sk_bad", base_url=MCP_URL)
+    transport._initialized = True
+    with pytest.raises(HyperpingAuthError):
+        transport.call_tool("list_team_members")
+    transport.close()
+
+
 @respx.mock
 def test_call_tool_jsonrpc_error():
     respx.post(MCP_URL).mock(

hyperping-1.4.0/src/hyperping/_version.py

@@ -1 +0,0 @@
-__version__ = "1.4.0"