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/serac-labs/seracWrote 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/serac-labs/serac/servicenow)<a href="https://agentmods.dev/mcp/serac-labs/serac/servicenow"><img src="https://agentmods.dev/badge/mcp/serac-labs/serac/servicenow.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
servicenow 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 7d 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
{
"servicenow": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"--package=@serac-labs/servicenow-mcp",
"servicenow-mcp-stdio"
]
}
}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.
- 7d ago First seen · 11 lines scan A 3c225f9f188b
servicenow is an MCP server published in the GitHub repository serac-labs/serac (78 stars, last pushed 12d 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
packkit-mcp
Scaffold, compose, and upgrade modern multi-language projects as a native tool for AI agents. Runs locally from the packkit-mcp npm package.
src-mcp
MCP server for semantic code search and codebase analysis — Treesitter parsing, AST extraction, and embedding-based indexing for any LLM that supports MCP. Runs locally from the src-mcp npm package.
tilt
MCP server "tilt" as configured in rrmistry/tilt-mcp. Runs in Docker (${HOME}/.tilt-dev:/home/mcp-user/.tilt-dev).
schemabrain
The trust and intelligence layer between AI agents and your database. Runs locally from the schemabrain Python package. Needs 1 environment variable to run.
toolradar
MCP server for Toolradar — search, compare, and get pricing for 8,600+ software tools. Works with Claude Desktop, Claude Code, Cursor, and any MCP-compatible AI assistant. Runs locally from the toolradar-mcp npm package. Needs 1 environment variable to run.
resilireplay
Inject deterministic MCP failures, verify bounded recovery, and generate executable regression tests. Runs locally from the resilireplay npm package.