# MCP Server Registry — Health & Trust Scores (`alaudinburki/mcp-server-registry`) Actor

Catalog Model Context Protocol servers and get the answer you need before wiring one into an agent: is it maintained, what transport does it speak, how do you install it, and should you trust it. Maintenance health, abandonment risk and a 0-100 trust score. Free GitHub API.

- **URL**: https://apify.com/alaudinburki/mcp-server-registry.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** MCP servers, Developer tools
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## MCP Server Registry — Health & Trust Scores

A catalog of **Model Context Protocol servers** that answers the question every list skips: *before I
wire this into an agent — is it maintained, what transport does it speak, how do I install it, and
should I trust it?*

Built on the free public GitHub API. **No login, no anti-bot.**

### Why this one

MCP went from a proposal to tens of thousands of servers in about a year. The registries that exist
give you a name and a star count. Neither tells you that the server you're about to depend on was last
touched 14 months ago, has no license, and speaks a transport your client doesn't support. This is the
**"npm registry data" of the agent era**: a catalog with a maintenance verdict.

### What you get

| Field | Description |
|---|---|
| **`trustScore`** | 0–100 "would I ship this?" — deliberately weights **maintenance over popularity** |
| **`maintenanceHealth`** | 0–100 from push recency, with small bonuses for a license and real adoption |
| **`abandonmentRisk`** | `active` · `slowing` · `at_risk` · `likely_abandoned` · `archived` |
| `daysSincePush` | How stale the code actually is |
| **`transport`** | `stdio` · `sse` · `http` (or `unknown`) — what your client must support |
| **`installMethod`** | `npx / npm` · `uvx / pip` · `docker` · `go install` · `cargo install` |
| `fullName` / `url` / `owner` | Repository identity |
| `stars` / `forks` / `openIssues` | Adoption signals |
| `language` / `license` / `topics` / `description` | Metadata |
| `archived` | Dead by definition (excluded unless you ask for them) |

> **Why a 40-star server can outrank a 5,000-star one:** a popular server abandoned two years ago is a
> worse dependency than a small one shipped last week. `trustScore` reflects that on purpose.

### How to use it

1. **Add a free GitHub token.** Unauthenticated search is rate-limited after a page or two; a token
   raises the limit ~30×. Read-only public scope is enough.
2. Leave topics empty to sweep the standard MCP topics, or pass your own.
3. Tick **Only actively maintained** (and/or set a **minimum trust score**) to get a shortlist you'd
   actually ship.

### Input

```json
{
  "githubToken": "ghp_your_token",
  "activeOnly": true,
  "minTrustScore": 50,
  "minStars": 5,
  "maxPages": 2
}
```

### Sample output

```json
[
  {
    "fullName": "acme/mcp-thing",
    "trustScore": 84,
    "maintenanceHealth": 100,
    "abandonmentRisk": "active",
    "daysSincePush": 5,
    "transport": "stdio",
    "installMethod": "uvx / pip",
    "language": "Python",
    "stars": 120,
    "forks": 8,
    "license": "MIT",
    "description": "MCP server over stdio",
    "topics": "mcp-server, python",
    "url": "https://github.com/acme/mcp-thing",
    "archived": false,
    "status": "ok"
  }
]
```

### Typical uses

- **Pick a dependency** — shortlist servers by trust before adding one to an agent stack.
- **Audit what you already use** — feed your current servers' topics and check none have gone stale.
- **Ecosystem research** — transport mix, language mix, and how fast the space is actually maintained.
- **Monitoring** — schedule it; a server sliding from `active` to `at_risk` is an early warning.

### Pricing

**$1.50 / 1,000 servers** (`$0.0015` per result), plus a near-zero start fee. Never charged beyond
`maxItems`; rate-limit and search problems are reported in `QUALITY_REPORT`, not billed as data.

### FAQ & limitations

- **Do I need a GitHub token?** Not strictly, but without one GitHub will rate-limit you quickly. It's free.
- **Where does discovery come from?** GitHub topics. A server that doesn't tag itself with an MCP topic
  won't be found — that's a real limitation, and it's why the actor reports how many raw hits it saw.
- **Is `transport` guaranteed?** No — it's **inferred** from the description/topics and can read `unknown`.
  Treat it as a strong hint, and confirm in the server's README before wiring it up.
- **Does it test that servers actually run?** No. It scores *maintenance and metadata*, not live uptime.
  Nothing here executes third-party code.
- **Why are archived repos missing?** Excluded by default; tick `includeArchived` to see them.

### Related actors

- **Reliability Toolkit (MCP)** — your own MCP server, exposing site-diligence tools to agents.
- **GitHub Repo Scraper** · **npm Package Info** — the same health approach for general dependencies.
- **AI Crawler Audit** — the other half of the AI-readiness picture.

# Actor input Schema

## `topics` (type: `array`):

Leave empty to use the standard MCP topics (mcp-server, model-context-protocol, mcp, modelcontextprotocol).

## `githubToken` (type: `string`):

A free personal access token raises GitHub's search rate limit ~30x. Without it you will likely be rate-limited after a page or two. Read-only public scope is enough.

## `activeOnly` (type: `boolean`):

Keep only servers pushed recently enough to score as 'active' — the ones safe to depend on.

## `minTrustScore` (type: `integer`):

Filter out low-confidence servers. Trust weights maintenance over popularity.

## `minStars` (type: `integer`):

Skip servers below this star count.

## `includeArchived` (type: `boolean`):

Archived servers are dead by definition; off by default.

## `maxPages` (type: `integer`):

100 servers per page. 2 pages per topic is a good default.

## `maxItems` (type: `integer`):

Hard limit, strictly enforced.

## Actor input object example

```json
{
  "topics": [],
  "activeOnly": false,
  "minTrustScore": 0,
  "minStars": 0,
  "includeArchived": false,
  "maxPages": 2,
  "maxItems": 2000
}
```

# Actor output Schema

## `results` (type: `string`):

MCP servers with health and trust scores.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/mcp-server-registry").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/mcp-server-registry").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call alaudinburki/mcp-server-registry --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/mcp-server-registry"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/d7Dpvon0l9zAzttBt/builds/Cq7yQSMwfbOIHZu9e/openapi.json