updated 2026-11-11 00:08 UTC

Serial MCP Server

Repository by es617

Serial port MCP server for Claude Code and other MCP-compatible agents.

MCP Servers Python Listed MIT

Is Serial MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.5 / 10
Provenance Attested
Signed commits 0%
Last push 249d ago
Advisories None known
Compare Serial MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Serial MCP Server scores 53.4/100 (Grade C), ranked #910 of 1387 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 3.5/10; recent commits are unsigned; no published advisory affects its latest release (serial-mcp-server); last pushed 2026-03-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How Serial MCP Server 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 Serial MCP Server 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 Unsigned

    github.com/es617/serial-mcp-server, MIT, last pushed 2026-03-07. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

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

    • Code Review0
    • Branch Protection4
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked and attested

    • PyPI serial-mcp-server Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: serial-mcp-server 0.1.3. No published advisory affects it (OSV, checked 2026-11-11).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 3.5/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 Serial MCP Server’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 Serial MCP Server compares in MCP Servers

  1. #503 Bitrise 53.5 +0.1
  2. #504 Stealth Browser MCP 53.5 +0.1
  3. #505 Serial MCP Server 53.4 this agent
  4. #506 Plateau Creative MCP 53.4 ±0
  5. #507 Licinexus MCP 53.3 −0.1

Bars show each HVTrust score; the tick marks Serial MCP Server’s 53.4.

Where the 53.4 comes from

HVTrust dimensions vs the MCP Servers average

53.4 / 100 · 100.0% confidence

Serial MCP Server MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.9 / 25
1.1 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.5 / 17
0.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.3 below avg 12.3
AdoptionLog-scaled stars · package downloads
6.0 / 20
1.6 below avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-30
Rank Moved
Rank dropped 12 spots (#914 → #926)
2026-10-24
Rank Moved
Rank rose 11 spots (#915 → #904)
2026-10-18
Rank Moved
Rank rose 12 spots (#915 → #903)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.5/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.
Refresh maintenance signals The repo was last pushed 249 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
12.9
Activity sub-score · out of 100
#505
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 C 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 249 days ago — may be stale

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
27
Forks
7
Last Push
2026-03-07
249 days ago
Commits (4 wk)
0
Downloads (7d)
78
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #910

Analysis

Activity Inputs

12.9 / 100
StarsRepository reach
8.7 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.2 / 20

Common questions about Serial MCP Server

Public trust evidence for Serial MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Serial MCP Server publish package provenance?
Yes. Serial MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Serial MCP Server have an OpenSSF Scorecard?
Serial MCP Server has an OpenSSF Scorecard score of 3.5/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 Serial MCP Server actively maintained?
Stale. The repository has not been pushed to in 249 days. Consider whether the project is still being maintained.
What license does Serial MCP Server use?
Serial MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Serial MCP Server's commits signed?
0% of the last 100 commits to Serial MCP Server 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
Serial MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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 Serial MCP Server'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
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Serial MCP Server?

For maintainers

HVTrust scores Serial MCP Server 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 22HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-10-30
Rank Moved
Rank dropped 12 spots (#914 → #926)
2026-10-24
Rank Moved
Rank rose 11 spots (#915 → #904)
2026-10-18
Rank Moved
Rank rose 12 spots (#915 → #903)
2026-10-17
Rank Moved
Rank dropped 14 spots (#901 → #915)
2026-10-09
Rank Moved
Rank dropped 13 spots (#864 → #877)
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 → C
2026-09-23
Rank Moved
Rank rose 417 spots (#1271 → #854)
2026-09-23
HVTrust Changed
HVTrust up 38.5pts (14.3 → 52.8)
2026-09-22
Newly Listed
First tracked at rank #1271
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-15
Rank Moved
Rank dropped 11 spots (#834 → #845)
2026-09-11
Rank Moved
Rank dropped 15 spots (#824 → #839)
2026-09-09
Rank Moved
Rank dropped 11 spots (#814 → #825)
2026-09-07
Rank Moved
Rank dropped 35 spots (#772 → #807)
2026-09-05
Rank Moved
Rank dropped 63 spots (#707 → #770)
2026-09-04
Rank Moved
Rank dropped 19 spots (#688 → #707)
2026-09-03
Rank Moved
Rank dropped 47 spots (#641 → #688)
2026-09-02
Rank Moved
Rank dropped 45 spots (#596 → #641)
2026-09-01
Rank Moved
Rank dropped 22 spots (#574 → #596)
2026-08-31
Rank Moved
Rank dropped 30 spots (#544 → #574)
2026-08-29
Rank Moved
Rank dropped 31 spots (#513 → #544)
2026-08-27
Rank Moved
Rank dropped 11 spots (#495 → #506)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.5/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 17 spots (#512 → #495)
2026-08-26
HVTrust Changed
HVTrust up 7.3pts (46.4 → 53.7)
2026-08-24
Rank Moved
Rank dropped 13 spots (#500 → #513)
2026-08-22
Rank Moved
Rank rose 12 spots (#515 → #503)
2026-08-19
Rank Moved
Rank dropped 10 spots (#502 → #512)
GitHub → PyPI: serial-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 53.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/serial-mcp-server.svg)](https://hvtracker.net/agents/serial-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/serial-mcp-server"><img src="https://hvtracker.net/badge/serial-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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