Sermon Registry
REMOTE · SERMONREGISTRY.COM
Search sermons and churches by topic, Bible book, preacher or place. Read-only, with links.
Available components
Last scanned (17 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 405 tokens (~101/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 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.
- 19 Nov 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.
- 18 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 72
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 21 Nov 2026 · Probed https://sermonregistry.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sermonregistry.com | CN=YE1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 62be14866b202f63304c8b40134f2b77a0a |
| SANs: *.sermonregistry.com, sermonregistry.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sermonregistry.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| sermonregistry.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://static.cloudflareinsights.com https://www.youtube.com https://*.googletagmanager.com https://maps.googleapis.com https://maps.gstatic.com https://relay.sermonregistry.com https://invitejs.trustpilot.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https://mojngmbgxcvpoimvbdgl.supabase.co https://*.supabase.co https://tile.openstreetmap.org https://basemaps.cartocdn.com https://tiles.basemaps.cartocdn.com https://i.ytimg.com https://*.google-analytics.com https://*.googletagmanager.com https://www.google.com https://maps.googleapis.com https://maps.gstatic.com; media-src 'self' https:; frame-src https://www.youtube.com https://www.youtube-nocookie.com https://challenges.cloudflare.com; connect-src 'self' https://mojngmbgxcvpoimvbdgl.supabase.co |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sermonregistry.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://sermonregistry.com/api/mcp | HTTPS enforced | 301 | https://sermonregistry.com/api/mcp |
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 →
find_churches Find churches ~81
Find churches listed on Sermon Registry by name, city, country or denomination, with links to their profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| country | string | – | – |
| denomination | string | – | – |
| page | integer | – | – |
| pageSize | integer | – | – |
| query | string | – | Words in the church's name. |
No output schema declared.
No examples provided.
get_sermon Get a sermon ~62
One published sermon's details: Sermon Registry's summary and takeaways, preacher, church, date, topics, Bible passages and links. No transcript text.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The sermon's slug: the last part of its sermonregistry.com URL. |
No output schema declared.
No examples provided.
list_topics List topics ~25
Every sermon topic id with its name and group, for use with search_sermons.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_sermons Search sermons ~158
Search published sermons by keywords, topics, Bible book, preacher, church or language. Returns titles, preachers, churches, dates, topics, main Bible passages and links; never transcripts.
| Name | Type | Req | Description |
|---|---|---|---|
| bookId | string | – | A Bible book id such as ROM, JHN or PSA. |
| church | string | – | A church's name. |
| language | string | – | Sermons available to read in this language. |
| page | integer | – | – |
| pageSize | integer | – | – |
| preacher | string | – | A preacher's name. |
| query | string | – | Words to search for in sermon titles, summaries and takeaways. |
| topics | array | – | Topic ids from list_topics; a sermon must have all of them. |
No output schema declared.
No examples provided.
How do I install the Sermon Registry MCP server?
Sermon Registry is a hosted endpoint at https://sermonregistry.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sermonregistry.com
claude mcp add --transport http com-sermonregistry-sermon-registry 'https://sermonregistry.com/api/mcp'
What is the Sermon Registry MCP server?
Sermon Registry is an MCP server listed in the public MCP registry as com.sermonregistry/sermon-registry. Search sermons and churches by topic, Bible book, preacher or place. Read-only, with links. This page covers its hosted endpoint (https://sermonregistry.com/api/mcp).
Is the Sermon Registry MCP server safe to use?
Sermon Registry scores 74 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 Sermon Registry MCP server expose?
Sermon Registry exposes 4 tools: search_sermons, get_sermon, find_churches, list_topics. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.
Does the Sermon Registry MCP server require authentication?
No. We connected to Sermon Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sermon Registry MCP server still maintained?
Sermon Registry is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Sermon Registry MCP server?
VerifyMCP ran 13 checks on Sermon Registry, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.