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.
git clone --depth 1 https://github.com/khanarmaghanrasheed-18/MCP-Dataset-ExplorerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/khanarmaghanrasheed-18/mcp-dataset-explorer/dataset-explorer)<a href="https://agentmods.dev/mcp/khanarmaghanrasheed-18/mcp-dataset-explorer/dataset-explorer"><img src="https://agentmods.dev/badge/mcp/khanarmaghanrasheed-18/mcp-dataset-explorer/dataset-explorer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/khanarmaghanrasheed-18/mcp-dataset-explorer/dataset-explorer"><img src="https://agentmods.dev/badge/mcp/khanarmaghanrasheed-18/mcp-dataset-explorer/dataset-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
dataset-explorer 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 9d 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.
What it actually says
{
"dataset-explorer": {
"command": "uvx",
"args": [
"dataset-explorer-mcp"
],
"env": {}
}
}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.
- 9d ago First seen · 9 lines scan A 5be60553d47b
dataset-explorer is an MCP server published in the GitHub repository khanarmaghanrasheed-18/MCP-Dataset-Explorer (0 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-10-08.
Other mcp servers, from other repositories
knowledge_catalog
MCP server "knowledgecatalog", hosted remotely at dataplex.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
dataproc
MCP server "dataproc", hosted remotely at dataproc-$gcpregion.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
Pinecone
Model Context Protocol server for Pinecone - enables AI assistants to interact with Pinecone indexes and documentation. Runs locally from the @pinecone-database/mcp npm package. Needs 1 environment variable to run.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
hubmesh
Centrality-aware GraphRAG retrieval planner — drop-in layer over any vector DB. Runs locally from the hubmesh Python package.
mcp-server-deapi
35 AI tools for image/video generation, TTS, transcription, OCR & embeddings via deAPI. Remote server at mcp.deapi.ai.