Church Website Audit by Journey Digital
MCPB · JD-CHURCH-WEBSITE-AUDIT.MCPB
Free church website audit for mobile, speed, SEO, and first-time guests.
Available components
Last scanned (20 hours ago)
Scores higher than 73% of MCPB servers
Category Marketing and SEO
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 → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- 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).Unverified
- Install-script risk not yet assessed.Unverified
- 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).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 (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 24 Oct 26 0
- Schema quality: 221 → 299 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Tool coverage: 100 functional
- Package version: 1.0.0 → 1.0.1 functional
- 23 Oct 26 36
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 4 Nov 2026 · Analysed mcpb/https://github.com/tnvolman/jd-church-website-audit/releases/download/v1.0.1/jd-church-website-audit.mcpb@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_church_website Audit a church website ~229
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
| Name | Type | Req | Description |
|---|---|---|---|
| include_cta | boolean | – | false omits the consultation note (cta). Omit this argument to keep the service default, which includes cta. |
| url | string | yes | One church homepage, with or without https://. Not a list of pages. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| citations | object | yes | – |
| couldnt | integer | yes | Scored checks the service could not measure. |
| cta | object | – | Consultation note. Absent when include_cta is false. |
| disclaimer | string | yes | Disclaimer text from the service. |
| final_url | string | yes | Address after redirects. |
| groups | array | yes | – |
| js_heavy | boolean | yes | True when the homepage looks JavaScript-heavy. |
| passed | integer | yes | Scored checks the service marked pass. |
| speed_source | string | yes | pagespeed when Google PageSpeed returned a score, otherwise fallback. |
| total | integer | yes | Scored checks in the service's denominator. |
| truncated | boolean | yes | True when the homepage fetch hit the service's byte cap. |
| url | string | yes | Address the service checked. |
No examples provided.
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.
mcpb · jd-church-website-audit.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
2683595ad3565f497a7501fe4ef1de56064f2d010b81c4195e679d5d8a4791ee
macOS / Linux
echo "2683595ad3565f497a7501fe4ef1de56064f2d010b81c4195e679d5d8a4791ee jd-church-website-audit.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\jd-church-website-audit.mcpb).Hash -eq "2683595ad3565f497a7501fe4ef1de56064f2d010b81c4195e679d5d8a4791ee"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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 41 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.