# CRED-1 (npm · @aloth/cred1)

Domain credibility ratings from the CRED-1 dataset: check, batch check and search news domains

- Trust score: 90/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@aloth/cred1`: 90/100 (this document), [markdown](https://verifymcp.io/servers/aloth-cred-1/aloth-cred1.md), [page](https://verifymcp.io/servers/aloth-cred-1/aloth-cred1)

## Channel facts

- Registry: `npm`
- Package: `@aloth/cred1`
- Version: `2026.11.17`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 84/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to aloth/cred-1).
  - License check failed: the license (MIT AND CC-BY-4.0) isn't a recognized OSI-approved license.
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 277 tokens (~55/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CRED-1 MCP server?

CRED-1 runs locally as an npm package, launched with npx -y @aloth/cred1 --mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add aloth-cred-1 -- npx -y @aloth/cred1 --mcp
```

### Cursor

```json
{
  "mcpServers": {
    "aloth-cred-1": {
      "command": "npx",
      "args": [
        "-y",
        "@aloth/cred1",
        "--mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aloth-cred-1": {
      "command": "npx",
      "args": [
        "-y",
        "@aloth/cred1",
        "--mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add aloth-cred-1 -- npx -y @aloth/cred1 --mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aloth-cred-1": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@aloth/cred1",
        "--mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  aloth-cred-1:
    command: "npx"
    args: ["-y", "@aloth/cred1", "--mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "aloth-cred-1": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@aloth/cred1",
        "--mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "aloth-cred-1": {
      "command": "npx",
      "args": [
        "-y",
        "@aloth/cred1",
        "--mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 88, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 73, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 2026.11.10 → 2026.11.17

### 2026-11-15 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 85, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-10 (score 70, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 2026.11.9 → 2026.11.10

## MCP tools (5)

### `check_domain` (~82 tokens)

Check a single domain's credibility score and category using the CRED-1 dataset. Returns score (0.0–1.0, lower = less credible), category, traffic-light level, and metadata.

Input parameters:

- `domain` (string, required): Domain name to check (e.g. "infowars.com", "bbc.com"). www. and protocols are stripped automatically.

### `batch_check` (~60 tokens)

Check multiple domains at once (max 100). Returns an array of results with the same fields as check_domain. Domains not found in the dataset are included with a "not_found" flag.

Input parameters:

- `domains` (array, required): Array of domain names to check.

### `search_domains` (~77 tokens)

Search for domains matching a substring or regex pattern. Useful for discovering all entries related to a topic or checking variations of a domain name.

Input parameters:

- `limit` (number): Maximum number of results to return (default 20, max 200).
- `pattern` (string, required): Substring or regex pattern to match against domain names (case-insensitive).

### `get_stats` (~31 tokens)

Get summary statistics for the CRED-1 dataset: total domain count, per-category breakdown, and dataset version.

### `get_categories` (~27 tokens)

List all credibility categories with their descriptions, typical score ranges, and domain counts from the dataset.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/aloth-cred-1/aloth-cred1#diagnostics

## Score history

- 2026-11-21: 90
- 2026-11-20: 89
- 2026-11-19: 89
- 2026-11-18: 88
- 2026-11-17: 73
- 2026-11-16: 87
- 2026-11-15: 87
- 2026-11-14: 86
- 2026-11-13: 86
- 2026-11-12: 85
- 2026-11-11: 85
- 2026-11-10: 70
- 2026-11-09: 84
- 2026-11-08: 84
- 2026-11-07: 68
- 2026-11-06: 83
- 2026-11-05: 82
- 2026-11-04: 67
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 66

## Common questions

### What is the CRED-1 MCP server?

CRED-1 is an MCP server listed in the public MCP registry as io.github.aloth/cred-1. Domain credibility ratings from the CRED-1 dataset: check, batch check and search news domains. This page covers its npm package (@aloth/cred1).

### Is the CRED-1 MCP server safe to use?

CRED-1 scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CRED-1 MCP server expose?

CRED-1 exposes 5 tools: check_domain, batch_check, search_domains, get_stats, get_categories. Their descriptions and schemas cost roughly 277 tokens of context every time the server is loaded.

### Is the CRED-1 MCP server still maintained?

CRED-1 is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the CRED-1 MCP server under?

CRED-1 declares the MIT AND CC-BY-4.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

### What did VerifyMCP test on the CRED-1 MCP server?

VerifyMCP ran 16 checks on CRED-1, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@aloth/cred1
- Socket report: https://socket.dev/npm/package/@aloth/cred1
- Repository: https://github.com/aloth/cred-1
- Website: https://aloth.github.io/cred-1/
- Changelog RSS feed: https://verifymcp.io/servers/aloth-cred-1/aloth-cred1.xml
- Changelog JSON feed: https://verifymcp.io/servers/aloth-cred-1/aloth-cred1/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/aloth-cred-1/aloth-cred1.json
- HTML version of this page: https://verifymcp.io/servers/aloth-cred-1/aloth-cred1
