An agent can connect on its own if it already holds OPSERA_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: opsera_mappings (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); opsera_users (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); opsera_groups (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
pass
tools.token_costabout 4,211 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump
stability75 · weight 15
warn
stability.changes6 tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package
11 tools, about 4,211 tokens to load them all · tool set 5c17a1f289a7 · tools last changed 2026-10-09 · checked 2026-10-20 12:13 UTC
Tool changes
opsera_pipelineschangedinput schema
opsera_pipelineschangedinput schema
opsera_pipelineschangedinput schema
opsera_userschangeddescription, input schema
before
User management: get_current, get, list, create, delete. See docs/API_REFERENCE.md.
after · 75% of words in common
User management: get_current, get, list (optional active=true|false), create, delete. See docs/API_REFERENCE.md.
opsera_pipelineschangedinput schema
opsera_pipeline_parametersadded
Pipeline parameters: reusable, configurable key-value pairs scoped to a pipeline. Parameters can be referenced by pipeline steps during execution for dynamic configuration (environment variables, secrets, build flags, deployment targets). Use list to see all parameters for a pipeline before triggering a run. Use create/update to set runtime values. Use get_value for lightweight value retrieval. Parameter types: string (default), number, boolean, secret (masked in logs). See docs/API_REFERENCE.md.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://agent.opsera.io/mcpsse
api_key ${OPSERA_TOKEN}
yes
100%
359 ms
2025-11-25
2026-10-20
Tools (11)
opsera_groups
Group management: list, get, create, delete, get_memberships, add/remove/patch members. See docs/API_REFERENCE.md.
opsera_insights
Insights: dashboards, filters, audit logs, KPIs, tool mappings. See docs/API_REFERENCE.md for all operations.
opsera_mappings
Data mappings: list, get, create, update. See docs/API_REFERENCE.md.
opsera_pipeline_parameters
Pipeline parameters: reusable, configurable key-value pairs scoped to a pipeline. Parameters can be referenced by pipeline steps during execution for dynamic configuration (environment variables, secrets, build flags, deployment targets). Use list to see all parameters for a pipeline before triggering a run. Use create/update to set runtime values. Use get_value for lightweight value retrieval. Parameter types: string (default), number, boolean, secret (masked in logs). See docs/API_REFERENCE.md.
opsera_pipelines
Pipelines: monitor runs, security audit, run duration stats, configuration, templates, and lifecycle actions. Execution questions (image tag, artifact, commit SHA): list_runs then get_run (view=artifacts by default). Do not call get afterward. security_audit: find pipelines with disabled security steps; set includeStats=true to include each pipeline average/min/max run duration. runs_stats: average/min/max run duration for one pipelineId or batch pipelineIds (no security filter). get with view=security audits one known pipeline; get without view is full config (large). list is a lightweight catalog. list_runs is recent run timing. action runs mutations. See docs/API_REFERENCE.md.
opsera_projects
Projects: list, get, create, update. See docs/API_REFERENCE.md for operations.
opsera_reports_and_logs
Reports and logs: reports_tasks_created, reports_pipelines_created, logs_audit_user, logs_task. See docs/API_REFERENCE.md.
opsera_search_data_settings
Cross-entity discovery and platform settings. search finds pipeline, task, or registry records by name or ID and returns lightweight metadata only — not execution history, artifacts, durations, or full stage configuration (use opsera_pipelines for those). org_hierarchy and settings_tasks for organizational mapping and task configuration updates. See docs/API_REFERENCE.md.
opsera_tasks
Tasks: list, create, status, lookup; lifecycle mutations via operation=action (run, stop, create, update, status). See docs/API_REFERENCE.md.
opsera_tools
Tools & registry: identifiers, registry, scm_repositories, scm_branches, registry_configurations. See docs/API_REFERENCE.md.
opsera_users
User management: get_current, get, list (optional active=true|false), create, delete. See docs/API_REFERENCE.md.