io.github.ai-human-andalusia/hrevn-mcp-server

MCPcommunity
v0.1.0a0io.github.ai-human-andalusiaUnknownUpdated 2mo agoGitHub

HREVN trust layer for baseline diagnostics and verifiable workflow integrity for AI agents.

Minimal stdio MCP server for HREVN, backed by the live managed runtime at This repo exposes HREVN as real MCP tools instead of ad hoc helper scripts. It stays intentionally thin: canonical semantics remain in the HREVN managed runtime the MCP layer only exposes stable tool contracts consequential results come back as structured output, including Optional environment variables: The console entry…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorio.github.ai-human-andalusia
LicenseUnknown
Version0.1.0a0
Sourcemcp-registry
GitHubai-human-andalusia/hrevn-mcp-server
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
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✓ Cleanv0.1.0a0 · 19d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Minimal stdio MCP server for HREVN, backed by the live managed runtime at This repo exposes HREVN as real MCP tools instead of ad hoc helper scripts. It stays intentionally thin: canonical semantics remain in the HREVN managed runtime the MCP layer only exposes stable tool contracts consequential results come back as structured output, including Optional environment variables: The console entry point is: The server uses MCP transport. If you are running directly from source without an installed…

Keywords
mcp