Ops (uluops) MCP Server
@uluops/ops-mcp
npm
v0.11.0
Published by @uluops — 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.
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 − 4 = 96. 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 |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −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 50
Each tool and what it can reach — statically extracted from the published source.
create_issuenetwork egressadd_issue_noteno sensitive capabilityarchive_runsno sensitive capabilitybulk_update_statusno sensitive capabilitycreate_projectno sensitive capabilitydelete_projectno sensitive capabilitydelete_runno sensitive capabilitydiff_runsno sensitive capabilityedit_issueno sensitive capabilityget_agent_lifecycleno sensitive capability
Show 40 more tools ↓
get_agent_matrixno sensitive capabilityget_agent_reliabilityno sensitive capabilityget_agent_runs_analysisno sensitive capabilityget_analyticsno sensitive capabilityget_burndownno sensitive capabilityget_discoveryno sensitive capabilityget_full_taxonomy_analyticsno sensitive capabilityget_issue_by_fingerprintno sensitive capabilityget_issue_detailsno sensitive capabilityget_issue_historyno sensitive capabilityget_latest_runno sensitive capabilityget_projectno sensitive capabilityget_project_analysisno sensitive capabilityget_project_summaryno sensitive capabilityget_project_trendsno sensitive capabilityget_runno sensitive capabilityget_run_analysisno sensitive capabilityget_run_detailsno sensitive capabilityget_taxonomyno sensitive capabilityget_velocityno sensitive capabilitylist_agentsno sensitive capabilitylist_projectsno sensitive capabilitylist_runsno sensitive capabilitymerge_issuesno sensitive capabilitymerge_projectsno sensitive capabilityquery_analysis_recordsno sensitive capabilityquery_issuesno sensitive capabilityrestore_issueno sensitive capabilityrestore_projectno sensitive capabilitysave_runno sensitive capabilitysearch_issuesno sensitive capabilitysoft_delete_issueno sensitive capabilitysoft_delete_projectno sensitive capabilityundo_issue_statusno sensitive capabilityupdate_issue_by_fingerprintno sensitive capabilityupdate_profileno sensitive capabilityupdate_projectno sensitive capabilityupdate_runno sensitive capabilityupdate_statusno sensitive capabilityvalidate_runno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (50 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.11.0 latest |
A 96/100 | 0 | 1.10.0 | 2026-07-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 @uluops/ops-mcp --onlineOther implementations of Ops 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.