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/tae0y/real-estate-mcpWrote 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/tae0y/real-estate-mcp/context7)<a href="https://agentmods.dev/mcp/tae0y/real-estate-mcp/context7"><img src="https://agentmods.dev/badge/mcp/tae0y/real-estate-mcp/context7/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/tae0y/real-estate-mcp/context7"><img src="https://agentmods.dev/badge/mcp/tae0y/real-estate-mcp/context7.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context7 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 9d 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
{
"context7": {
"command": "npx",
"args": [
"-y",
"@upstash/context7-mcp@latest"
],
"type": "stdio"
}
}What else .mcp.json configures
This page is one entry in a file that holds 6. 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.
- 9d ago First seen · 10 lines scan A a82ed3f65368
context7 is an MCP server published in the GitHub repository tae0y/real-estate-mcp (376 stars, last pushed 1mo 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-30.
Other mcp servers, from other repositories
mcportal
Quota-guarded runtime layer bridging Korean public data APIs (data.go.kr) into the MCP ecosystem. Runs locally from the mcportal Python package.
filesystem
Gives the agent read and write access to a set of allowed directories on the local filesystem. Runs locally from the @modelcontextprotocol/server-filesystem npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
mcp
Korean stocks: median price path after each DART filing type, plus T+1 closes. Remote server at mcp.aikstockdata.com.
manifold
MCP server "manifold" as configured in nonchan7720/manifold. Runs in Docker (ghcr.io/nonchan7720/manifold:v1.9.0). Needs 2 environment variables to run.
pmgs-reference
A local search tool for Japanese Patent Office PMGS data, including definitions and hierarchies for FI, F-term, and IPC patent classifications.