io.github.itsryanarmani/petcremation
REMOTE · PETCREMATION.FYI
Find pet crematories near you and compare what they publish.
Available components
Last scanned (19 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security69
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 689 tokens (~62/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 12 Nov 26 +1
- Tool “get_course” changed its title: Get Course cosmetic
- Tool “get_listing” changed its title: Get Listing cosmetic
- Tool “get_product” changed its title: Get Product cosmetic
- Tool “get_stats” changed its title: Get Stats cosmetic
- Tool “list_categories” changed its title: List Categories cosmetic
- Tool “list_courses” changed its title: List Courses cosmetic
- Tool “list_places” changed its title: List Places cosmetic
- Tool “list_product_categories” changed its title: List Product Categories cosmetic
- Tool “list_products” changed its title: List Products cosmetic
- Tool “list_sources” changed its title: List Sources cosmetic
- Tool “search_listings” changed its title: Search Listings cosmetic
11 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
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://petcremation.fyi/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=petcremation.fyi | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | df9151d997c7243a132b4c61a11fae5f |
| SANs: petcremation.fyi, admin.petcremation.fyi, *.admin.petcremation.fyi | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of petcremation.fyi. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fyi. | DS published | 6839 | 8 | Verified |
| petcremation.fyi. | 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=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://js.stripe.com https://*.googletagmanager.com https://connect.facebook.net https://www.redditstatic.com https://*.clarity.ms; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://neeed.directory https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://www.facebook.com https://alb.reddit.com https://*.clarity.ms https://c.bing.com; font-src 'self' data:; connect-src 'self' https://challenges.cloudflare.com https://api.stripe.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://www.facebook.com https://connect.facebook.net https://www.redditstatic.com https://alb.reddit.com https://pixel-config.reddit.com https://ads.reddit.com https://*.clarity.ms https://c.bing.com; frame-src https://challenges.cloudflare.com https://js.stripe.com; worker-src 'self' blob:; media-src 'self' blob:; manifest-src 'self'; objec |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://petcremation.fyi/mcp | Verified | 200 | |
| http (plaintext) | http://petcremation.fyi/mcp | Inconclusive | 405 |
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 →
get_course Get Course ~43
Get one published academy course by its slug, with its objectives, lessons and FAQ. Exam questions and answers are never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The course slug. |
No output schema declared.
No examples provided.
get_listing Get Listing ~28
Get one published pet crematory by its slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The listing slug. |
No output schema declared.
No examples provided.
get_product Get Product ~33
Get one affiliate product by its slug, with its page and outbound link.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The product slug. |
No output schema declared.
No examples provided.
get_stats Get Stats ~28
Get the number of published pet crematories, places and categories, and when the data last changed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_categories List Categories ~17
List categories with their pet crematory counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_courses List Courses ~48
List the published academy courses with their level, length, pass mark and certificate validity.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Only courses of this level. |
| limit | integer | – | Most courses to return. |
No output schema declared.
No examples provided.
list_places List Places ~20
List countries, regions and cities that have pet crematories.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_product_categories List Product Categories ~18
List the product categories with their product counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_products List Products ~41
List the affiliate products, with the price each had on the day it was checked. Filter by product category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A product category slug. |
No output schema declared.
No examples provided.
list_sources List Sources ~27
List where the pet crematory data comes from, with the license and refresh of each source.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_listings Search Listings ~218
Search published pet crematories by text, place and category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug, from /categories. A parent slug also matches its children. |
| city | string | – | City slug, from /places. |
| country | string | – | ISO 3166-1 alpha-2 country code, any case. A country the directory does not cover, as listed in /places, gives 400. |
| cursor | string | – | `page.nextCursor` from the previous response. Opaque. Send the same filters and `limit`. |
| limit | integer | – | Items per page. |
| q | string | – | Search text, with at least one letter or digit. Matches name, categories, attributes, description and place. Typos fall back to close matches. |
| region | string | – | Region slug, from /places. |
| sort | string | – | `relevance` needs `q` and is the default with it. `name` is the default without `q`. `recent` is newest first. |
No output schema declared.
No examples provided.
How do I install the io.github.itsryanarmani/petcremation MCP server?
io.github.itsryanarmani/petcremation is a hosted endpoint at https://petcremation.fyi/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 · petcremation.fyi
claude mcp add --transport http itsryanarmani-petcremation 'https://petcremation.fyi/mcp'
What is the io.github.itsryanarmani/petcremation MCP server?
io.github.itsryanarmani/petcremation is an MCP server listed in the public MCP registry as io.github.itsryanarmani/petcremation. Find pet crematories near you and compare what they publish. This page covers its hosted endpoint (https://petcremation.fyi/mcp).
Is the io.github.itsryanarmani/petcremation MCP server safe to use?
io.github.itsryanarmani/petcremation 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 io.github.itsryanarmani/petcremation MCP server expose?
io.github.itsryanarmani/petcremation exposes 11 tools: search_listings, get_listing, list_places, list_categories, get_stats, and 6 more. Their descriptions and schemas cost roughly 521 tokens of context every time the server is loaded.
Does the io.github.itsryanarmani/petcremation MCP server require authentication?
No. We connected to io.github.itsryanarmani/petcremation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.itsryanarmani/petcremation MCP server still maintained?
io.github.itsryanarmani/petcremation 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 io.github.itsryanarmani/petcremation MCP server?
VerifyMCP ran 12 checks on io.github.itsryanarmani/petcremation, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.itsryanarmani/petcremation: HTTPS. 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.