updated 2026-11-11 00:08 UTC

MCP Ts Core

Repository by cyanheads

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 4.6 / 10
Provenance None
Signed commits 100%
Last push 3d ago
Advisories None known
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 67.5/100 (Grade B), ranked #440 of 1387 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 4.6/10; 100% of recent commits are signed; no published advisory affects its latest release (@cyanheads/mcp-ts-core); last pushed 2026-11-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Ts Core could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Ts Core and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/cyanheads/mcp-ts-core, Apache-2.0, last pushed 2026-11-08. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.6/10 (scanned Oct 25, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    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 0

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @cyanheads/mcp-ts-core 0.13.22. No published advisory affects it (OSV, checked 2026-11-11).

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 4.6/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Ts Core’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Ts Core compares in MCP Servers

  1. #255 Pubmed MCP Server 67.5 ±0
  2. #256 MCP Local Rag 67.5 ±0
  3. #257 MCP Ts Core 67.5 this agent
  4. #258 Companies House MCP 67.5 ±0
  5. #259 ContextStream 67.4 −0.1

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

Where the 67.5 comes from

HVTrust dimensions vs the MCP Servers average

67.5 / 100 · 100.0% confidence

MCP Ts Core MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.8 / 25
in line with avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
7.4 above avg 12.3
AdoptionLog-scaled stars · package downloads
10.9 / 20
3.3 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-07
Rank Moved
Rank rose 14 spots (#452 → #438)
2026-11-06
Rank Moved
Rank rose 29 spots (#481 → #452)
2026-11-05
Rank Moved
Rank dropped 12 spots (#469 → #481)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/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
View MCP Servers Report missing data
69.7
Activity sub-score · out of 100
#257
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-11-11 00:08 UTC · Repo last pushed 3 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
153
Forks
32
Last Push
2026-11-08
3 days ago
Commits (4 wk)
96
Downloads (7d)
17,072
npm
HN mentions (30d)
—
Open Issues
155
Rank Change
=
was #440

Analysis

Activity Inputs

69.7 / 100
StarsRepository reach
13.1 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
24.8 / 25
CommunityFork signal
7.1 / 20

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 4.6/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 3 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 24HVTrust 3Grade 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-11-07
Rank Moved
Rank rose 14 spots (#452 → #438)
2026-11-06
Rank Moved
Rank rose 29 spots (#481 → #452)
2026-11-05
Rank Moved
Rank dropped 12 spots (#469 → #481)
2026-10-24
Rank Moved
Rank rose 18 spots (#458 → #440)
2026-10-18
Rank Moved
Rank dropped 28 spots (#422 → #450)
2026-10-09
Rank Moved
Rank dropped 13 spots (#402 → #415)
2026-10-01
Rank Moved
Rank dropped 59 spots (#338 → #397)
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)
GitHub → npm: @cyanheads/mcp-ts-core

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 67.5 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.4 · Raw JSON