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/tale-project/taleWrote 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/tale-project/tale/convex)<a href="https://agentmods.dev/mcp/tale-project/tale/convex"><img src="https://agentmods.dev/badge/mcp/tale-project/tale/convex/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/tale-project/tale/convex"><img src="https://agentmods.dev/badge/mcp/tale-project/tale/convex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
convex 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
{
"convex": {
"command": "bunx",
"args": [
"convex",
"mcp",
"start",
"--project-dir",
"services/platform"
]
}
}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.
- 1mo ago First seen · 12 lines scan A f58bed85bb61
convex is an MCP server published in the GitHub repository tale-project/tale (35 stars, last pushed today), 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-30.
Other mcp servers, from other repositories
veritasgraph
The first zero-trust, air-gapped Enterprise GraphRAG server for the Model Context Protocol (MCP). Runs locally from the veritasgraph-mcp Python package. Needs 3 environment variables to run.
sentry
Lets the agent search and read Sentry issues, errors and traces, and act on them. Runs locally from the @sentry/mcp-server npm package. Needs 1 environment variable to run.
web-fetcher
MCP server "web-fetcher" as configured in akanthed/SecureAI-Scan. Runs locally from the some-mcp-fetch-server npm package. Needs 1 environment variable to run.
local-dev
MCP server "local-dev", hosted remotely at localhost, as configured in akanthed/SecureAI-Scan.
ideal-harness-guard
MCP server "ideal-harness-guard" as configured in bharat3645/The-Ideal-Harness. Runs dist/guard/cli/index.js with node.
greedy-token
MCP server "greedy-token" as configured in svasenkov/greedy-token. Launched with greedy-token-mcp. Needs 1 environment variable to run.