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/DesignPipe/exfigInstalling this writes the configuration, not the program: `./bin/mise` has to be on your PATH already, or the server will not start.
Wrote 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/designpipe/exfig/swiftindex)<a href="https://agentmods.dev/mcp/designpipe/exfig/swiftindex"><img src="https://agentmods.dev/badge/mcp/designpipe/exfig/swiftindex/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/designpipe/exfig/swiftindex"><img src="https://agentmods.dev/badge/mcp/designpipe/exfig/swiftindex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swiftindex 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
{
"swiftindex": {
"type": "stdio",
"command": "./bin/mise",
"args": [
"exec",
"--",
"swiftindex",
"serve"
]
}
}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 · 12 lines scan A dc5ddbefe74b
swiftindex is an MCP server published in the GitHub repository DesignPipe/exfig (10 stars, last pushed 27d 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
figma-desktop
MCP server "figma-desktop", hosted remotely at 127.0.0.1, as configured in naver/design-to-ui.
mobiloop-mcp
MCP server "mobiloop-mcp" as configured in enessubass/mobiloop-mcp. Runs in Docker (ghcr.io/enessubass/mobiloop-mcp:0.1.0-alpha.14). Needs 2 environment variables to run.
phonebook
Self-hosted gallery of your SwiftUI #Preview and Jetpack Compose @Preview screens. Runs locally from the @stag-build/phonebook npm package.
figjam-mcp
MCP server "figjam-mcp" as configured in ecestnrkl/figjam-mcp. Runs locally from the figjam-context-mcp npm package. Needs 4 environment variables to run.
test-genie
AI-powered app test automation for iOS, Android, Flutter, React Native, Web. Runs locally from the test-genie-mcp npm package.
figma-mcp
Allow your AI coding agents to access figma files & prototypes directly. Runs locally from the figma-mcp Python package.