Is Scira MCP Chat safe to use?

Scira MCP Chat has an HVTrust score of 30.7/100 (Grade D), ranked #1278 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Scira MCP Chat?

Scira MCP Chat scores 30.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 826 GitHub stars and is categorized under Protocols & Tool Integration.

Scira MCP Chat

zaidmukaddam/scira-mcp-chat

A minimalistic MCP client with a good feature set.

Protocols & Tool Integration TypeScript Grade D Listed Apache-2.0

30.7/100

Rank #1278 of 1328

Compare Scira MCP Chat

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2025-12-11 · 273d ago

Recent change

Rank +5

Is Scira MCP Chat safe? Scira MCP Chat scores 30.7/100 (Grade D), ranked #1278 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.8/10; 20% of recent commits are signed; last pushed 2025-12-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#57 MCP Playwright — 36.9 (D) → #58 MCP Hub for Neovim — 36.3 (D) → #60 MCP Context Forge — 26.0 (D) → #61 Hexis — 23.1 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-08

Rank Moved

Rank dropped 12 spots (#1258 → #1270)

2026-09-06

Rank Moved

Rank dropped 17 spots (#1233 → #1250)

2026-09-05

Rank Moved

Rank dropped 20 spots (#1213 → #1233)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.8/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.

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 273 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Scira MCP Chat View Protocols & Tool Integration Report missing data

28.3

Activity sub-score · out of 100

#59

In Protocols & Tool Integration

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

Rank Trend

2026-08-11 2026-09-10

Activity & Reach

Stars

826

Forks

210

Last Push

2025-12-11

273 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1277

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

30.7 / 100 · 100.0% confidence

Scira MCP Chat Protocols & Tool Integration average (61 agents)

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

3.2 / 25

7.3 below avg 10.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

10.0 / 17

2.7 below avg 12.7

Maintenance60% last-push freshness · 40% commit activity

0 / 20

14.3 below avg 14.3

AdoptionLog-scaled stars · package downloads

7.0 / 20

3.6 below avg 10.6

Activity Inputs

28.3 / 100

StarsRepository reach

17.5 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

1.8 / 10

OpenSSF Scorecard · scanned Sep 10, 2026

Signed Commits

20%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 2

CII-Best-Practices 0

Code-Review 1

Contributors 6

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is Scira MCP Chat safe?

Public trust evidence for Scira MCP Chat 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 Scira MCP Chat publish package provenance?

No published build provenance is currently detected for Scira MCP Chat. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Scira MCP Chat have an OpenSSF Scorecard?

Scira MCP Chat has an OpenSSF Scorecard score of 1.8/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 Scira MCP Chat actively maintained?

Stale. The repository has not been pushed to in 273 days. Consider whether the project is still being maintained.

What license does Scira MCP Chat use?

Scira MCP Chat ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Scira MCP Chat's commits signed?

20% of the last 100 commits to Scira MCP Chat 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

Scira MCP Chat appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

5 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

database

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 Scira MCP Chat'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-03

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain Scira MCP Chat?

For maintainers

HVTrust scores Scira MCP Chat 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-08

Rank Moved

Rank dropped 12 spots (#1258 → #1270)

2026-09-06

Rank Moved

Rank dropped 17 spots (#1233 → #1250)

2026-09-05

Rank Moved

Rank dropped 20 spots (#1213 → #1233)

2026-09-04

Rank Moved

Rank dropped 18 spots (#1195 → #1213)

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-09-03

Rank Moved

Rank dropped 36 spots (#1159 → #1195)

2026-09-02

Scorecard Added

OSSF Scorecard: 1.8/10

2026-09-02

Rank Moved

Rank rose 153 spots (#1312 → #1159)

2026-09-02

HVTrust Changed

HVTrust up 17.3pts (13.1 → 30.4)

2026-08-26

Rank Moved

Rank dropped 11 spots (#1293 → #1304)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1268 → #1293)

2026-08-10

Newly Listed

First tracked at rank #1267

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Protocols & Tool Integration

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