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/justinwilliames/orbit-for-claudeWrote 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/justinwilliames/orbit-for-claude/braze-lifecycle-mcp)<a href="https://agentmods.dev/mcp/justinwilliames/orbit-for-claude/braze-lifecycle-mcp"><img src="https://agentmods.dev/badge/mcp/justinwilliames/orbit-for-claude/braze-lifecycle-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/justinwilliames/orbit-for-claude/braze-lifecycle-mcp"><img src="https://agentmods.dev/badge/mcp/justinwilliames/orbit-for-claude/braze-lifecycle-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
braze-lifecycle-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 10d 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
2 near-identical copies found in the catalogue:
- orbit-lifecycle-mcp — 92% identical, 4 lines differ
- orbit-for-claude — 89% identical, 4 lines differ
What it actually says
{
"braze-lifecycle-mcp": {
"command": "https://github.com/justinwilliames/orbit-for-claude/releases/download/v0.31.0/orbit-lifecycle-marketing-system-for-claude.mcpb",
"args": [],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 3. 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.
- 10d ago First seen · 7 lines scan A 64719e771588
braze-lifecycle-mcp is an MCP server published in the GitHub repository justinwilliames/orbit-for-claude (0 stars, last pushed today), 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
hubspot-mcp-server
A powerful Model Context Protocol (MCP) server implementation for seamless HubSpot CRM integration, enabling AI assistants to interact with your HubSpot data. Runs locally from the hubspot-mcp-server npm package.
kafka-schema-registry
MCP server "kafka-schema-registry" as configured in aywengo/kafka-schema-reg-mcp. Runs kafka_schema_registry_unified_mcp.py with python. Needs 3 environment variables to run.
thunderbird-cli
Give AI agents full read/write email access via Mozilla Thunderbird. Zero credentials. Runs locally from the thunderbird-cli-mcp npm package. Needs 2 environment variables to run.
lorg-mcp-server
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP. Runs locally from the lorg-mcp-server npm package. Needs 1 environment variable to run.
pushengage-mcp
Send push notifications, build audiences, and view campaign analytics from PushEngage. Runs locally from the @pushengage/mcp npm package. Needs 2 environment variables to run.
mcp-nevent
Talk to your live-events CRM (campaigns, analytics, paid ads, segments) in Claude and ChatGPT. Runs locally from the mcp-nevent npm package. Needs 2 environment variables to run.