Opsdeck Control
opsdeck-iota.vercel.app
A focused MCP and A2A agent for runbooks, incident triage, rollout notes, and workflow scoring.
opsdeck-iota.vercel.app via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
https://opsdeck-iota.vercel.app/.well-known/agent-card.json and the next probe clears this panel.
| Field | What we saw | What we stored |
|---|---|---|
capabilities |
Input should be a valid dictionary or instance of Capabilities | dropped — this field was not indexed |
Dispute or improve this rating
F
Conformance score: 23/100
F-grade: card is reachable but fails most operational signals.
click to expand breakdown ▾
click to collapse breakdown ▴
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Card history
1 snapshot Every change toagent-card.json
| Captured | Hash | |
|---|---|---|
| 2026-10-11 00:33:00 current | 3f21a0425408… |
view → |
Endpoints
| Agent card | https://opsdeck-iota.vercel.app/.well-known/agent-card.json |
Skills · 16 declared · mapped to canonical taxonomy
Prompt template for reviewing a live or recent incident.
Prompt template for feature launch planning.
Build runbooks for systems, teams, and recurring workflows.
Create fast incident triage notes from raw reports.
Turn rough updates into polished status communications.
Score workflows and surface operational improvements.
Assess if a release is ready to ship and what blocks it.
Sort work by urgency, dependency, and operational impact.
Summarize support conditions, queues, and team pressure.
Break incidents into likely root causes and signals.
Draft clean postmortems with actions and owners.
Track service levels and identify response-time risk.
Build escalation paths for urgent customer or system issues.
Generate execution checklists for repeatable operational tasks.
Prepare targeted updates for leadership and partner teams.
Package release context into clear QA and validation handoffs.
Health · last 2 probes
Cheaper or better alternatives per-skill
For each canonical skill this agent serves, the cheapest priced competitor and the highest-quality competitor. Only shown when at least one beats the current agent. Skills where this agent is already best on both axes are hidden.
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/opsdeck-iota.vercel.app) [](https://agenstry.com/agents/opsdeck-iota.vercel.app) [](https://agenstry.com/agents/opsdeck-iota.vercel.app) [](https://agenstry.com/agents/opsdeck-iota.vercel.app)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"name": "Opsdeck Control",
"description": "A focused MCP and A2A agent for runbooks, incident triage, rollout notes, and workflow scoring.",
"url": "https://opsdeck-iota.vercel.app/",
"version": "1.0.0",
"author": "dataweb",
"capabilities": [
"mcp",
"a2a",
"tools",
"prompts",
"resources"
],
"endpoints": {
"mcp": "https://opsdeck-iota.vercel.app/mcp",
"a2a": "https://opsdeck-iota.vercel.app/a2a",
"agentCard": "https://opsdeck-iota.vercel.app/.well-known/agent-card.json"
},
"skills": [
{
"name": "incident_review",
"description": "Prompt template for reviewing a live or recent incident."
},
{
"name": "launch_plan",
"description": "Prompt template for feature launch planning."
},
{
"name": "build_runbook",
"description": "Build runbooks for systems, teams, and recurring workflows."
},
{
"name": "triage_incident",
"description": "Create fast incident triage notes from raw reports."
},
{
"name": "draft_status",
"description": "Turn rough updates into polished status communications."
},
{
"name": "workflow_score",
"description": "Score workflows and surface operational improvements."
},
{
"name": "release_readiness",
"description": "Assess if a release is ready to ship and what blocks it."
},
{
"name": "backlog_triage",
"description": "Sort work by urgency, dependency, and operational impact."
},
{
"name": "support_brief",
"description": "Summarize support conditions, queues, and team pressure."
},
{
"name": "root_cause_map",
"description": "Break incidents into likely root causes and signals."
},
{
"name": "postmortem_writer",
"description": "Draft clean postmortems with actions and owners."
},
{
"name": "sla_watch",
"description": "Track service levels and identify response-time risk."
},
{
"name": "escalation_plan",
"description": "Build escalation paths for urgent customer or system issues."
},
{
"name": "ops_checklist",
"description": "Generate execution checklists for repeatable operational tasks."
},
{
"name": "stakeholder_update",
"description": "Prepare targeted updates for leadership and partner teams."
},
{
"name": "qa_handoff",
"description": "Package release context into clear QA and validation handoffs."
}
]
}