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/jrlingyin888/SwiftNewModulesWrote 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/jrlingyin888/swiftnewmodules/swiftforge)<a href="https://agentmods.dev/mcp/jrlingyin888/swiftnewmodules/swiftforge"><img src="https://agentmods.dev/badge/mcp/jrlingyin888/swiftnewmodules/swiftforge/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/jrlingyin888/swiftnewmodules/swiftforge"><img src="https://agentmods.dev/badge/mcp/jrlingyin888/swiftnewmodules/swiftforge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swiftforge 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
{
"swiftforge": {
"command": "npx",
"args": [
"-y",
"swiftforge-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.
- 1mo ago First seen · 10 lines scan A 27f6366bc652
swiftforge is an MCP server published in the GitHub repository jrlingyin888/SwiftNewModules (0 stars, last pushed 4mo 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
storybook-react-native-mcp
MCP server "storybook-react-native-mcp", hosted remotely at localhost, as configured in MetaMask/metamask-design-system.
figma
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot. Runs locally from the figma-developer-mcp npm package. Needs 1 environment variable to run.
apple-dev-mcp
Complete Apple development guidance: Human Interface Guidelines (design) + Technical Documentation for iOS, macOS, watchOS, tvOS, and visionOS. Runs locally from the apple-dev-mcp npm package.
mcp-figma-to-code
MCP server for converting Figma designs to React Native components. Runs locally from the @kailashg101/mcp-figma-to-code npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.