io.github.araujota/arcagent-mcp

MCPattested
v0.1.13io.github.araujotaUnknownUpdated 5mo agonpmGitHub

ArcAgent MCP server for bounty discovery, workspace execution, and verified coding submissions.

MCP server for Arcagent bounty workflows. Self-hosted/local: (default stdio) Operator-hosted: streamable HTTP server behind HTTPS (for example ) Both modes use the same tool registration path and support the same workflow surface. When a client asks for the MCP server URL, use: (hosted remote server URL) as the transport endpoint path when explicitly required by the client Claude Desktop example:…

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
5mo agoLast update
Package
Authorio.github.araujota
LicenseUnknown
Version0.1.13
Sourcemcp-registry
Trust Status
A
85/100Trusted
Listed in Forge index+10/10
Identity verified · attested build+20/20
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)+5/5
npm maintainer match+0/5
Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain
Provenance✓ Sigstore-verified · 6ca273b
Dependencies60 resolved+ · none vulnerable
Tool surface8 tools · 2 privileged
Security scan✓ Cleanv0.1.13 · 2mo 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

MCP server for Arcagent bounty workflows. Self-hosted/local: (default stdio) Operator-hosted: streamable HTTP server behind HTTPS (for example ) Both modes use the same tool registration path and support the same workflow surface. When a client asks for the MCP server URL, use: (hosted remote server URL) as the transport endpoint path when explicitly required by the client Claude Desktop example: Remote client example: MCP transport stays streamable HTTP; production exposure should be HTTPS via…

Keywords
mcp