Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CRED-1

NPM · @ALOTH/CRED1

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

Available components

+4 this week 90 Trust /100

Last scanned (20 hours ago)

Scores higher than 86% of npm servers

Category News and Social

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

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

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 2026.11.10 → 2026.11.17 functional
  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 2026.11.9 → 2026.11.10 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@aloth/cred1@2026.11.17

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo aloth/cred-1
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/aloth/cred-1/.github/workflows/publish.yml@refs/tags/v2026-11-17
Rekor log index 3955178014
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d3d0c8aef27561ff54c1238db580469f5d3b6243281d67225f8e2d22780bd31ac52c2726e223d873fa649e976ebe4a67d20210c8d8dcd3d3544457e80

Background: How many MCP packages publish verified provenance →

Dependencies 94 packages
Packages resolved 94
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~277 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
batch_check ~60

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.

NameTypeReqDescription
domainsarrayyesArray of domain names to check.

No output schema declared.

No examples provided.

check_domain ~82

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.

NameTypeReqDescription
domainstringyesDomain name to check (e.g. "infowars.com", "bbc.com"). www. and protocols are stripped automatically.

No output schema declared.

No examples provided.

get_categories ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_stats ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_domains ~77

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.

NameTypeReqDescription
limitnumber–Maximum number of results to return (default 20, max 200).
patternstringyesSubstring or regex pattern to match against domain names (case-insensitive).

No output schema declared.

No examples provided.

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.

npm · @aloth/cred1

# add to Claude Code
claude mcp add aloth-cred-1 -- npx -y @aloth/cred1 --mcp
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.