Read Scorecard evaluation projects, then run API changes as approved steps
Connect Scorecard MCP and your agent can look up how the SDK works before it touches anything. Search the documentation for the right method and parameters, then run JavaScript against the Scorecard API to manage projects, testsets, testcases, systems, metrics, runs, records, scores, and annotations. Luumen authenticates with OAuth via dynamic client registration.
2 tools: 1 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Scorecard MCP run looks like inside Luumen.
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — execute — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Scorecard MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.