io.github.san-techie21/astracipher

MCPcommunity
v0.1.1io.github.san-techie21UnknownUpdated 7mo agonpmGitHub

Cryptographic identity for AI agents: W3C DIDs, Verifiable Credentials, post-quantum crypto

Cryptographic Identity & Trust Protocol for AI Agents The "SSL certificates" for the AI agent economy. Open-source protocol that gives every AI agent a verifiable, cryptographic identity. AI agents are operating across enterprise systems with zero identity verification. No one can answer: Which agent performed this action? Can we prove compliance to regulators? MCP servers expose powerful tools,…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
1Forks
7mo agoLast update
Package
Authorio.github.san-techie21
LicenseUnknown
Version0.1.1
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies6 resolved · 1 with advisories
Tool surface—
Security scan✓ Cleanv0.1.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

No tool declarations found in the source3mo ago

Forge read 12 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Cryptographic Identity & Trust Protocol for AI Agents The "SSL certificates" for the AI agent economy. Open-source protocol that gives every AI agent a verifiable, cryptographic identity. AI agents are operating across enterprise systems with zero identity verification. No one can answer: Which agent performed this action? Can we prove compliance to regulators? MCP servers expose powerful tools, but any agent can call any tool. There's no authentication, no authorization, no audit trail.…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.