cred-1

★ 17

mcptrustchecker

★ 172

cred-1 vs mcptrustchecker

Q: Which is better, cred-1 or mcptrustchecker?

By GitHub stars, mcptrustchecker has more community adoption, but the best choice depends on your specific use case.

cred-1: CRED-1 is an open, reproducible domain-level credibility dataset that provides scores for over 2,600 domains known to publish unreliable content. It functions as both a CLI tool and a JavaScript library, and integrates with AI assistants via MCP for real-time misinformation checking.; mcptrustchecker: MCP Trust Checker is a local-first, deterministic security scanner that evaluates the safety of Model Context Protocol (MCP) servers. It utilizes a unique Capability-Flow Trust Model to statically identify potential data exfiltration paths and other vulnerabilities before you connect servers to sensitive data.

TL;DR

cred-1Security & Safety · ★ 17

AI Assistant Integration for Misinformation Detection

Read cred-1 full review →

mcptrustcheckerSecurity & Safety · ★ 172

Scanning already installed MCP servers or local package directories for vulnerabilities.

Read mcptrustchecker full review →

Side-by-Side Comparison

Field

cred-1

mcptrustchecker

Features

cred-1

01Domains with Credibility Scores

02Dual-mode CLI and Library

03Fully Reproducible Dataset Pipeline

04Multi-Signal Scoring

05Privacy-Preserving & On-Device

mcptrustchecker

01Offline by Default: Operates without requiring an account, token, API key, or hosted service, ensuring data privacy.

02Cross-Tool Toxic-Flow Graph: Identifies lethal trifecta scenarios where untrusted input, sensitive data, and external exfiltration paths coexist across multiple tools.

03Deep-Scans Published Packages: Fetches, verifies, and analyzes the actual published source code from npm/PyPI without installation or execution.

04Auditable Trust Score: Provides a deterministic A-F grade with a transparent scoring methodology, including penalty vectors and confidence levels.

05Rug-Pull Integrity: Detects post-approval mutations of tool definitions and verifies package artifact hashes to prevent silent changes.

Use Cases

cred-1

↳AI Assistant Integration for Misinformation Detection

↳Real-time Domain Credibility Checks via CLI or Library

↳Building Browser Extensions for Content Warnings

↳Dataset for Machine Learning Pipelines and Research

mcptrustchecker

↳Scanning already installed MCP servers or local package directories for vulnerabilities.

↳Auditing live HTTP/SSE or OAuth-protected remote MCP endpoints before integration.

↳Integrating into CI/CD pipelines (e.g., GitHub Actions) to enforce security gates and generate SARIF reports.

↳Embedding the scanning engine into marketplaces or platforms to verify the security of listed MCP servers.

↳Using the free hosted web API for quick, zero-install security checks of tool manifests or published packages.

FAQ

What is the difference between cred-1 and mcptrustchecker?

Both cred-1 and mcptrustchecker are in the Security & Safety category. cred-1 has 17 stars, while mcptrustchecker has 172 stars.

Which is better, cred-1 or mcptrustchecker?

The best choice depends on your use case. Choose cred-1 if AI Assistant Integration for Misinformation Detection, and mcptrustchecker if Scanning already installed MCP servers or local package directories for vulnerabilities..

Is cred-1 free or open source?

Yes, cred-1 is open source on GitHub (CC-BY-4.0).

Is mcptrustchecker free or open source?

Yes, mcptrustchecker is open source on GitHub (MIT).

Cloud Infrastructure

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit

→

Alternatives to cred-1 →Alternatives to mcptrustchecker →cred-1 details →mcptrustchecker details →

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related