HookPulse

HookPulse MCP API

The Mcp API from HookPulse — 1 operation(s) for mcp.

Documentation GitHub OpenAPI

Operations 1

POST /mcp MCP server over HTTP (Streamable HTTP, JSON-RPC 2.0) — plugs into the client… #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/hookpulse-mcp-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: HookPulse MCP API
  version: 2d690e87
  description: 'Dead-man switch for webhooks/cron. Index: GET /api/.'
servers:
- url: https://hookpulse.net
tags:
- name: MCP
paths:
  /mcp:
    post:
      operationId: post_mcp
      summary: MCP server over HTTP (Streamable HTTP, JSON-RPC 2.0) — plugs into the client…
      description: 'The tools are the operations of this same catalog; the MCP has no backend of its own. `GET /mcp` returns the server card.

        Returns: JSON-RPC 2.0 response (`initialize`, `tools/list` or `tools/call`).

        Credentials go in the usual headers (X-Guest-Token, Authorization, X-PAYMENT) and are forwarded to the API.

        An exhausted quota comes back as a 402 with accepts[] inside the tool result — pay and repeat.'
      security: []
      responses:
        '200':
          description: JSON-RPC 2.0 response (`initialize`, `tools/list` or `tools/call`).
      tags:
      - MCP
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: 'Guest token (`POST /api/guest`) in `X-Guest-Token: hp_…` or `Authorization: Bearer hp_…`. A `sess_…` session also works.'