Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Alkilo-do/orita-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/alkilo-do/orita-mcp/orita-provider-resolution)<a href="https://agentmods.dev/mcp/alkilo-do/orita-mcp/orita-provider-resolution"><img src="https://agentmods.dev/badge/mcp/alkilo-do/orita-mcp/orita-provider-resolution/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/alkilo-do/orita-mcp/orita-provider-resolution"><img src="https://agentmods.dev/badge/mcp/alkilo-do/orita-mcp/orita-provider-resolution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
orita-provider-resolution scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "orita-provider-resolution": { "command": "uvx", "args": [ "orita-mcp" ], "env": { "ORITA_API_KEY": "" } } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 11 lines scan A 018b0392cabe
orita-provider-resolution is an MCP server published in the GitHub repository Alkilo-do/orita-mcp (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
agentdraft-mcp
MCP server for AgentDraft — expose inbox, conflict-free calendar, and audit tools to MCP-aware AI clients. Runs locally from the agentdraft-mcp Python package. Needs 2 environment variables to run.
smartsuite
MCP server "smartsuite" as configured in SmartSuiteFoundry/smartsuite-mcp-server. Launched with smartsuite-mcp. Needs 4 environment variables to run.
astravue-mcp
Manage projects, tasks, time tracking, and team collaboration through natural language. Remote server at api.astravue.com.
plane-workflow
MCP server "plane-workflow" as configured in amirhosseinkz/plane-workflow-mcp. Runs locally from the plane-workflow Python package.
planfix
MCP server for Planfix — tasks, contacts, project management (Russia). Runs locally from the @theyahia/planfix-mcp npm package. Needs 2 environment variables to run.
swsd
MCP server for SolarWinds Service Desk tickets, catalog, knowledge, ITSM operations, and workflows. Runs locally from the swsd-mcp npm package. Needs 5 environment variables to run.