updated 2026-09-26 10:08 UTC

MCP Ts Core

cyanheads/mcp-ts-core

Agent-native TypeScript framework for building MCP servers.

MCP Servers TypeScript Listed Apache-2.0

Is MCP Ts Core safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.7 / 10
Provenance None
Signed commits 100%
Last push yesterday
Compare MCP Ts Core

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Ts Core scores 69.9/100 (Grade B), ranked #335 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.7/10; 100% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Ts Core compares in MCP Servers

  1. #199 MCP After Effects 70.0 +0.1
  2. #200 Brave Search MCP Server 69.9 ±0
  3. #201 MCP Ts Core 69.9 this agent
  4. #202 MCP Server For ISO27001 69.8 −0.1
  5. #203 ZulipChat MCP Server 69.8 −0.1

Bars show each HVTrust score; the tick marks MCP Ts Core’s 69.9.

Where the 69.9 comes from

HVTrust dimensions vs the MCP Servers average

69.9 / 100 · 100.0% confidence

MCP Ts Core MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.1 / 25
1.8 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.1 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.8 above avg 12.1
AdoptionLog-scaled stars · package downloads
10.9 / 20
3.7 above avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, OpenRouter, Supabase
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.7/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for MCP Ts Core View MCP Servers Report missing data
70.0
Activity sub-score · out of 100
#201
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 →

Signals refreshed 2026-09-26 10:08 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
152
Forks
30
Last Push
2026-09-25
yesterday
Commits (4 wk)
154
Downloads (7d)
17,578
npm
HN mentions (30d)
—
Open Issues
128
Rank Change
=
was #335

Analysis

Activity Inputs

70.0 / 100
StarsRepository reach
13.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
6.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.7 / 10
OpenSSF Scorecard · scanned Sep 23, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 10
License 10
Maintained 10
Packaging -1
Pinned-Dependencies -1
SAST 10
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 10

Common questions about MCP Ts Core

MCP Ts Core has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does MCP Ts Core publish package provenance?
No published build provenance is currently detected for MCP Ts Core. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Ts Core have an OpenSSF Scorecard?
MCP Ts Core has an OpenSSF Scorecard score of 5.7/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 MCP Ts Core actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MCP Ts Core use?
MCP Ts Core ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Ts Core's commits signed?
100% of the last 100 commits to MCP Ts Core 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
MCP Ts Core appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Extensions
Extension based 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 MCP Ts Core'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 → extension-based
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, OpenRouter, Supabase
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain MCP Ts Core?

For maintainers

HVTrust scores MCP Ts Core 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
Rank 19HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, OpenRouter, Supabase
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 398 spots (#732 → #334)
2026-09-23
HVTrust Changed
HVTrust up 39.3pts (30.3 → 69.6)
2026-09-22
Newly Listed
First tracked at rank #732
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-07
Rank Moved
Rank dropped 24 spots (#332 → #356)
2026-09-05
Rank Moved
Rank dropped 65 spots (#269 → #334)
2026-09-04
Rank Moved
Rank dropped 13 spots (#256 → #269)
2026-09-02
Grade Changed
Trust grade D → B
2026-09-02
Rank Moved
Rank rose 640 spots (#891 → #251)
2026-09-02
HVTrust Changed
HVTrust up 25.7pts (41.6 → 67.3)
2026-09-01
Rank Moved
Rank dropped 36 spots (#855 → #891)
2026-08-31
Rank Moved
Rank dropped 31 spots (#824 → #855)
2026-08-30
Rank Moved
Rank dropped 32 spots (#792 → #824)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.6/10
2026-08-29
Rank Moved
Rank rose 296 spots (#1088 → #792)
2026-08-29
HVTrust Changed
HVTrust up 19.4pts (22.4 → 41.8)
2026-08-28
Rank Moved
Rank dropped 29 spots (#1059 → #1088)
2026-08-27
Rank Moved
Rank dropped 25 spots (#1034 → #1059)
2026-08-26
Rank Moved
Rank dropped 82 spots (#952 → #1034)
2026-08-24
Rank Moved
Rank dropped 16 spots (#932 → #948)
2026-08-22
Rank Moved
Rank rose 11 spots (#947 → #936)
2026-08-20
Rank Moved
Rank rose 27 spots (#979 → #952)
2026-08-19
Rank Moved
Rank dropped 10 spots (#969 → #979)
2026-08-16
Rank Moved
Rank dropped 28 spots (#945 → #973)
2026-08-12
Rank Moved
Rank rose 15 spots (#956 → #941)
2026-08-10
Rank Moved
Rank dropped 15 spots (#928 → #943)
2026-08-08
Newly Listed
First tracked at rank #913
GitHub → npm: @cyanheads/mcp-ts-core

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 69.9 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-ts-core.svg)](https://hvtracker.net/agents/mcp-ts-core)
HTML:
<a href="https://hvtracker.net/agents/mcp-ts-core"><img src="https://hvtracker.net/badge/mcp-ts-core.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