@dravensoft/arena-mcp

Name: @dravensoft/arena-mcp
Author: io.github.dravensoft-dev

MCPattested

v11.1.0io.github.dravensoft-devMITUpdated 13d agonpm GitHub

Arena by Dravensoft over MCP: the router, the references and every component document.

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.

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.

80Downloads/wk

2GitHub stars

13d agoLast update

Package

Authorio.github.dravensoft-dev

LicenseMIT

Version11.1.0

Sourcenpm+mcp-registry

npm@dravensoft/arena-mcp

GitHubdravensoft-dev/arena

SBOMCycloneDX 1.6 ↓

Trust Status

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 · 8a1fd51

Dependencies✓ 3 resolved · none vulnerable

Tool surface4 tools · none privileged

Security scan✓ Cleanv11.0.1 · 18d agoHow well does this scan work?

EvalsNone

IndexedSep 5, 2026

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

Tools

4 tools · none privileged

Statically extracted from the published packagev11.0.1 · 18d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

arena_startWhere to begin with Arena: what is installed, and the one document to read

Where to begin with Arena: what is installed, and the one document to read

No input schema was published for this tool.

arena_listEvery Arena document this project carries, as addressable URIs: the router, the

Every Arena document this project carries, as addressable URIs: the router, the

No input schema was published for this tool.

arena_findFind the Arena documents that answer a question, by words in their name and

Find the Arena documents that answer a question, by words in their name and

No input schema was published for this tool.

arena_readRead one Arena document by its URI. Every resource this server offers is also

Read one Arena document by its URI. Every resource this server offers is also

No input schema was published for this tool.

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Arena by Dravensoft over MCP: the router, the references and every component document.

Keywords

mcp

Alternatives

Comparing tool surfaces…

@dravensoft/arena-mcp

Tools

Tools exposed

Dependency tree