Laravel MCP Companion
OCI · GHCR.IO/BRIANIRISH/LARAVEL-MCP-COMPANION:V0.13.0
Laravel documentation aggregator: multi-version core docs, services, packages, learning paths.
Available components
Last scanned (3 hours ago)
Scores higher than 91% of OCI servers
Category Code Search and Documentation
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: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency35
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 92 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 687 tokens (~171/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 (75% 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 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
- 15 Oct 26 +1
- Stability: 0.97 → pass security
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 90. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 −3
- Stability: pass → 0.83 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 5 Nov 2026 · Analysed oci/ghcr.io/brianirish/laravel-mcp-companion:v0.13.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| 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 →
call_tool ~53
Call a tool by name with the given arguments. Use this to execute tools discovered via search_tools.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | – | – | Arguments to pass to the tool |
| name | string | yes | The name of the tool to call |
No output schema declared.
No examples provided.
read_laravel_doc_section ~114
Read one section of a Laravel documentation file by the anchor or heading returned by search_laravel_docs. Prefer this over read_laravel_doc_content: a whole file can exceed 30,000 tokens, while a section is typically a few hundred.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | Documentation file, e.g. 'queues.md' |
| section | string | yes | Anchor or heading, e.g. 'dealing-with-failed-jobs' |
| version | – | – | Laravel version. Defaults to the configured version. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_laravel_docs ~266
Searches every aggregated corpus at once: core Laravel docs, service docs (Forge, Vapor, Envoyer, Nova), fetched package docs (Spatie, Livewire, Inertia, Filament, ...), and learning resources. Returns ranked sections with snippets, anchors, and a source label; read the winning section with read_laravel_doc_section. When to use: - Any question about Laravel or its ecosystem, in plain language - Narrow with sources=["core"] (or services/packages/learning) when the corpus is known - Exact symbols like queue:retry also work via a literal fallback
| Name | Type | Req | Description |
|---|---|---|---|
| all_versions | boolean | – | Search every supported core version instead of just the configured one |
| include_external | boolean | – | Legacy core-only switch; False limits the search to core docs. Superseded by an explicit `sources`. |
| query | string | yes | Search term to look for |
| sources | – | – | Restrict the corpus: any of "core", "services", "packages", "learning". Default searches all of them; each hit is labeled with its source. |
| version | – | – | Laravel version for the core docs (e.g., "12.x"). Defaults to the configured version. Packages, services, and learning docs are not Laravel-versioned. |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Extra detail accompanying an error |
| error | string | – | Present instead of the success keys when the call failed |
| query | string | – | – |
| results | array | – | – |
| scope | string | – | Comma-separated versions/services searched |
No examples provided.
search_tools ~45
Search for tools using natural language. Returns matching tool definitions ranked by relevance, in the same format as list_tools.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural language query to search for tools |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
How do I install the Laravel MCP Companion server?
Laravel MCP Companion runs locally as a container image, launched with docker run --rm -i ghcr.io/brianirish/laravel-mcp-companion:v0.13.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/brianirish/laravel-mcp-companion:v0.13.0
claude mcp add brianirish-laravel-mcp-companion -- docker run --rm -i ghcr.io/brianirish/laravel-mcp-companion:v0.13.0
What is the Laravel MCP Companion server?
Laravel MCP Companion is listed in the public MCP registry as io.github.brianirish/laravel-mcp-companion. Laravel documentation aggregator: multi-version core docs, services, packages, learning paths. This page covers its container image (ghcr.io/brianirish/laravel-mcp-companion:v0.13.0).
Is the Laravel MCP Companion server safe to use?
Laravel MCP Companion scores 54 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 Laravel MCP Companion server expose?
Laravel MCP Companion exposes 4 tools: search_laravel_docs, read_laravel_doc_section, search_tools, call_tool. Their descriptions and schemas cost roughly 478 tokens of context every time the server is loaded.
Is the Laravel MCP Companion server still maintained?
Laravel MCP Companion is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.