Heartpingr
Pricing
$1.00 / 1,000 heartbeats
Heartpingr
Heartpingr is a heartbeat monitoring API for developers. Easily track service pings AI token-based usage metrics over time. The API reports real-time usage counts and provides alerting mechanisms to prevent billing overages from your cloud provider, AI integration, or other expensive 3rd parties.
0.0 (0)
Pricing
$1.00 / 1,000 heartbeats
0
Total users
1
Monthly users
1
Runs succeeded
>99%
Last modified
7 hours ago
You can access the Heartpingr programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
{ "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/sse?actors=maplerope44/heartpingr", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Configure MCP server with Heartpingr
You have a few options for interacting with the MCP server:
Use
mcp.apify.comviamcp-remotefrom your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).Set up the connection directly in your MCP client UI by providing the URL
https://mcp.apify.com/sse?actors=maplerope44/heartpingralong with an API token (or use OAuth).Connect to
mcp.apify.comvia Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=maplerope44/heartpingr", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.
