# Church Website Audit by Journey Digital (mcpb · jd-church-website-audit.mcpb)

Free church website audit for mobile, speed, SEO, and first-time guests.

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

## Components

- mcpb · `jd-church-website-audit.mcpb`: 42/100 (this document), [markdown](https://verifymcp.io/servers/tnvolman-jd-church-website-audit/jd-church-website-audit.md), [page](https://verifymcp.io/servers/tnvolman-jd-church-website-audit/jd-church-website-audit)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/tnvolman/jd-church-website-audit/releases/download/v1.0.1/jd-church-website-audit.mcpb`
- Version: `1.0.1`
- Transport: `stdio`
- SHA-256: `2683595ad3565f497a7501fe4ef1de56064f2d010b81c4195e679d5d8a4791ee`

## 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 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 299 tokens (~299/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; 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 Church Website Audit by Journey Digital MCP server?

Church Website Audit by Journey Digital 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, 2683595ad3565f497a7501fe4ef1de56064f2d010b81c4195e679d5d8a4791ee; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/tnvolman/jd-church-website-audit/releases/download/v1.0.1/jd-church-website-audit.mcpb`
- SHA-256: `2683595ad3565f497a7501fe4ef1de56064f2d010b81c4195e679d5d8a4791ee`

### Verify on macOS / Linux

```bash
echo "2683595ad3565f497a7501fe4ef1de56064f2d010b81c4195e679d5d8a4791ee  jd-church-website-audit.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\jd-church-website-audit.mcpb).Hash -eq "2683595ad3565f497a7501fe4ef1de56064f2d010b81c4195e679d5d8a4791ee"
```

## 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-05 (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-11-03 (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-11-01 (score 40, +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.

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

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

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

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

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

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

### 2026-10-24 (score 36, 0)

- [functional regression] Schema quality: 221 → 299
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Tool coverage: 100
- [functional] Package version: 1.0.0 → 1.0.1

### 2026-10-23 (score 36)

First indexed and scored.

## MCP tools (1)

### `audit_church_website` (~229 tokens)

Audit a church website

Audits one church homepage for mobile fit, speed, SEO basics, and first-time-guest findability, and returns Journey Digital's report unchanged. Use it when the user gives one church website address. Do not use it to crawl a site, to promise a search ranking, or when no address was given. Sends that address to journeydigital.ai, which fetches the page, and the speed check to Google PageSpeed. No API key. Plugin audits store an anonymous count, so repeating the call records another count, and the church website itself is not modified. If the service is unreachable, rate-limited, or the report is malformed, the result is an error and includes no checks. Privacy: https://journeydigital.ai/privacy Terms: https://journeydigital.ai/terms

Input parameters:

- `include_cta` (boolean): false omits the consultation note (cta). Omit this argument to keep the service default, which includes cta.
- `url` (string, required): One church homepage, with or without https://. Not a list of pages.

Output parameters:

- `checks` (array)
- `citations` (object)
- `couldnt` (integer): Scored checks the service could not measure.
- `cta` (object): Consultation note. Absent when include_cta is false.
- `disclaimer` (string): Disclaimer text from the service.
- `final_url` (string): Address after redirects.
- `groups` (array)
- `js_heavy` (boolean): True when the homepage looks JavaScript-heavy.
- `passed` (integer): Scored checks the service marked pass.
- `speed_source` (string): pagespeed when Google PageSpeed returned a score, otherwise fallback.
- `total` (integer): Scored checks in the service's denominator.
- `truncated` (boolean): True when the homepage fetch hit the service's byte cap.
- `url` (string): Address the service checked.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/tnvolman-jd-church-website-audit/jd-church-website-audit#diagnostics

## Score history

- 2026-11-05: 42
- 2026-11-04: 41
- 2026-11-03: 41
- 2026-11-02: 40
- 2026-11-01: 40
- 2026-10-31: 39
- 2026-10-30: 39
- 2026-10-29: 38
- 2026-10-28: 38
- 2026-10-27: 38
- 2026-10-26: 37
- 2026-10-25: 37
- 2026-10-24: 36
- 2026-10-23: 36

## Common questions

### What is the Church Website Audit by Journey Digital MCP server?

Church Website Audit by Journey Digital is an MCP server listed in the public MCP registry as io.github.tnvolman/jd-church-website-audit. Free church website audit for mobile, speed, SEO, and first-time guests. This page covers its MCPB bundle (https://github.com/tnvolman/jd-church-website-audit/releases/download/v1.0.1/jd-church-website-audit.mcpb).

### Is the Church Website Audit by Journey Digital MCP server safe to use?

Church Website Audit by Journey Digital scores 42 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 Church Website Audit by Journey Digital MCP server expose?

Church Website Audit by Journey Digital exposes 1 tool: audit_church_website. Their descriptions and schemas cost roughly 229 tokens of context every time the server is loaded.

### What licence is the Church Website Audit by Journey Digital MCP server under?

Church Website Audit by Journey Digital declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/tnvolman/jd-church-website-audit
- Website: https://journeydigital.ai/audit
- Changelog RSS feed: https://verifymcp.io/servers/tnvolman-jd-church-website-audit/jd-church-website-audit.xml
- Changelog JSON feed: https://verifymcp.io/servers/tnvolman-jd-church-website-audit/jd-church-website-audit.json
- HTML version of this page: https://verifymcp.io/servers/tnvolman-jd-church-website-audit/jd-church-website-audit