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/LayerCall/layercall-sdkWrote 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/layercall/layercall-sdk/trust-api)<a href="https://agentmods.dev/mcp/layercall/layercall-sdk/trust-api"><img src="https://agentmods.dev/badge/mcp/layercall/layercall-sdk/trust-api/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/layercall/layercall-sdk/trust-api"><img src="https://agentmods.dev/badge/mcp/layercall/layercall-sdk/trust-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trust-api 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
{ "trust-api": { "url": "https://www.layercall.com/api/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 b05b5eb56151
trust-api is an MCP server published in the GitHub repository LayerCall/layercall-sdk (0 stars, last pushed 23d 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
xupersplit
Split shared expenses in a group — no account needed. See who owes whom and settle up. Remote server at split.xuper.fun.
stripekit
The create-next-app of Stripe. Declarative catalog reconciliation into your own Stripe account, plus correct-by-construction billing code you own. Runs locally from the stripekit npm package.
cryptodata-mcp
CryptoData MCP Server - Real-time crypto market data, DeFi analytics, and on-chain intelligence... Runs locally from the cryptodata-mcp npm package.
defiguard-mcp
DeFiGuard MCP Server - DeFi protocol risk analysis tools for AI coding agents. Analyze token co... Runs locally from the defiguard-mcp npm package.
vaultguard-mcp
VaultGuard MCP Server - Yearn V3 / DeFi vault security and analysis tools for AI coding agents.... Runs locally from the vaultguard-mcp npm package.
looktwice
MCP server for the LookTwice API: email, EU VAT, IBAN, and domain validation plus evidence-backed CPSC recall screening from any MCP client. Runs locally from the looktwice-mcp npm package. Needs 1 environment variable to run.