Resources Reference

MCP resources are read-only JSON snapshots the server exposes over a URI scheme. Agents load them to ground themselves before running tool calls — reading the ability catalog, for example, lets an agent propose the minimum-privilege token to mint for a given task.

URI scheme

Every resource URI starts with subscriby://. Seven resources are published:

URI	Contents
`subscriby://connectors/catalog`	The Connectors Marketplace: every connector in its lane, its badges, manifest and connect form.
`subscriby://enums/ability`	The full Sanctum ability catalog, grouped by domain.
`subscriby://enums/error-code`	Every error code with HTTP status, default message, remediation hint, and `docs_url` anchor.
`subscriby://enums/payment-provider`	Every payment provider key: the gateway slugs, access codes, one `connector:provider` key per currency a registered connector brings (each with `connector` and `requires_connector`), and `platformcurrency` flagged `legacy_alias`.
`subscriby://enums/subscription-status`	The canonical subscription statuses with human label and UI colour family.
`subscriby://enums/webhook-event`	The outbound webhook catalog with the minimum subscribing-creator ability for each event.

Why load them

An agent that knows the enum universe before making calls will:

Avoid proposing a status that does not exist ("is the subscription in 'dormant' state?" when dormant is not a value).
Pattern-match error codes to remediation hints without a docs round-trip.
Pre-filter webhook events when registering an endpoint via the REST POST /v1/webhook-endpoints endpoint.
Mint minimum-privilege follow-up tokens by reading the ability catalog.
Propose a connector a creator can actually install today, and render its connect form from the declared fields, by reading the connector catalog.

Example — Claude Desktop

Reference a resource in a prompt:

Load subscriby://enums/subscription-status and explain the difference between unpaid and past_due.

Claude fetches the resource, parses the JSON, and answers without calling any tools.

Payload shape

There is no shared envelope. Each resource returns JSON keyed by its own collection name, with whatever counts are meaningful for it — and none of them carry a version field.

Resource	Top-level keys
`subscriby://connectors/catalog`	`connectors[]`, `total`
`subscriby://enums/ability`	`abilities[]`, `core_count`, `extras_count`, `total`
`subscriby://enums/error-code`	`error_codes[]`
`subscriby://enums/payment-provider`	`payment_providers[]`
`subscriby://enums/subscription-status`	`subscription_statuses[]`
`subscriby://enums/webhook-event`	`webhook_events[]`, `families[]`

{
  "abilities": [
    {
      "value": "project:view-any",
      "category": "project",
      "label": "View Any Project"
    }
  ],
  "core_count": 50,
  "extras_count": 25,
  "total": 75
}

The { version, count, items[] } envelope belongs to the HTTP manifests at api.subscriby.net/*.json, not to these MCP resources. If you are switching an agent between the two sources, the shapes differ.

Prompts

The MCP server does not publish any prompts today — the full surface is tools plus the seven resources above.