Tages (ryantlee25-droid/tages) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 56 tools. No publisher has claimed this listing.

D
Caution
50/100

Tages

Enables AI coding agents to maintain persistent, cross-session memory of codebase architecture, naming conventions, and decisions through MCP tools. Eliminates repetitive project re-explanation by automatically injecting stored context into every session with local-first SQLite storage and optional team sharing capabilities.

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

ryantlee25-droid

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: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 6 credentials: ANTHROPIC_API_KEY, OPENAI_API_KEY, SUPABASE_ANON_KEY, TAGES_ENCRYPTION_KEY, TAGES_SERVICE_KEY, TAGES_SUPABASE_ANON_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes56 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

remember

Store a memory about this codebase — conventions, decisions, architecture, patterns, or lessons learned

recall

Search codebase memories by fuzzy query — finds conventions, decisions, patterns, and lessons. Results are numbered passages [1..n] with source and date. Before answering, briefly note which numbered passage(s) support your answer, then cite them.

forget

Delete a memory by its key

conventions

List all coding conventions for this project

architecture

List all architecture notes and module boundaries

decisions

List the decision log — why things were built the way they are

context

Get all memories related to a specific file path

staleness

Check for stale memories that may be outdated or no longer relevant

conflicts

Detect potential conflicts between memories — overlapping or contradictory entries

stats

Show memory usage statistics — counts by type, recall hit rate, agent sessions, most/least accessed

observe

Report what you are doing or learning — Tages silently extracts memories from your observations. Call this naturally as you work, no need to format.

session_end

End the current session with a summary of what was built, decided, or learned — auto-extracts memories from the summary

verify_memory

Verify a pending auto-extracted memory — promotes it to live so it appears in recall results

pending_memories

List auto-extracted memories that need verification before they appear in recall

memory_stats_detail

Detailed memory statistics — counts by type and status, average confidence, top 5 agents, and total count

memory_history

Get the version history of a memory — shows past values, confidence changes, and who changed it. Optionally revert to a previous version.

contextual_recall

Search memories filtered by execution context — current files, agent name, or phase. More precise than recall for context-aware retrieval.

resolve_conflict

Resolve a detected memory conflict using keep_newer, keep_older, or merge strategies

list_conflicts

List unresolved memory conflicts for this project

suggestions

Get suggestions for memories you should store, based on queries that returned no results

import_memories

Import memories from a JSON array or markdown file content. Handles duplicates with skip/overwrite/merge strategies.

memory_graph

Build a relationship graph from crossSystemRefs and output as a Mermaid diagram

fork_branch

Fork current memories into a session branch for experimentation. Branch writes won't affect main until merged.

merge_branch

Merge a session branch back into main memory. Detects conflicts between branch and main changes.

list_branches

List memories in a session branch

detect_duplicates

Detect near-duplicate memories using Jaccard similarity on key+value tokens

consolidate_memories

Merge two duplicate memories into one, preserving all metadata

impact_analysis

Analyze the downstream impact of a memory — how many others depend on it

risk_report

Get project-wide risk ranking — which memories are most dangerous to change

graph_analysis

Analyze the memory dependency graph — orphans, critical paths, impact scores

check_convention

Check a memory against all stored conventions — detect conflicts or duplicates before storing

enforcement_report

Get per-agent convention compliance stats and recent violations

memory_quality

Score a specific memory on completeness, freshness, consistency, and usefulness (0-100)

project_health

Get overall project memory health score with dimension breakdown and improvement suggestions

list_templates

List available memory templates (api-endpoint, react-component, database-migration, test-suite, cli-command)

match_templates

Find templates matching given file paths — prompts agent to fill required fields

apply_template

Create a memory from a filled template with automatic key generation

archive_memory

Archive a memory to cold storage — removes it from recall but preserves it for restoration

restore_memory

Restore an archived memory back to live status

list_archived

List archived memories with their archive reasons and dates

archive_stats

Get archive statistics — total archived, restored, expired

auto_archive

Scan for stale low-quality memories and auto-archive them

federate_memory

Promote a project memory to the org-wide federated library

import_federated

Import a federated memory from the shared library into this project

list_federated

List all memories in the federated library

federation_overrides

Show which federated memories have local project overrides

session_replay

Replay a session timeline showing all tool calls with metrics

agent_metrics

Get agent effectiveness metrics — recall hit rate, memory creation quality, convention compliance

trends

Detect performance trends across sessions — improvements and regressions

pre_check

Before starting a task, get a list of gotchas: anti-patterns to avoid, conventions to follow, and lessons learned from past experience

file_recall

Find memories related to specific file paths — matches by exact path, directory prefix, or reverse prefix. Prioritises anti-pattern and convention memories.

project_brief

Generate a token-budgeted project brief for system prompt injection. Returns gotchas, conventions, architecture, and decisions — prioritized by importance. Use this ONCE at session start instead of calling recall/conventions/architecture individually.

import_claude_md

Parse a CLAUDE.md file and auto-create memories from its sections. Conventions, architecture notes, decisions, and anti-patterns become typed memories.

memory_audit

Audit project memory coverage and quality: type distribution, brief-critical coverage score, imperative phrasing ratio, and actionable suggestions.

sharpen_memory

Rewrite a memory value into imperative form (ALWAYS/NEVER/MUST/DO NOT) using Claude Haiku. Returns a before/after preview unless confirmed=true.

post_session

End-of-session tool: extract memories from a session summary, optionally regenerate the project brief. Combines session_end + brief regeneration in one call.

// known CVEs in dependencies3 high

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

high@modelcontextprotocol/sdk@1.12.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

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.
🔐 secretANTHROPIC_API_KEY
configOLLAMA_URL
🔐 secretOPENAI_API_KEY
🔐 secretSUPABASE_ANON_KEY
configSUPABASE_URL
configTAGES_AGENT_NAME
configTAGES_CWD
🔐 secretTAGES_ENCRYPTION_KEY
configTAGES_OPENAI_EMBED
configTAGES_PLAN
configTAGES_PROJECT_ID
configTAGES_PROJECT_SLUG
configTAGES_RECALL_CANDIDATE_POOL
🔐 secretTAGES_SERVICE_KEY
🔐 secretTAGES_SUPABASE_ANON_KEY
configTAGES_SUPABASE_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

56/56 tools missing one or more hints — remember (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); forget (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +53 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

13/20 tool handlers declare input schemas (65%)

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

Tool handlers catch errors

Only 0/20 tool handlers wrap calls in try/catch (0%)

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

README present

No README found

Add a README.md describing the server and its tools.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Shell command execution

12 child_process calls — runs shell commands

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

Secrets not written to files

2 secret values written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.0 (high), @modelcontextprotocol/sdk@1.12.0 (high)

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

Domain consistency

npm scope @tages doesn't match GitHub owner ryantlee25-droid

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 10 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/ryantlee25-droid/tages?variant=verified)](https://m8ven.ai/mcp/ryantlee25-droid/tages)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b850ebeaf03db7011e8b946667dd8633475d9f20
code hash: 4722e8f5dbde27c24452fe41eda78ccdb754ee030de2a0007209ef5192b6fbb8
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