MCP App coverage, with the counting method included

Use the data to compare App availability and access requirements, or cite the snapshot in your own evaluation.

What does this dataset cover?

The 2026-10-20 snapshot contains 116 reviewed Stackyapper App listings: 25 with Available status and 91 with Beta status. Each row describes one named integration, its category, availability, review stage and access metadata. These are Stackyapper catalog records, not a survey of the MCP market or a count of every provider API operation.

The wider App directory includes 5,200+ discovery listings across OpenAPI, MCP, CLI and GraphQL. Those listings and customer-created private apps are outside this dataset. The two counts describe different populations and should not be added together.

Download and inspect the data

Both downloads are free to access without an account. They describe the same snapshot. Follow each row’s canonical App URL for current setup requirements and supported operations.

How the counts are produced

  1. Start with Stackyapper’s published, reviewed App catalog. Count each unique App key once, including separate integrations for the same provider when they have different keys.
  2. Group records by their published availability status, category and default customer-access policy. Available and Beta totals must add up to the number of records.
  3. Keep availability separate from review-stage metadata. An Alpha or Beta review stage stays visible in the downloads; a review stage never promotes an App to Available.
  4. Keep unspecified authentication fields empty in CSV and null in JSON. Missing metadata does not mean that credentials or permissions are unnecessary.

Snapshot dates change when the published catalog data changes. A newer page or download request does not make the snapshot newer. This dataset contains public catalog information, not customer records, usage measurements or provider test results.

Which categories are represented?

App categoryCatalog records
Security29
Productivity16
RMM14
PSA10
Platform9
CRM7
Project Delivery7
Automation5
Documentation5
Observability5
Backup4
Accounting3
Forms1
HR1

A category count includes both Available and Beta records. It does not establish that every action in that category is supported.

How to read the fields

CSV fieldMeaning
key, name, categoryStable App identifier, display name and category.
statusAvailable means ready for normal use and covered by Stackyapper support. Beta means available for evaluation, may change, and should begin with a small set of read-only tools.
maturitySeparate review stage: alpha, beta or certified. The certified value records Stackyapper review; it is not third-party certification or a substitute for availability status.
auth_method, auth_levelPublished authentication metadata. Empty means unspecified. Check the App page for its actual setup.
needs_base_urlWhether the App setup asks for a provider-specific base URL.
customer_accessDefault eligibility in managed customer workspaces. This does not grant a person access or override provider, workspace, group or tool permissions.
canonical_url, snapshot_dateCurrent App page and the date of this catalog snapshot.

The JSON includes the same fields using its existing camelCase field names, plus descriptions, audiences and aggregate totals.

What can you use it for?

Shortlist the Apps relevant to your team, separate normal use from evaluation, and identify setup questions before connecting an AI client. Pair it with the business access-control checklist when evaluating permissions. For a specific workflow, verify the required operations on the App page rather than treating a listing as full API coverage.

How to cite the snapshot

Stackyapper. Stackyapper MCP App coverage dataset. Catalog snapshot: 2026-10-20. https://stackyapper.dev/research/mcp-app-coverage. Include your retrieval date and retain the downloaded file when comparing snapshots.

This is first-party catalog data maintained by Stackyapper. It does not establish independent certification, vendor endorsement, measured reliability or coverage of all MCP products.

Sources and corrections

Found a catalog error? Send a correction with the App key and the field to review.