Splunk Oncall MCP Server
mcp-server-splunk-oncall
PyPI
v0.4.0
Published by arnstarn — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Splunk On-Call (VictorOps) incident management
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 46
Each tool and what it can reach — statically extracted from the published source.
acknowledge_all_incidentsno sensitive capabilityacknowledge_incidentsno sensitive capabilityadd_team_memberno sensitive capabilitycreate_maintenanceno sensitive capabilitycreate_policyno sensitive capabilitycreate_routing_keyno sensitive capabilitycreate_teamno sensitive capabilitycreate_userno sensitive capabilitydelete_policyno sensitive capabilitydelete_routing_keyno sensitive capability
Show 36 more tools ↓
delete_teamno sensitive capabilitydelete_userno sensitive capabilityend_maintenanceno sensitive capabilityget_access_modeno sensitive capabilityget_alertno sensitive capabilityget_incident_historyno sensitive capabilityget_incident_timelineno sensitive capabilityget_maintenanceno sensitive capabilityget_oncallno sensitive capabilityget_oncall_reportno sensitive capabilityget_org_infono sensitive capabilityget_org_timelineno sensitive capabilityget_policyno sensitive capabilityget_teamno sensitive capabilityget_team_adminsno sensitive capabilityget_team_membersno sensitive capabilityget_team_oncall_scheduleno sensitive capabilityget_team_policiesno sensitive capabilityget_userno sensitive capabilityget_user_contact_methodsno sensitive capabilityget_user_devicesno sensitive capabilityget_user_oncall_scheduleno sensitive capabilityget_user_policiesno sensitive capabilityget_user_teamsno sensitive capabilitylist_alertsno sensitive capabilitylist_incidentsno sensitive capabilitylist_maintenanceno sensitive capabilitylist_policiesno sensitive capabilitylist_routing_keysno sensitive capabilitylist_teamsno sensitive capabilitylist_usersno sensitive capabilityremove_team_memberno sensitive capabilityreroute_incidentsno sensitive capabilityresolve_all_incidentsno sensitive capabilityresolve_incidentsno sensitive capabilityupdate_teamno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (46 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.4.0 latest |
A 99/100 | 0 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-server-splunk-oncall --online --registry pypiMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.