Mar 4, 2026 at 4:17 AM 6 signals analysed No manual reviews · fully automatedTrust Signal Breakdown medium 23 sub-signals across 6 dimensions
Vulnerability & Safety ×0.25 0.0 CVEs, dependency health, and supply chain integrity
0 of 3 sub-signals with data
Known CVEs no data —
Weight redistributed to sub-signals with data
Dependency Health no data —
Weight redistributed to sub-signals with data
Supply Chain no data —
Weight redistributed to sub-signals with data
Operational Reliability ×0.15 4.0 Uptime, latency, error rates, and incident history
4 of 4 sub-signals with data
Uptime 35% 5.0
100.00% over 3 checks
via Health checks
Response Latency 25% 5.0
p99: 156ms, p50: 153ms
via Health checks
Error Rate 20% 1.0
33.33% error rate (1/3)
via Health checks
Incident History 20% 4.0
1 incidents in last 90 days
via Incidents table
Maintenance Activity ×0.15 2.2 Commit recency, release cadence, issue response, CI/CD
3 of 4 sub-signals with data
Commit Recency 37% 0.0
via GitHub
Release Cadence 31% 2.0
via GitHub
Issue Response no data —
Weight redistributed to sub-signals with data
CI/CD Presence 31% 5.0
via GitHub Actions
Adoption ×0.15 1.0 Downloads, stars, dependents, and growth trajectory
1 of 4 sub-signals with data
Download Volume no data —
Weight redistributed to sub-signals with data
GitHub Stars 100% 1.0
43 stars
via GitHub
Dependent Packages no data —
Weight redistributed to sub-signals with data
Growth Trend no data —
Weight redistributed to sub-signals with data
Transparency ×0.15 3.4 License, documentation, security policy, changelog
4 of 4 sub-signals with data
Open Source 30% 5.0
Public repo with OSI-approved license (mit)
via GitHub
Documentation 25% 4.0
Good README (>2000 bytes with examples)
via GitHub
Security Policy 20% 2.0
No SECURITY.md found
via GitHub
Changelog 25% 2.0
No CHANGELOG.md and no releases found
via GitHub
Publisher Trust ×0.15 0.0 Track record, org maturity, community standing
0 of 4 sub-signals with data
Track Record no data —
Weight redistributed to sub-signals with data
Org Maturity no data —
Weight redistributed to sub-signals with data
Community Standing no data —
Weight redistributed to sub-signals with data
Cross-Platform no data —
Weight redistributed to sub-signals with data
About this scoreScored across 23 sub-signals in 6 dimensions Scoring engine v1 (beta) — actively being expanded Phase 1: Core sub-signal architecture (live) Phase 2: Permission scope & expanded collection (in progress)
Trust Assessment AI Assessment
mcp-servers-kagi is an MIT-licensed MCP server by ac3xx that provides Kagi Search API integration for web searches. The service shows reliable uptime but has zero recorded weekly downloads and minimal publisher track record, indicating it may be newly released or not yet widely adopted. The Kagi API is noted as being in private beta, which may limit immediate usability for general users.
Generated by Fabric AI · Mar 4, 2026 at 4:17 AM
Package Availability (30d)
100.00%
p50: 153ms · p99: 156ms
Avg Latency
109ms
averaged across 30d health checks
Weekly Downloads
—
no package registry data
Transparency & Compliance 3/5 passed
Incidents & Alerts last 90 days
Score History 3 snapshots
Feb 24 Mar 2
Data Sources 6 indexed
◎
OSV.dev CVE database · vulnerability scanning for npm & PyPI packages
◈
GitHub API Commits, issues, releases, repo metadata, transparency checks
⬡
npm Registry Package metadata, weekly downloads, maintainers, dependencies
⬡
PyPI Package metadata, weekly downloads, dependency tree
△
HTTP Health Checks 15-min pings · uptime, latency, status monitoring
◎
PyPI Stats Download statistics and trends
Are you the publisher? Claim this profile to unlock deeper evaluation, real-time monitoring, and trust signals that help agents discover your service.
Claim Provider Report Issue
Share this Trust Score Generate a scorecard image optimised for X, LinkedIn and other social platforms.
⬇ Download Score Card