updated 2026-09-26 10:08 UTC

Replicant MCP

thecombatwombat/replicant-mcp

Android MCP server - production-grade, token-optimized, accessibility-first

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.5 / 10
Provenance Attested
Signed commits 29%
Last push 62d ago
Compare Replicant MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Replicant MCP scores 61.3/100 (Grade C), ranked #599 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 3.5/10; 29% of recent commits are signed; last pushed 2026-07-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Replicant MCP compares in MCP Servers

  1. #335 MCP Me 61.4 +0.1
  2. #336 Desktop Commander MCP 61.3 ±0
  3. #337 Replicant MCP 61.3 this agent
  4. #338 Norman MCP Server 61.2 −0.1
  5. #339 Atlassian Rovo MCP Server 61.1 −0.2

Bars show each HVTrust score; the tick marks Replicant MCP’s 61.3.

Where the 61.3 comes from

HVTrust dimensions vs the MCP Servers average

61.3 / 100 · 100.0% confidence

Replicant MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.3 / 25
3.0 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
11.5 / 17
0.7 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
7.9 / 20
4.2 below avg 12.1
AdoptionLog-scaled stars · package downloads
5.2 / 20
2.0 below 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-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-24
Rank Moved
Rank dropped 27 spots (#566 → #593)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
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 62 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Replicant MCP View MCP Servers Report missing data
27.3
Activity sub-score · out of 100
#337
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-09-26 10:08 UTC · Repo last pushed 62 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
17
Forks
4
Last Push
2026-07-26
62 days ago
Commits (4 wk)
0
Downloads (7d)
44
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #599

Analysis

Activity Inputs

27.3 / 100
StarsRepository reach
7.5 / 30
FreshnessLast push recency
16.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.5 / 10
OpenSSF Scorecard · scanned Sep 22, 2026
Signed Commits
29%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
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 3
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Common questions about Replicant MCP

Replicant MCP 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 Replicant MCP publish package provenance?
Yes. Replicant MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Replicant MCP have an OpenSSF Scorecard?
Replicant MCP 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 Replicant MCP actively maintained?
Slowing down. Last push was 62 days ago — keep an eye on whether activity resumes.
What license does Replicant MCP use?
Replicant MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Replicant MCP's commits signed?
28% of the last 100 commits to Replicant 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
Replicant MCP 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
high confidence
Declared
Declared plugin/integration surface detected.
  • shell
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 Replicant 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-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Replicant MCP?

For maintainers

HVTrust scores Replicant 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
Rank 19HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1Provenance 1MCP 1Surface 1
2026-09-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-24
Rank Moved
Rank dropped 27 spots (#566 → #593)
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 626 spots (#1192 → #566)
2026-09-23
HVTrust Changed
HVTrust up 42.6pts (19.5 → 62.1)
2026-09-22
Newly Listed
First tracked at rank #1192
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank rose 15 spots (#555 → #540)
2026-09-13
Rank Moved
Rank dropped 18 spots (#533 → #551)
2026-09-08
Rank Moved
Rank dropped 12 spots (#499 → #511)
2026-09-07
Rank Moved
Rank dropped 37 spots (#462 → #499)
2026-09-06
Rank Moved
Rank dropped 12 spots (#450 → #462)
2026-09-05
Rank Moved
Rank dropped 71 spots (#379 → #450)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 553 spots (#923 → #370)
2026-09-03
HVTrust Changed
HVTrust up 21.0pts (42.3 → 63.3)
2026-09-02
Rank Moved
Rank dropped 52 spots (#871 → #923)
2026-09-01
Scorecard Added
OSSF Scorecard: 3.5/10
2026-09-01
Rank Moved
Rank rose 76 spots (#947 → #871)
2026-09-01
HVTrust Changed
HVTrust up 4.9pts (37.4 → 42.3)
2026-08-31
Rank Moved
Rank dropped 32 spots (#915 → #947)
2026-08-30
Rank Moved
Rank dropped 43 spots (#872 → #915)
2026-08-29
Rank Moved
Rank dropped 47 spots (#825 → #872)
2026-08-28
Rank Moved
Rank dropped 25 spots (#800 → #825)
2026-08-27
Rank Moved
Rank dropped 22 spots (#778 → #800)
2026-08-26
Rank Moved
Rank dropped 102 spots (#676 → #778)
2026-08-16
Rank Moved
Rank dropped 12 spots (#654 → #666)
2026-08-10
Rank Moved
Rank dropped 27 spots (#628 → #655)
2026-08-08
Newly Listed
First tracked at rank #626
GitHub → npm: replicant-mcp

Embed Badge Badge guide for maintainers →

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