bikky (bikky-dev/bikky) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 18 tools. No publisher has claimed this listing.

C
Emerging
74/100
2 months ago

bikky

Provides persistent memory for AI coding agents via MCP, enabling teams to share and recall facts across sessions. Automatically captures, classifies, and curates knowledge from supported transcript sources.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

bikky-dev

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: BIKKY_LLM_EXTRA_VIRTUAL_KEY, OPENAI_API_KEY, PORTKEY_API_KEY, QDRANT_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configAWS_BEDROCK_REGION
configAWS_PROFILE
configAWS_REGION
configBIKKY_ACTOR_ID
configBIKKY_ACTOR_LABEL
configBIKKY_AGENT_ID
configBIKKY_AGENT_NAME
configBIKKY_COLLECTION
configBIKKY_DAEMON_ENTITY_TYPING_ENABLED
configBIKKY_DAEMON_ENTITY_TYPING_INTERVAL_SEC
configBIKKY_DAEMON_ENTITY_TYPING_MAX_ENTITIES_PER_RUN
configBIKKY_DAEMON_MEMORY_QUALITY_ROLLUPS_ENABLED
configBIKKY_DAEMON_MEMORY_QUALITY_ROLLUPS_INTERVAL_SEC
configBIKKY_DAEMON_MEMORY_QUALITY_ROLLUPS_LOW_CONFIDENCE_THRESHOLD
configBIKKY_DAEMON_MEMORY_QUALITY_ROLLUPS_MAX_SCOPES_PER_RUN
configBIKKY_DAEMON_RELATION_INFERENCE_ENABLED
configBIKKY_DAEMON_RELATION_INFERENCE_INTERVAL_SEC
configBIKKY_DAEMON_RELATION_INFERENCE_MAX_PAIRS_PER_RUN
configBIKKY_EMBEDDING_RETRIES
configBIKKY_EMBEDDING_RETRY_BASE_DELAY_MS
configBIKKY_EMBEDDING_TIMEOUT_MS
configBIKKY_HOMEThe UI reads from your existing ~/.bikky/config.json (or /config.json) — no extra configuration required.
configBIKKY_LLM_EXTRA_REGION
🔐 secretBIKKY_LLM_EXTRA_VIRTUAL_KEY
configBIKKY_LLM_LOG
configBIKKY_LLM_LOG_MAX_BYTES
configBIKKY_LLM_RETRIES
configBIKKY_LLM_RETRY_BASE_DELAY_MS
configBIKKY_LLM_TIMEOUT_MS
configBIKKY_UI_NO_OPEN
configBIKKY_UI_PORT
configBIKKY_USER_ID
configBIKKY_USER_NAME
configEMBEDDING_BASE_URL
configEMBEDDING_DIMENSIONS
configEMBEDDING_MODEL
configEMBEDDING_PROVIDER
configLLM_BASE_URL
configLLM_FALLBACK_PROVIDER
configLLM_MODEL
configLLM_PROVIDER
configLOGNAME
🔐 secretOPENAI_API_KEYPrefer env vars? Omit api_key above and set instead.
🔐 secretPORTKEY_API_KEY
🔐 secretQDRANT_API_KEY
configQDRANT_RETRIES
configQDRANT_RETRY_BASE_DELAY_MS
configQDRANT_TIMEOUT_MS
configQDRANT_URL
// 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

18/18 tools missing one or more hints — get_setup_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_search_scopes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); configure_credentials (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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 inputs are validated

14/18 tool handlers declare input schemas (78%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

15/18 tool handlers wrap calls in try/catch (83%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 0/18 tools referenced in tests (0%)

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

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

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 Score](https://m8ven.ai/badge/mcp/bikky-dev/bikky)](https://m8ven.ai/mcp/bikky-dev/bikky)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: acf1baeb87afae0a62380d9b45e29ff98c5c3c76
code hash: 63cb985623e4b6a9a0a7b0dbc444f6825243289eea835e0d9cb72264e8e045fe
verified: 6/17/2026, 11:33:04 AM
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