Mar 5, 2026 at 8:01 AM6 signals analysedNo manual reviews · fully automated Trust Signal Breakdownhigh23 sub-signals across 6 dimensions
CVEs, dependency health, and supply chain integrity
1 of 3 sub-signals with data
Known CVEs100%5.0
No known CVEs
via OSV.dev
Dependency Healthno data—
Weight redistributed to sub-signals with data
Supply Chainno data—
Weight redistributed to sub-signals with data
Uptime, latency, error rates, and incident history
4 of 4 sub-signals with data
Uptime35%5.0
100.00% over 10 checks
via Health checks
Response Latency25%5.0
p99: 143ms, p50: 108ms
via Health checks
Error Rate20%1.0
30.00% error rate (3/10)
via Health checks
Incident History20%4.0
1 incidents in last 90 days
via Incidents table
Commit recency, release cadence, issue response, CI/CD
3 of 4 sub-signals with data
Commit Recency37%1.0
via GitHub
Release Cadence31%2.0
via GitHub
Issue Responseno data—
Weight redistributed to sub-signals with data
CI/CD Presence31%2.0
via GitHub Actions
Downloads, stars, dependents, and growth trajectory
1 of 4 sub-signals with data
Download Volumeno data—
Weight redistributed to sub-signals with data
GitHub Stars100%1.0
52 stars
via GitHub
Dependent Packagesno data—
Weight redistributed to sub-signals with data
Growth Trendno data—
Weight redistributed to sub-signals with data
License, documentation, security policy, changelog
4 of 4 sub-signals with data
Open Source30%5.0
Public repo with OSI-approved license (mit)
via GitHub
Documentation25%5.0
Docs site present with comprehensive README (>2000 bytes + examples)
via GitHub
Security Policy20%2.0
No SECURITY.md found
via GitHub
Changelog25%3.0
CHANGELOG.md present but no releases found
via GitHub
Track record, org maturity, community standing
4 of 4 sub-signals with data
Track Record30%3.0
Internal: 3.0 (3 services), External: 2.0 (33 followers, 735 stars)
via Fabric index
Org Maturity30%5.0
User account, 10.9 years old
via GitHub
Community Standing20%3.0
39 public repositories
via GitHub
Cross-Platform20%1.0
Present on 1 platform(s): github
via Registry scan
About this score
Scored across 23 sub-signals in 6 dimensionsScoring engine v1 (beta) — actively being expandedPhase 1: Core sub-signal architecture (live)Phase 2: Permission scope & expanded collection (in progress)
Trust AssessmentAI Assessment
A MCP server that enables LLMs to interact with Tripadvisor API, supporting location data, reviews, and photos through standardized MCP interfaces
Package Availability (30d)
100.00%
p50: 108ms · p99: 143ms
Avg Latency
89ms
averaged across 30d health checks
Weekly Downloads
—
no package registry data
Transparency & Compliance4/5 passed
Incidents & Alertslast 90 days
Score History10 snapshots
Feb 24Mar 5
Data Sources6 indexed
◎
OSV.devCVE database · vulnerability scanning for npm & PyPI packages
◈
GitHub APICommits, issues, releases, repo metadata, transparency checks
⬡
npm RegistryPackage metadata, weekly downloads, maintainers, dependencies
⬡
PyPIPackage metadata, weekly downloads, dependency tree
△
HTTP Health Checks15-min pings · uptime, latency, status monitoring
◎
PyPI StatsDownload 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.
Share this Trust Score
Generate a scorecard image optimised for X, LinkedIn and other social platforms.
⬇ Download Score Card
