io.github.Servosity/axcient-mcp

MCPcommunity
v0.2.13io.github.ServosityUnknownUpdated 6d agoGitHub

Every x360Recover endpoint, plus the fleet-wide backup-health answers the API alone can't give

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
46GitHub stars
10Forks
6d agoLast update
Needs 1 credential before it runs
  • AXCIENT_API_KEYAPI keyrequired

    Set the AXCIENT_API_KEY credential for the Axcient MCP server.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.Servosity
LicenseUnknown
Version0.2.13
Sourcemcp-registry
GitHubservosity/msp-skills
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 12, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source not readable3mo ago

The repository archive could not be read at scan time (The operation was aborted due to timeout), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Every x360Recover endpoint, plus the fleet-wide backup-health answers the API alone can't give

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.