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/datalastic/mcp-server-datalasticWrote 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/datalastic/mcp-server-datalastic/vessel-tracking)<a href="https://agentmods.dev/mcp/datalastic/mcp-server-datalastic/vessel-tracking"><img src="https://agentmods.dev/badge/mcp/datalastic/mcp-server-datalastic/vessel-tracking/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/datalastic/mcp-server-datalastic/vessel-tracking"><img src="https://agentmods.dev/badge/mcp/datalastic/mcp-server-datalastic/vessel-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vessel-tracking 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 1mo 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
{
"vessel-tracking": {
"url": "https://mcp.datalastic.com/mcp",
"type": "streamable-http"
}
}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.
- 1mo ago First seen · 6 lines scan A 3382632dc5b1
vessel-tracking is an MCP server published in the GitHub repository datalastic/mcp-server-datalastic (0 stars, last pushed 3mo 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-08-31.
Other mcp servers, from other repositories
supply-chain-local-kb
MCP server "supply-chain-local-kb" as configured in wublinux/supply-chain-local-agent. Runs locally from the supply-chain-local-kb npm package.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
ActiveDirectoryMCP
MCP server "ActiveDirectoryMCP" as configured in alpadalar/ActiveDirectoryMCP. Launched with uv --directory /absolute/path/to/ActiveDirectoryMCP run activedirectory-mcp. Needs 3 environment variables to run.
claude-octopus
Spawn multiple specialized Claude Code agents as MCP servers, each independently configured. Runs locally from the claude-octopus npm package. Needs 7 environment variables to run.
behavior-mcp
MCP server "behavior-mcp" as configured in putervision/state-memory-mcp. Launched with behavior-mcp run. Needs 1 environment variable to run.
plonk
Plonk gives agents local macOS tools for windows, workspaces, screenshots, OCR, and more. Runs locally from the plonk-mcp npm package.