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 manzoor-source/teradata-mcp-server-stcnpx agentmods add plugins/manzoor-source/teradata-mcp-server-stc/agenticgit clone --depth 1 https://github.com/manzoor-source/teradata-mcp-server-stcGrade A, and why
teradata-mcp-customisation 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 2d ago.
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.
This is a copy
100% identical to teradata-mcp-customisation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "teradata-mcp-customisation",
"description": "Build, edit, and debug a semantic layer for the Teradata MCP server — custom tools, cubes, prompts, and glossary entries declared in YAML, plus the profiles.yml that exposes them.",
"version": "1.0.0"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 90 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2d ago First seen · 6 lines scan A 3d5f85f3cf69
teradata-mcp-customisation is a plugin published in the GitHub repository manzoor-source/teradata-mcp-server-stc (0 stars, last pushed 2mo 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. It is 100% identical to teradata-mcp-customisation, differing in 0 lines, and is treated as a copy.
Other plugins, from other repositories
skills
Agent skills for Qdrant vector search: scaling, performance optimization, search quality, monitoring, deployment, edge, model migration, multitenancy, version upgrades, and SDK usage.
pinecone-claude-code-plugin
Pinecone vector database integration. Streamline your Pinecone development with powerful tools for managing vector indexes, querying data, and rapid prototyping. Use slash commands like /quickstart to generate AGENTS.md files and initialize Python projects and /query to quickly explore indexes. Access the Pinecone MCP.
sparq
Usage skills for the sparq RDF triplestore + SPARQL 1.1/1.2 engine (Rust/CLI/HTTP/Python/WASM + reasoning, SHACL, full-text, vector, GeoSPARQL, RSP-QL, ZK query proofs).
kdbai-knowledge
KDB.AI vector database — schema design, hybrid search, and integration patterns for AI applications.
polygres
Sync PostgreSQL sources, set up data pipelines, operate, design, build, and troubleshoot Polygres and pgContext AI Search through public dashboard, CLI, SDK, and Runtime API workflows.
zilliz
Manage Zilliz Cloud clusters and Milvus vector databases from Claude Code using the zilliz-cli.