FastDrop Health API

openapi: 3.2.0
info:
  title: FastDrop Health API
  version: 1.3.0
  description: 'FastDrop is the liveness layer for agent-ready software: the official MCP Registry authenticates who published a server, FastDrop probes whether it still answers, and publishes the tools each endpoint actually returned.


    Three surfaces, one API:

    - `POST /mcp` - a Streamable HTTP MCP server (JSON-RPC 2.0). Read tools (list_launches, get_engagement_feed, get_product, get_maker, search_products, find_tools, list_reviews, list_comments, get_launch_day_status, get_install_config, find_alternatives, compare_products, find_deals) are unauthenticated; write tools (submit_product, update_product, toggle_vote, post_review, post_comment, recheck_mcp, check_submission_status, invite_collaborator, get_my_stats, get_inbox, mark_notifications_read, get_launch_kit, follow, list_following, list_webhooks, create_webhook, delete_webhook, test_webhook, update_profile, set_deal, set_open_to) require a Bearer token. Prompts (prompts/list, prompts/get): launch_my_product, daily_engagement, find_tools_for, launch_report.

    - `GET /v0.1/servers` - an MCP Registry-compatible subregistry (OpenAPI shape) with a `dev.fastdrop/verification` liveness block in `_meta`. Unauthenticated, cursor-paginated.


    When to use this API: discover agent-ready products by probed capability (not marketing tags), check whether an MCP endpoint currently answers, submit or update your own listing programmatically, and poll submission status. When NOT to use it: identity verification of server publishers (that is the official registry at registry.modelcontextprotocol.io) and human browsing (use the website).


    Agent resources: llms.txt at /llms.txt (complete reference at /llms-full.txt), developer docs at /developers, sitemap at /sitemap.xml, MCP server manifest at /.well-known/mcp.'
  contact:
    name: FastDrop
    url: https://fastdrop.dev/contact
    email: privacy@fastdrop.dev
servers:
- url: https://fastdrop.dev
  description: Production
tags:
- name: Health
  description: Liveness probes for the API itself
paths:
  /v0.1/health:
    get:
      tags:
      - Health
      operationId: getSubregistryHealth
      summary: Subregistry liveness probe
      description: Static ok/no-store probe in the official registry shape. Unauthenticated.
      responses:
        '200':
          description: Subregistry is up
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                    - ok
                required:
                - status
  /health:
    get:
      tags:
      - Health
      operationId: getHealth
      summary: Service health including database reachability
      description: Reports ok only when the process answers and PostgreSQL responds to SELECT 1. 503 when degraded.
      responses:
        '200':
          description: Healthy
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                    - ok
                  db:
                    type: string
                    enum:
                    - ok
                  timestamp:
                    type: string
                    format: date-time
                required:
                - status
                - db
                - timestamp
        '503':
          description: Degraded (database unreachable)
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                    - degraded
                  db:
                    type: string
                    enum:
                    - error
                  timestamp:
                    type: string
                    format: date-time
                required:
                - status
                - db
                - timestamp
components:
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: fd_
      description: FastDrop API key (starts with fd_). Create one in the dashboard at /app/developer (Developer tab). Grants read access plus write access to your own submissions, votes, reviews, and comments over /mcp. Revoke any time; no scope narrowing on keys - prefer OAuth when a client only needs MCP access.
    FastDropOAuth:
      type: oauth2
      description: OAuth 2 for MCP clients (RFC 8414 metadata at /.well-known/oauth-authorization-server, protected-resource metadata at /.well-known/oauth-protected-resource/mcp). Public clients supported (empty client secret on the token endpoint).
      flows:
        authorizationCode:
          authorizationUrl: https://fastdrop.dev/api/auth/oauth2/authorize
          tokenUrl: https://fastdrop.dev/api/auth/oauth2/token
          refreshUrl: https://fastdrop.dev/api/auth/oauth2/token
          scopes:
            mcp: Call the FastDrop MCP server (/mcp) on behalf of the signed-in user. Read tools plus their own submissions, votes, reviews, and comments - nothing else.
            offline_access: Receive refresh tokens so a long-lived agent session can renew access without re-consent.
externalDocs:
  description: FastDrop developer documentation
  url: https://fastdrop.dev/developers