Laravel MCP Companion
PYPI · LARAVEL-MCP-COMPANION · 2 COMPONENTS
Laravel docs for every version from 6.x to 13.x, plus services and packages, kept local and offline.
Available components
Last scanned (18 hours ago)
Scores higher than 55% of PyPI 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 Security44
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 1 of 25 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to brianirish/laravel-mcp-companion). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 978 tokens (~244/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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.
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 18 Nov 26 63
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 · Analysed pypi/laravel-mcp-companion@1.0.0rc1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | brianirish/laravel-mcp-companion |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/brianirish/laravel-mcp-companion/.github/workflows/publish-pypi.yml@refs/tags/v1.0.0-rc1 |
| Rekor log index | 3977545041 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:ea2bc549abe925d0036916eafe8aa248ff70bfa285c60b21d1d535a0250ad7cc |
Background: How many MCP packages publish verified provenance →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
| build_hook | Not reviewed | hatch_build.py,tool.hatch.build.targets.wheel.hooks.custom |
Background: Why install scripts are a supply-chain risk →
Dependencies 25 packages
| Packages resolved | 25 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~207
Read one section of a documentation page. Give it a search result's `file` (as `filename`) and `section`, and it returns that section's markdown and nothing else. This is the cheap way to read: a whole page such as queues.md runs to tens of thousands of tokens, and an answer usually needs one section of it. `section` may be an anchor ("dealing-with-failed-jobs"), a heading ("Dealing With Failed Jobs") or a heading written as a slug. If the section is not found, the error lists the sections the page does have.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | The page, as search returns it: "queues.md", "12.x/queues.md" or "forge/servers/php.md" |
| section | string | yes | The section's anchor or heading, as search returns it |
| version | – | – | Laravel version for a framework page named without one. Ignored for service, package and learning pages |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The section as markdown; the same text as the result's text content |
| corpus | string | – | The service, package or learning source, for any other page |
| file | string | yes | – |
| heading | string | yes | – |
| section | string | yes | – |
| version | string | – | Laravel version, for a framework page |
No examples provided.
search_laravel_docs ~303
Search Laravel's documentation and get back the sections that answer the question. Covers every corpus on this server at once: the framework docs for the selected Laravel version, the first-party services (Forge, Vapor, Envoyer, Nova, Cloud, Nightwatch, Herd), fetched package docs (Livewire, Filament, Inertia, Spatie and others) and learning resources. Each result names a `file` and a `section`; pass them to read_laravel_doc_section as `filename` and `section` to read just that section. Use it first for any Laravel question. Narrow with `sources` when you know the corpus, and set `version` for an older Laravel release. Results are ranked across corpora, and no single source takes the whole page when others match. Nothing found is a normal result with count 0.
| Name | Type | Req | Description |
|---|---|---|---|
| all_versions | boolean | – | Search every Laravel version instead of one |
| limit | integer | – | How many results to return, 1 to 20. Default 5 |
| query | string | yes | What to look for, as a question or as keywords |
| sources | – | – | Restrict the search to any of "core", "services", "packages", "learning". Default: all four |
| version | – | – | Laravel version for the framework docs (e.g. "12.x"). Defaults to the server's configured version. Services, packages and learning resources are not Laravel-versioned. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | How many results follow; 0 when nothing matched |
| matched_needs | array | – | Common tasks recognised in the query, whose usual documentation pages were favoured |
| query | string | yes | – |
| results | array | yes | – |
| scope | string | yes | The Laravel versions searched, comma-separated |
| sources | array | yes | – |
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 PyPI package, launched with uvx laravel-mcp-companion. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · laravel-mcp-companion
claude mcp add brianirish-laravel-mcp-companion -- uvx laravel-mcp-companion
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 docs for every version from 6.x to 13.x, plus services and packages, kept local and offline. This page covers its PyPI package (laravel-mcp-companion).
Is the Laravel MCP Companion server safe to use?
Laravel MCP Companion scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 608 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Laravel MCP Companion server under?
Laravel MCP Companion declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Laravel MCP Companion server?
VerifyMCP ran 14 checks on Laravel MCP Companion, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Laravel MCP Companion: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.