Laravilt
REMOTE · MCP.LARAVILT.COM
Laravilt docs, packages and plugins for agents: a Laravel admin panel on Inertia with Vue or React.
Available components
Last scanned (21 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Code Search and Documentation
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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 9548 tokens (~24/item across 387 items; 9 tools + 378 resources), lean.Pass
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 23 Oct 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.
- 21 Oct 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.
- 19 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 68
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 24 Oct 2026 · Probed https://mcp.laravilt.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=laravilt.com | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f22a5fda878b175f131ac54a06baab88 |
| SANs: laravilt.com, *.laravilt.com | ||||||
| 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 mcp.laravilt.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| laravilt.com. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.laravilt.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.laravilt.com/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-changelog Get a Laravilt package changelog ~101
Get the release history of a Laravilt package: tagged versions with release dates and GitHub release notes, followed by entries from its CHANGELOG.md. Useful for upgrade notes and for checking when a feature or fix shipped.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of releases and changelog entries to include (1-50, default 10). |
| package | string | yes | Package name, e.g. "panel" or "laravilt/forms". |
No output schema declared.
No examples provided.
get-latest-versions Get latest Laravilt versions ~61
Get a compact map of every Laravilt package to its latest released version (from Packagist and GitHub releases) plus ready-to-paste composer require lines. Use it before writing composer.json constraints or upgrade instructions so versions are never guessed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-package Get a Laravilt package ~103
Get details about one Laravilt package: README summary, latest version and install command, requirements (PHP, Laravel and other laravilt/* dependencies from composer.json), frontend support (Vue in resources/js, React in resources/react), its documentation index and the most recent changelog/release entries.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Package name, e.g. "panel", "forms" or "laravilt/tables". Use list-packages to see all names. |
No output schema declared.
No examples provided.
installation-guide Laravilt installation guide ~109
Step-by-step instructions for installing Laravilt on a new Laravel 13 application with `php artisan laravilt:install --stack=vue|react`, including requirements, the official installation docs from laravilt/laravilt, which packages support the chosen frontend stack, and current package versions.
| Name | Type | Req | Description |
|---|---|---|---|
| stack | string | – | Frontend stack of the Laravel app: "vue" (Inertia + Vue 3) or "react" (Inertia + React). Defaults to "vue". |
No output schema declared.
No examples provided.
list-docs List Laravilt documentation files ~103
Show the documentation tree (README, CHANGELOG, composer.json and every Markdown file under docs/) for one Laravilt package with document titles, or a compact tree for all packages when no package is given. The laravilt/laravilt meta package holds the main framework guide.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | – | Optional package name, e.g. "laravilt" (main docs), "panel" or "plugins". Omit to list every package. |
No output schema declared.
No examples provided.
list-packages List Laravilt packages ~63
List every Laravilt package (laravilt/*) with its description, latest released version, last release date, composer install command and GitHub repository URL. Use this first to discover which packages exist before calling get-package, list-docs or search-docs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plugin-development-guide Laravilt plugin development guide ~84
An up-to-date guide to building Laravilt plugins, assembled from the latest laravilt/plugins README and docs plus the plugin chapters of the main Laravilt docs: the laravilt:plugin and laravilt:make generators, generated plugin structure, plugin classes and registration of resources/pages/widgets, Vue and React frontends, and links to every plugin document.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read-doc Read a Laravilt document ~141
Read a full documentation file from a Laravilt package, e.g. {"package":"laravilt","path":"docs/getting-started/installation.md"}. Paths come from search-docs, list-docs or get-package. Long documents are split into pages; pass "page" to continue.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Package name, e.g. "panel" or "laravilt/forms". |
| page | integer | – | Page number for long documents (default 1). |
| path | string | yes | File path inside the package repository, e.g. "README.md", "CHANGELOG.md" or "docs/resources/introduction.md". |
No output schema declared.
No examples provided.
search-docs Search Laravilt documentation ~131
Full-text search across the documentation, READMEs and changelogs of all Laravilt packages. Returns ranked snippets with the package, file path and GitHub link. Use short keyword queries (e.g. "relation manager", "TextInput validation", "tenancy"), then open a hit with read-doc.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (1-25, default 8). |
| package | string | – | Optional package to restrict the search to, e.g. "forms" or "laravilt/panel". |
| query | string | yes | Keywords to search for. |
No output schema declared.
No examples provided.
How do I install the Laravilt MCP server?
Laravilt is a hosted endpoint at https://mcp.laravilt.com/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 · mcp.laravilt.com
claude mcp add --transport http laravilt-laravilt 'https://mcp.laravilt.com/mcp'
What is the Laravilt MCP server?
Laravilt is an MCP server listed in the public MCP registry as io.github.laravilt/laravilt. Laravilt docs, packages and plugins for agents: a Laravel admin panel on Inertia with Vue or React. This page covers its hosted endpoint (https://mcp.laravilt.com/mcp).
Is the Laravilt MCP server safe to use?
Laravilt 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 Laravilt MCP server expose?
Laravilt exposes 9 tools: list-packages, get-package, search-docs, read-doc, list-docs, and 4 more. Their descriptions and schemas cost roughly 896 tokens of context every time the server is loaded.
Does the Laravilt MCP server require authentication?
No. We connected to Laravilt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Laravilt MCP server still maintained?
Laravilt is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.