AsDecided
OCI · GHCR.IO/ASDECIDED/CORE:MCP-V0.26.2 · SCANNED AUG 3
Read-only access to deterministic engineering decisions stored in a local repository.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- CVE data not yet available for this package.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency-health data not yet available.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 807 tokens (~134/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 2 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
oci · ghcr.io/asdecided/core:mcp-v0.26.2
claude mcp add asdecided-core -- docker run --rm -i ghcr.io/asdecided/core:mcp-v0.26.2
codex mcp add asdecided-core -- docker run --rm -i ghcr.io/asdecided/core:mcp-v0.26.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"asdecided-core": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/asdecided/core:mcp-v0.26.2"
],
"enabled": true
}
}
} mcp_servers:
asdecided-core:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/asdecided/core:mcp-v0.26.2"] {
"mcpServers": {
"asdecided-core": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/asdecided/core:mcp-v0.26.2"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +26
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 1 Aug 26 9
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed oci/ghcr.io/asdecided/core:mcp-v0.26.2
Provenance none
Ecosystem: oci · Outcome: none
Reason: no_attestation
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
find_decisions ~238
Find the team's already-settled decisions about a topic — or the decisions that govern a specific code path. Call this whenever the user (or you) asks 'what did we decide about X', 'is X ruled out', 'did we already decide this', 'what's our policy on X', or before proposing, changing, or arguing for anything a prior decision might have settled — so you respect recorded decisions instead of re-litigating them. Pass `topic` for a keyword query, or pass `path` (a repository file or directory) to get the decisions whose declared scope governs that code — the recorded decisions that constrain an edit there. Returns the live (Accepted, non-retired) decisions, each with its identifier, title, and path; a topic query ranks by relevance with category and a snippet, a path query reports each decision's status and the matching declared scope. It tells you which decisions bind; read them and judge for yourself — it does not decide whether a change contradicts them. Use get_artifact to read a decision's full text.
| Name | Type | Req | Description |
|---|---|---|---|
| path | — | — | — |
| topic | string | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_artifact ~103
Retrieve one artifact from this repository's recorded product knowledge — a requirement, decision (ADR), design, roadmap, or prompt — by its identifier. Call this whenever an artifact ID is mentioned (for example REQ-001, ADR-012, or a RAC-prefixed ID), and before relying on or changing anything a known requirement or decision covers. Returns the artifact's metadata and full Markdown content.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | — | — |
| id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_related ~122
List the artifacts connected to one artifact in this repository's product knowledge: the references it declares and the artifacts that reference it. Call this after retrieving an artifact, and before changing anything it covers, to find the decisions, requirements, designs, and roadmaps the change could affect. Pass depth>1 (up to 5) to also return a `neighborhood` of artifacts two or more hops out, each tagged with its hop distance, when you need transitive context rather than immediate neighbours.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | — | — |
| id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_summary ~64
Get an overview of this repository's recorded product knowledge: artifact counts by type, validation state, relationship health, and items needing attention. Call this once at the start of a session, before exploring or changing the repository, to learn what recorded knowledge exists and where it needs care.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
retrieve_grounding ~120
One-call grounding for a task from this repository's recorded product knowledge: a ranked, budget-capped set of artifacts with excerpts and provenance, deterministically retrieved. Pass `scope` (a file or directory you will touch) to include the decisions governing that path; superseded matches are replaced by their live successors. Use get_artifact to read an item in full.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | — | — |
| live_only | boolean | — | — |
| scope | string | — | — |
| task | string | yes | — |
| top_k | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
search_artifacts ~142
Search this repository's recorded product knowledge — requirements, decisions (ADRs), designs, roadmaps, and prompts — by keyword. Call this before designing or implementing anything that an existing requirement or prior decision might cover, and whenever the user mentions a feature area, so recorded decisions are respected instead of rediscovered. Optionally pass `tags` to narrow the query to artifacts carrying every given frontmatter tag. Returns matching artifact IDs, types, titles, and paths (plus their tags when tagged); use get_artifact to read a match.
| Name | Type | Req | Description |
|---|---|---|---|
| live_only | boolean | — | — |
| query | string | yes | — |
| tags | — | — | — |
| type | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.