Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
/plugin marketplace add HermesSilva/DASE-MCPnpx agentmods add plugins/hermessilva/dase-mcp/claude-plugingit clone --depth 1 https://github.com/HermesSilva/DASE-MCPGrade A, and why
dase-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "dase-mcp",
"displayName": "DASE ORM Designer MCP",
"version": "2.1.682",
"description": "Connect Claude Code to a live DASE ORM Designer session in VS Code: read, edit and organize .dsorm data models (tables, fields, FK references, layout) through 40+ MCP tools.",
"author": {
"name": "Hermes Silva",
"url": "https://github.com/hermessilva"
},
"homepage": "https://github.com/hermessilva/DASE-MCP",
"repository": "https://github.com/hermessilva/DASE-MCP",
"license": "MIT",
"keywords": [
"dase",
"orm",
"database",
"modeling",
"dsorm",
"dbml",
"designer"
]
}
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 24 lines scan A b9a807b6b3ca
dase-mcp is a plugin published in the GitHub repository HermesSilva/DASE-MCP (0 stars, last pushed 18d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
hana-cli
150+ SAP HANA database tools for AI assistants. Query tables, import/export data, profile data quality, compare schemas, manage backups, monitor performance, and more. Connects to SAP HANA Cloud and on-premise databases.
duckdb-skills
DuckDB-powered skills for Claude Code: read any data file, attach and query DuckDB databases, search DuckDB/DuckLake docs, search past session logs, and install/update DuckDB extensions.
sql-database-pipeline
Build SQL database pipelines with dlt: connect to any SQL source, load tables to a destination, tune performance with backends.
supabase
Supabase MCP integration for database operations, authentication, storage, and real-time subscriptions. Manage your Supabase projects, run SQL queries, and interact with your backend directly.
database
Access MySQL, PostgreSQL, SQLite databases, and Redis key-value stores via CLI for querying, schema/key exploration, and data management.
supabase
Supabase MCP integration for database operations, authentication, storage, and real-time subscriptions. Manage your Supabase projects, run SQL queries, and interact with your backend directly.