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/tunahanaliozturk/partner-center-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/tunahanaliozturk/partner-center-mcp/mcp-partner-center-mcp)<a href="https://agentmods.dev/mcp/tunahanaliozturk/partner-center-mcp/mcp-partner-center-mcp"><img src="https://agentmods.dev/badge/mcp/tunahanaliozturk/partner-center-mcp/mcp-partner-center-mcp/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/tunahanaliozturk/partner-center-mcp/mcp-partner-center-mcp"><img src="https://agentmods.dev/badge/mcp/tunahanaliozturk/partner-center-mcp/mcp-partner-center-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
partner-center-mcp 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- hemnet-mcp — 88% identical, 4 lines differ
What it actually says
{
"partner-center-mcp": {
"command": "npx",
"args": [
"-y",
"partner-center-mcp"
],
"env": {}
}
}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.
- 12d ago First seen · 10 lines scan A 3dae3964f334
partner-center-mcp is an MCP server published in the GitHub repository tunahanaliozturk/partner-center-mcp (2 stars, last pushed 5d 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
membridge
Cross-platform, cross-process shared memory with rwlock and SPSC ring buffer for Python, powered by Rust. Runs locally from the membridge Python package.
runecho
MCP server "runecho" as configured in inth3shadows/runecho. Launched with ${RUNECHO_MCP_COMMAND:-runecho-mcp}.
openapi-anything
MCP server "openapi-anything" as configured in schniggie/openapi-anything. Runs locally from the openapi-anything Python package.
rts
MCP server "rts" as configured in njfio/rs-agent-code-utility. Launched with rts-mcp --workspace ${CLAUDE_PROJECT_DIR:-.}. Needs 2 environment variables to run.
slipstream
Shared distillation cache for AI agents — every fetch 73-89% fewer tokens via a shared cache. Remote server at slipstream-pi.vercel.app.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.