# DAGP documentation (mcpb · dagp-docs-mcp-0.1.0.mcpb)

Read-only DAGP governance rules, agent quickstart and experimental society guides.

- Trust score: 46/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `dagp-docs-mcp-0.1.0.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/martines90-dagp-docs/dagp-docs-mcp.md), [page](https://verifymcp.io/servers/martines90-dagp-docs/dagp-docs-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Martines90/dagp/releases/download/v0.1.0-seed.1/dagp-docs-mcp-0.1.0.mcpb`
- Transport: `stdio`
- SHA-256: `eeb3d872f3f3ab775a2899cb050148fe374986266c406461926e390b0c5e8b19`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 29 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 289 tokens (~19/item across 15 items; 3 tools + 12 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: 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.

## Install

### How do I install the DAGP documentation MCP server?

DAGP documentation ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, eeb3d872f3f3ab775a2899cb050148fe374986266c406461926e390b0c5e8b19; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Martines90/dagp/releases/download/v0.1.0-seed.1/dagp-docs-mcp-0.1.0.mcpb`
- SHA-256: `eeb3d872f3f3ab775a2899cb050148fe374986266c406461926e390b0c5e8b19`

### Verify on macOS / Linux

```bash
echo "eeb3d872f3f3ab775a2899cb050148fe374986266c406461926e390b0c5e8b19  dagp-docs-mcp-0.1.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\dagp-docs-mcp-0.1.0.mcpb).Hash -eq "eeb3d872f3f3ab775a2899cb050148fe374986266c406461926e390b0c5e8b19"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 40, +1)

- [functional improvement] Maintenance: unverified → pass

### 2026-10-23 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `read_document` (~31 tokens)

Read a bundled DAGP document by ID. Call list_documents to discover IDs.

Input parameters:

- `id` (string, required)

### `list_documents` (~19 tokens)

List bundled DAGP protocol, status and starter guides.

### `search_documents` (~30 tokens)

Search bundled documentation for a literal phrase; returns up to ten bounded snippets.

Input parameters:

- `query` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/martines90-dagp-docs/dagp-docs-mcp#diagnostics

## Score history

- 2026-11-05: 46
- 2026-11-04: 46
- 2026-11-03: 45
- 2026-11-02: 45
- 2026-11-01: 44
- 2026-10-31: 44
- 2026-10-30: 43
- 2026-10-29: 43
- 2026-10-28: 42
- 2026-10-27: 42
- 2026-10-26: 41
- 2026-10-25: 41
- 2026-10-24: 40
- 2026-10-23: 39
- 2026-10-22: 38
- 2026-10-21: 36
- 2026-10-20: 36
- 2026-10-19: 36
- 2026-10-18: 36
- 2026-10-17: 36
- 2026-10-16: 36
- 2026-10-15: 36
- 2026-10-14: 36
- 2026-10-13: 9
- 2026-10-12: 9
- 2026-10-10: 9
- 2026-10-09: 9

## Common questions

### What is the DAGP documentation MCP server?

DAGP documentation is an MCP server listed in the public MCP registry as io.github.Martines90/dagp-docs. Read-only DAGP governance rules, agent quickstart and experimental society guides. This page covers its MCPB bundle (https://github.com/Martines90/dagp/releases/download/v0.1.0-seed.1/dagp-docs-mcp-0.1.0.mcpb).

### Is the DAGP documentation MCP server safe to use?

DAGP documentation scores 46 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DAGP documentation MCP server expose?

DAGP documentation exposes 3 tools: read_document, list_documents, search_documents. Their descriptions and schemas cost roughly 80 tokens of context every time the server is loaded.

### What licence is the DAGP documentation MCP server under?

DAGP documentation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the DAGP documentation MCP server?

VerifyMCP ran 12 checks on DAGP documentation, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about DAGP documentation: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/Martines90/dagp
- Changelog RSS feed: https://verifymcp.io/servers/martines90-dagp-docs/dagp-docs-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/martines90-dagp-docs/dagp-docs-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/martines90-dagp-docs/dagp-docs-mcp.json
- HTML version of this page: https://verifymcp.io/servers/martines90-dagp-docs/dagp-docs-mcp