shinobi (numbererikson/shinobi) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 39 tools. No publisher has claimed this listing.

D
Caution
50/100

shinobi

Task spine + searched dead-ends + mobile approvals for AI coding agents — one shared brain across every session, machine, and device. Local SQLite or remote streamable-HTTP MCP, MIT.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

numbererikson

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Known vulnerabilities in dependencies: 2 critical, 11 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 7 credentials: GROQ_API_KEY, OPENAI_API_KEY, SHINOBI_DASHBOARD_TOKEN, SHINOBI_EMBED_API_KEY, SHINOBI_VAPID_PRIVATE_KEY, SHINOBI_VAPID_PUBLIC_KEY, VOYAGE_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical11 high6 medium33 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@2.1.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@2.1.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

high@hono/node-server@1.13.0GHSA-wc8c-qw6v-h7f6

@hono/node-server has authorization bypass for protected static paths via encoded slashes in Serve Static Middleware

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highhono@4.6.0GHSA-3vhc-576x-3qv4

Hono JWK Auth Middleware has JWT algorithm confusion when JWK lacks "alg" (untrusted header.alg fallback)

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretGROQ_API_KEY
🔐 secretOPENAI_API_KEYSHINOBI_EMBED_API_KEY — Auth for OpenAI / Voyage (else falls back to / VOYAGE_API_KEY)
configSHINOBI_CONFIG_DIR~/.shinobi Config + plugins directory
configSHINOBI_DASHBOARD_AUTH
configSHINOBI_DASHBOARD_HOST127.0.0.1 Dashboard bind host. Loopback skips auth; non-loopback auto-enables token auth.
configSHINOBI_DASHBOARD_PORT8765 Dashboard port
🔐 secretSHINOBI_DASHBOARD_TOKENcurl -H "Authorization: Bearer $" http://192.168.1.10:8765/api/projects/1/snapshot
configSHINOBI_DB_PATH~/.shinobi/shinobi.db SQLite location
configSHINOBI_DIGESTS_DIR
configSHINOBI_DIGEST_AUTO
🔐 secretSHINOBI_EMBED_API_KEYAuth for OpenAI / Voyage (else falls back to OPENAI_API_KEY / VOYAGE_API_KEY)
configSHINOBI_EMBED_DIMSprovider default Override dimensions
configSHINOBI_EMBED_MODELprovider default Override model id
configSHINOBI_EMBED_PROVIDERnone openai / voyage / ollama / none
configSHINOBI_LLM_PROVIDER
configSHINOBI_MCP_HTTP
configSHINOBI_MIGRATIONS_DIRpackage>/migrations Override migrations source
configSHINOBI_OLLAMA_URL
configSHINOBI_PREPARE_RUNNING
🔐 secretSHINOBI_VAPID_PRIVATE_KEY
🔐 secretSHINOBI_VAPID_PUBLIC_KEY
🔐 secretVOYAGE_API_KEYSHINOBI_EMBED_API_KEY — Auth for OpenAI / Voyage (else falls back to OPENAI_API_KEY / )
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

39/39 tools missing one or more hints — request_approval (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +36 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 2/39 tools referenced in tests (5%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

7 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 7 high severity in production deps — @hono/node-server@1.13.0 (high), @modelcontextprotocol/sdk@1.0.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

6 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

1/7 production deps stale: web-push@2024-01-16 (2.6y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/numbererikson/shinobi?variant=verified)](https://m8ven.ai/mcp/numbererikson/shinobi)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 79dd187a3be74be0166c5e3d4396e881b3f25868
code hash: 7335bf8daf2ad25668754afdcaecc5b2bed2c4205872f50c5456f9fb286b0d71
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client