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/juspay/xyne-spacesInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/juspay/xyne-spaces/xyne-claw)<a href="https://agentmods.dev/mcp/juspay/xyne-spaces/xyne-claw"><img src="https://agentmods.dev/badge/mcp/juspay/xyne-spaces/xyne-claw/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/juspay/xyne-spaces/xyne-claw"><img src="https://agentmods.dev/badge/mcp/juspay/xyne-spaces/xyne-claw.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
xyne-claw 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 16d 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
{
"xyne-claw": {
"command": "node",
"args": [
"packages/xyne-claw-mcp/dist/index.js"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. 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.
- 16d ago First seen · 8 lines scan A b780031939cf
xyne-claw is an MCP server published in the GitHub repository juspay/xyne-spaces (811 stars, last pushed yesterday), 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-10-01.
Other mcp servers, from other repositories
openfoodfacts-mcp-server
Barcode lookup, nutrition search, and product comparison for 3M+ crowd-sourced food products. Runs locally from the @cyanheads/openfoodfacts-mcp-server npm package. Needs 5 environment variables to run.
flashalpha
MCP server "flashalpha", hosted remotely at lab.flashalpha.com, as configured in FlashAlpha-lab/flashalpha-mcp.
pm-copilot
MCP server "pm-copilot" as configured in dkships/pm-copilot. Runs dist/index.js with node.
document-buddy
MCP server "document-buddy" as configured in Hanzhi0807/document-buddy. Runs locally from the document-buddy Python package.
compactprompt
Easy-to-use prompt & data compression for LLM workflows. Runs locally from the compactprompt Python package.
mcp-bash-server
MCP server "mcp-bash-server" as configured in uditk2/mcp-bash-server. Runs locally from the mcp-bash-server Python package.