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/richer-richard/fenestraInstalling this writes the configuration, not the program: `https://github.com/richer-richard/fenestra/releases/download/fenestra-mcp-v0.40.1/fenestra-mcp-0.40.1-macos-arm64.mcpb` 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/richer-richard/fenestra/fenestra-mcp)<a href="https://agentmods.dev/mcp/richer-richard/fenestra/fenestra-mcp"><img src="https://agentmods.dev/badge/mcp/richer-richard/fenestra/fenestra-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/richer-richard/fenestra/fenestra-mcp"><img src="https://agentmods.dev/badge/mcp/richer-richard/fenestra/fenestra-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fenestra-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 2mo 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
{
"fenestra-mcp": {
"command": "https://github.com/richer-richard/fenestra/releases/download/fenestra-mcp-v0.40.1/fenestra-mcp-0.40.1-macos-arm64.mcpb",
"args": [],
"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.
- 2mo ago First seen · 7 lines scan A 064797a05bb3
fenestra-mcp is an MCP server published in the GitHub repository richer-richard/fenestra (14 stars, last pushed 1mo 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-08-30.
Other mcp servers, from other repositories
dembrandt
Extract design tokens and publicly visible CSS information from any website. Runs locally from the dembrandt npm package.
neuralng
Angular UI expert for NeuralNg discovery, composition, validation, icons and project-aware themes. Runs locally from the @neural-ng/mcp-server npm package.
slack
MCP server "slack" as configured in instructure/instructure-ui. Launched with sh -c set -a; [ -f ./.env ] && . ./.env; set +a; exec npx -y @modelcontextprotoc.
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.
atlassian
MCP server "atlassian", hosted remotely at mcp.atlassian.com, as configured in instructure/instructure-ui.
liquefy-ui
Answers questions about liquefy-ui from its real API surface, so an agent stops inventing props. Runs locally from the @liquefy-ui/mcp npm package.