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/Marc-Dvci/praxis-datahubWrote 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/marc-dvci/praxis-datahub/datahub)<a href="https://agentmods.dev/mcp/marc-dvci/praxis-datahub/datahub"><img src="https://agentmods.dev/badge/mcp/marc-dvci/praxis-datahub/datahub/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/marc-dvci/praxis-datahub/datahub"><img src="https://agentmods.dev/badge/mcp/marc-dvci/praxis-datahub/datahub.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
datahub 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
{
"datahub": {
"command": "uvx",
"args": [
"mcp-server-datahub@latest"
],
"env": {
"DATAHUB_GMS_URL": "http://localhost:8080",
"DATAHUB_GMS_TOKEN": ""
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 12 lines scan A bc458ba5a486
datahub is an MCP server published in the GitHub repository Marc-Dvci/praxis-datahub (0 stars, last pushed 29d ago), licensed Apache-2.0. 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-08-31.
Other mcp servers, from other repositories
operator-etl
MCP server "operator-etl" as configured in khaosans/operator-etl. Runs locally from the operator-etl Python package.
datahub-polygraph
MCP server "datahub-polygraph" as configured in kishanraj41/datahub-polygraph. Runs locally from the datahub-polygraph Python package.
goldencheck
Data validation that discovers rules from your data so you don't have to write them. Runs locally from the goldencheck Python package.
goldenanalysis
Read-only cross-cutting analysis, metrics, and reporting engine for the Golden Suite. Runs locally from the goldenanalysis Python package.
codebase-memory
MCP server "codebase-memory" as configured in benseverndev-oss/goldenmatch. Launched with codebase-memory-mcp.
scherlok
A detective for your data. Zero-config data quality monitoring. Runs locally from the scherlok Python package. Needs 1 environment variable to run.