Church Website Audit by Journey Digital
io.github.tnvolmanPublished by GitHub account tnvolmanv1.0.1Updated Oct 25, 2026
Free church website audit for mobile, speed, SEO, and first-time guests.
The publisher's own server: audit.domains - Domain Valuation
Overview
A local MCP server that sends one church homepage to Journey Digital's free audit service and returns mobile, speed, SEO and first-time-guest checks.
- What you can do
- Audit a church homepage through one tool, audit_church_website, which submits the URL and returns every check with a plain-English finding and cited source per check, plus passed/total counts as the service reports them. Checks cover mobile viewport, zoom and text size; Google PageSpeed mobile performance; SEO basics such as title, meta description, H1, https, canonical, robots.txt and sitemap; and guest-facing items like service times, address, an I'm New path, map or directions, tap-to-call, contact info and giving. Heads-up notes on menu size and labels are reported but never counted as failures. An optional argument leaves off the consultation note; nothing else changes.
- When to use it
- Useful when you want a quick, structured review of a church website's mobile, speed, SEO and visitor-friendliness basics, or when comparing several church homepages. It is a starting checklist, not a ranking guarantee, and subjective points like first-screen placement still need a human look.
- Requirements
- Runs locally over stdio as a Node.js process (Node 18+ per the README, zero dependencies), or as a Docker image. No API key and no declared environment variables; the optional JOURNEY_DIGITAL_AUDIT_BASE_URL overrides the audit origin. Network access to the audit service and Google PageSpeed is required.
Installation
In SourceWeft
- Open Church Website Audit by Journey Digital in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Church Website Audit by Journey Digital
[Church Website Audit score on Glama] [Church Website Audit listing card on Glama] [CI]
A free church website audit tool (an MCP server and Cursor plugin) that checks mobile, page speed, SEO basics, and whether a first-time visitor can find service times.
[Real audit output for https://www.redeemer.com/: 11/21 checks passed]
Real output of audit_church_website for a public church homepage, run 2026-10-21. Finding text is shortened in the image; the full JSON is in docs/example-audit-redeemer.json.
Install
One line, from a clean checkout (Node 18+, zero dependencies). It clones the repo and runs the local self-test:
Then point your MCP client at server/audit-mcp.js (see Usage). In Cursor, the repo also loads as a plugin through .cursor-plugin/plugin.json.
Prefer not to install anything? Run the same church website checker in your browser at journeydigital.ai/audit.
What it checks
One MCP tool, audit_church_website, sends one church homepage to Journey Digital's audit and returns every check:
- Mobile: viewport tag, pinch-to-zoom, text size.
- Speed: Google PageSpeed mobile performance.
- SEO basics: title, meta description, H1, https, canonical link, robots.txt, sitemap.
- First-time guests: service times, street address, an I'm New / Plan a Visit path, map or directions.
- Contact and giving: tap-to-call, contact info, giving one click away.
- About and local identity: beliefs or about link, city in the title or main heading.
- Heads-up notes (never counted as a fail): menu size and menu labels.
Report the result as passed/total exactly as the API returns passed and total. Do not hardcode /21 and do not recompute the counts. Each check comes with a plain-English finding and a cited source for each check. It covers church website SEO basics only and does not guarantee any search ranking. Things like first-screen placement and how easy the phone menu feels still need a human look.
Usage
MCP client config (Claude Desktop, Cursor mcp.json, and similar):
Then ask your agent: "Audit https://example-church.org with audit_church_website."
Tool arguments:
Set JOURNEY_DIGITAL_AUDIT_BASE_URL to use another origin (default https://journeydigital.ai). There is no API key. If the audit service is unreachable or returns a malformed report, the tool returns an error; it never invents results.
Docker
The image speaks MCP over stdio. It is node:22-alpine, installs nothing, and runs as the node user:
Point the MCP client at that command. JOURNEY_DIGITAL_AUDIT_BASE_URL still overrides the origin.
Privacy
The church website address you submit is sent to journeydigital.ai, which fetches that page, and to Google PageSpeed for the speed check. Plugin audits store anonymous counts only. See the privacy policy, terms and PRIVACY.md.
What is in this repo
About
Built and published by Michael McClanahan at Journey Digital, a small church website design studio in Wilson, NC. Questions: [email protected]. Not endorsed by Cursor or Grok Bot.
Contributing
Issues and pull requests are welcome. Keep the server zero-dependency, run node scripts/prove.js before opening a PR, and never hardcode or recompute scores: the tool passes the API's passed and total through unchanged. Notable changes go in CHANGELOG.md.
License
MIT. Copyright 2026 Michael McClanahan.
Source: README.md at commit 6254dd3
Tools
0Version history
2- v1.0.1LatestOct 25, 2026
- v1.0.0Oct 23, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Audit integrations
audit.domains - Domain Valuation
domains.auditOfficial publisher
Deterministic domain-name valuation: fair-value intervals, comparable recorded sales, availability checks, and a verified for-sale listing market.
Revenue Agent — OpenAPI Audit & Change Detection
news.prhOfficial publisher
A remote MCP endpoint that audits OpenAPI specifications and detects API changes, charging $0.10 USDC per analysis via x402 on Base.
SEO Audit & Broken Link Checker
Published by GitHub account prometheus-maker
An Apify-hosted MCP server that audits a website's pages for SEO metadata and finds broken links and images, returning per-page scores.
FinePrint AI Legal Risk & Contract Audit MCP Server
Published by GitHub account RitualDev-Lab
Local in-memory scanner that grades legal contracts, NDAs and leases for risk and drafts redline amendments for coding agents.
Mcp Supply Audit
Published by GitHub account kimmawla
Audits MCP servers as supply-chain artifacts — registry entries, PyPI/npm packages, client configs and tool definitions — using read-only static checks.