Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rakutentech/sorify/plugin install sorifyWrote 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/rakutentech/sorify/sorify-sorify)<a href="https://agentmods.dev/mcp/rakutentech/sorify/sorify-sorify"><img src="https://agentmods.dev/badge/mcp/rakutentech/sorify/sorify-sorify/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/rakutentech/sorify/sorify-sorify"><img src="https://agentmods.dev/badge/mcp/rakutentech/sorify/sorify-sorify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sorify 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
{
"sorify": {
"type": "http",
"url": "${SORIFY_URL}/mcp",
"headersHelper": "${CLAUDE_PLUGIN_ROOT}/scripts/mcp-auth-headers.sh",
"http_headers_helper": "${PLUGIN_ROOT}/scripts/mcp-auth-headers.sh"
}
}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 · 8 lines scan A a95c0e3068a4
sorify is an MCP server published in the GitHub repository rakutentech/sorify (50 stars, last pushed 4d 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-09-16.
Other mcp servers, from other repositories
vibe-testing
Code-aware browser testing agent — 14 Playwright tools for AI code editors via MCP. Runs locally from the vibe-testing npm package.
dsh-verify
Agent-built web app quality gate. Real browser is the judge. PASS/FAIL with receipts. Runs locally from the dsh-verify npm package.
five46
BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success. Runs locally from the five46 npm package. Needs 5 environment variables to run.
beforeusersdo
Browser-backed QA with evidence and fix-ready reports for coding agents. Remote server at mcp.beforeusersdo.com.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
browser
MCP server "browser" as configured in felipebarcelospro/igniter-js. Launched with npx @playwright/mcp@latest.