Is Livetennisapi MCP safe to use?

Livetennisapi MCP has an HVTrust score of 77.1/100 (Grade B), ranked #185 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Livetennisapi MCP?

Livetennisapi MCP scores 77.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 151 GitHub stars and is categorized under MCP Servers.

Livetennisapi MCP

livetennisapi/livetennisapi-mcp

MCP server for the Live Tennis API — give Claude, Cursor and other LLM agents real-time tennis scores, odds and model win-probability

MCP Servers TypeScript Listed MIT

Is Livetennisapi MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.0 / 10

Provenance Attested

Signed commits 1%

Last push 6d ago

Compare Livetennisapi MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Livetennisapi MCP scores 77.1/100 (Grade B), ranked #185 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.0/10; 1% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Livetennisapi MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Livetennisapi MCP’s 77.1.

Where the 77.1 comes from

HVTrust dimensions vs the MCP Servers average

77.1 / 100 · 100.0% confidence

Livetennisapi MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

15.1 / 25

4.8 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.6 / 17

1.4 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.3 / 20

4.2 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.4 / 20

1.2 above avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Livetennisapi MCP View MCP Servers Report missing data

60.2

Activity sub-score · out of 100

#104

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

151

Forks

Last Push

2026-09-20

6 days ago

Commits (4 wk)

Downloads (7d)

244

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #184

Analysis

Activity Inputs

60.2 / 100

StarsRepository reach

13.1 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

14.7 / 25

CommunityFork signal

8.1 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

6.0 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 1

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Common questions about Livetennisapi MCP

Public supply-chain signals for Livetennisapi MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Livetennisapi MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Livetennisapi MCP publish package provenance?

Yes. Livetennisapi MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Livetennisapi MCP have an OpenSSF Scorecard?

Livetennisapi MCP has an OpenSSF Scorecard score of 6.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Livetennisapi MCP actively maintained?

Actively maintained. The repository was pushed to within the last 6 day(s).

What license does Livetennisapi MCP use?

Livetennisapi MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Livetennisapi MCP's commits signed?

1% of the last 100 commits to Livetennisapi MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Livetennisapi MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Livetennisapi MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-03

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintain Livetennisapi MCP?

For maintainers

HVTrust scores Livetennisapi MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 554 spots (#733 → #179)

2026-09-23

HVTrust Changed

HVTrust up 47.1pts (30.2 → 77.3)

2026-09-22

Newly Listed

First tracked at rank #733

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-14

Rank Moved

Rank rose 12 spots (#196 → #184)

2026-09-11

Rank Moved

Rank dropped 15 spots (#187 → #202)

2026-09-07

Rank Moved

Rank dropped 21 spots (#164 → #185)

2026-09-06

Rank Moved

Rank dropped 10 spots (#154 → #164)

2026-09-05

Rank Moved

Rank dropped 46 spots (#108 → #154)

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-03

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-03

Grade Changed

Trust grade C → B

2026-09-03

Rank Moved

Rank rose 533 spots (#635 → #102)

2026-09-03

HVTrust Changed

HVTrust up 26.2pts (52.9 → 79.1)

2026-09-02

Rank Moved

Rank dropped 23 spots (#612 → #635)

2026-09-01

Rank Moved

Rank dropped 26 spots (#586 → #612)

2026-08-31

Rank Moved

Rank dropped 30 spots (#556 → #586)

2026-08-29

Rank Moved

Rank dropped 29 spots (#531 → #560)

2026-08-27

Rank Moved

Rank dropped 16 spots (#509 → #525)

2026-08-26

Scorecard Added

OSSF Scorecard: 5.9/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 29 spots (#538 → #509)

2026-08-26

HVTrust Changed

HVTrust up 8.2pts (44.7 → 52.9)

2026-08-24

Rank Moved

Rank dropped 15 spots (#525 → #540)

2026-08-19

Rank Moved

Rank dropped 10 spots (#518 → #528)

2026-08-13

Rank Moved

Rank dropped 15 spots (#512 → #527)

2026-08-10

Rank Moved

Rank dropped 19 spots (#500 → #519)

2026-08-08

Newly Listed

First tracked at rank #500

GitHub → npm: livetennisapi-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/livetennisapi-mcp.svg)](https://hvtracker.net/agents/livetennisapi-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/livetennisapi-mcp"><img src="https://hvtracker.net/badge/livetennisapi-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON