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/sinch/sinch-pluginsWrote 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/sinch/sinch-plugins/sinch-claude-plugin-sinch)<a href="https://agentmods.dev/mcp/sinch/sinch-plugins/sinch-claude-plugin-sinch"><img src="https://agentmods.dev/badge/mcp/sinch/sinch-plugins/sinch-claude-plugin-sinch.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sinch 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 6d 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
{
"sinch": {
"command": "npx",
"args": [
"-y",
"@sinch/mcp"
],
"env": {
"CONVERSATION_PROJECT_ID": "${CONVERSATION_PROJECT_ID}",
"CONVERSATION_KEY_ID": "${CONVERSATION_KEY_ID}",
"CONVERSATION_KEY_SECRET": "${CONVERSATION_KEY_SECRET}",
"CONVERSATION_REGION": "${CONVERSATION_REGION}",
"CONVERSATION_APP_ID": "${CONVERSATION_APP_ID}"
}
}
}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.
- 6d ago First seen · 16 lines scan A 15e2b392f075
sinch is an MCP server published in the GitHub repository sinch/sinch-plugins (6 stars, last pushed 24d 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
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
bigquery
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
webhook
Receive, inspect, replay and deliver webhooks — with signature verification and agent triggers. Remote server at mcp.webhook.co.
api2mcp
Serve any OpenAPI 3.x / Swagger 2.x API as a local MCP (Model Context Protocol) server over stdio, proxying tool calls to the upstream HTTP API. Runs locally from the @swayam5342/api2mcp npm package.
ytdl-rmcp
yt-dlp search, download, metadata, delivery, and Plex workflows over MCP and CLI. Runs locally from the @dinglebear/rytdl npm package. Needs 28 environment variables to run.
mcpify
CLI tool that generates an MCP server from OpenAPI specs automatically. Runs locally from the @bahridev/mcpify npm package.