Use the notifications inbox
/notifications is the unified inbox for everything that needs your attention. It’s grouped by type, with a link to the full-page list of each kind.
Page layout
- Title: Notifications
- Subtitle: “Items that need your attention.”
- Empty state: ”✓ All clear — nothing needs attention.”
Sections
Agents awaiting activation
Agents in pending status. Each row:
- Agent name
- Time it was registered
- “pending activation” tag
- Activate → button → opens the agent’s page,
/agents/{id}, where Activate agent turns it on
A Go to Agents → link sits in the section header.
Pending uninstall requests
When an MCPB or CLI agent has been deleted locally (npx @agentvalet/register uninstall) but is still active server-side, it appears here:
- Agent name
- Reason (if provided) and request time
- Approve Uninstall (green) → marks the agent revoked server-side
- Reject (red) → keeps the agent active and tells the local install to re-register
Agent self-reports
When agents call report_self_diagnostic (see Read agent self-reports for the full surface):
- Severity badge —
CRIT/ERRO/WARN/INFO - Title and body summary
- Metadata: time, platform, agent ID
- Review → button → opens
/agent-reports(a View all → link sits in the section header)
Agent authorization requests
An agent is granted a connected MCP server that nobody in the organisation has signed in to yet. Each row shows the request and an Authorize → button that opens the consent page for that server, so you can complete the sign-in.
Platform access requests
An agent asked for access to a platform or scope it doesn’t hold. Each row shows the request with Approve and Deny buttons that decide it right here.
Agent registration requests
Registration requests waiting for your decision (the owner-approval path used by MCPB and legacy registrations):
- Agent name
- Requested time + expiry, or “Expired”
- Review → button → goes to
/agents, where you approve or reject it
Tip: notifications versus the queue
Notifications is broad — it surfaces anything that might need attention. The narrower pages (/approvals, /agents, /agent-reports, /anomalies) are where you actually action items.
Treat the inbox as the “did anything happen?” check; treat the action pages as the working surfaces.
Push notifications
If you’re on Team or above and have enabled push, access and authorization requests also reach you via Web Push the moment they’re created. Self-reports come by email instead. The inbox is the catch-up surface for when you’ve missed a notification or come back after a while.