Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.laraplugins/mcp

REMOTE · LARAPLUGINS.IO · SCANNED SEP 24

Validated Laravel plugin data - health scores, compatibility and vendor trust

Available components

0 this week 77 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 868 tokens (~217/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 (100% 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 current MCP spec version (2026-07-28).Pass
Install

How do I install the io.laraplugins/mcp server?

io.laraplugins/mcp is a hosted endpoint at https://laraplugins.io/mcp/plugins, 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 · laraplugins.io

# add to Claude Code
claude mcp add --transport http io-laraplugins-mcp 'https://laraplugins.io/mcp/plugins'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-laraplugins-mcp": {
      "url": "https://laraplugins.io/mcp/plugins"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-laraplugins-mcp": {
      "type": "http",
      "url": "https://laraplugins.io/mcp/plugins"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-laraplugins-mcp]
url = "https://laraplugins.io/mcp/plugins"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-laraplugins-mcp": {
      "type": "remote",
      "url": "https://laraplugins.io/mcp/plugins",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-laraplugins-mcp --url 'https://laraplugins.io/mcp/plugins' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-laraplugins-mcp:
    url: "https://laraplugins.io/mcp/plugins"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-laraplugins-mcp": {
      "Transport": "http",
      "Url": "https://laraplugins.io/mcp/plugins"
    }
  }
}
# add to Vellum
assistant mcp add io-laraplugins-mcp -t streamable-http -u 'https://laraplugins.io/mcp/plugins'
// mcp.json
{
  "mcpServers": {
    "io-laraplugins-mcp": {
      "type": "http",
      "url": "https://laraplugins.io/mcp/plugins"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 10 Sept 26 +1
    • Stability: 0.97 → pass security
  • 9 Sept 26 −1
    • Stability: pass → 0.97 functional
  • 30 Aug 26 +1
    • Stability: 0.97 → pass security
  • 29 Aug 26 −1
    • Stability: pass → 0.97 functional
  • 26 Aug 26 77
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 17 Aug 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 12 Aug 26 0
    • Endpoint reachability: not serving MCP → reachable ▲ functional
Diagnostics

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 Sept 2026 · Probed https://laraplugins.io/mcp/plugins

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=laraplugins.io CN=WE1,O=Google Trust Services,C=US 27 Jul 2026 25 Oct 2026 ECDSA 256 ECDSA-SHA256 8df9b07c9472360c0ee94712ce0aeb42
SANs: laraplugins.io, *.laraplugins.io
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 laraplugins.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
laraplugins.io. 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://laraplugins.io/mcp/plugins Verified 200
http (plaintext) http://laraplugins.io/mcp/plugins HTTPS enforced 301 https://laraplugins.io/mcp/plugins
MCP tools · 4 exposed · ~607 tokens

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 →

Tool Tokens
get-curated-tool-recommendations ~140

Returns curated tool recommendations for Laravel development, organized by category (Hosting / Deployment, Monitoring / Error Tracking, Email / Notifications, Authentication / Authorization, Payments / Billing, IDE / Development Tools, Testing, Security, SEO / Auditing, Analytics, Other). NOTE: Some of these are affiliate/partner recommendations — each result includes its relationship type and whether it is an affiliate.

NameTypeReqDescription
categorystring–Optional category filter. Available categories: Hosting / Deployment, Monitoring / Error Tracking, Email / Notifications, Authentication / Authorization, Payments / Billing, IDE / Development Tools,…
NameTypeReqDescription
dataarray––

No examples provided.

get-plugin-details-tool ~117

Fetch detailed information for a specific plugin given its vendor/package name, including security advisories, readme, and version history.

NameTypeReqDescription
include_readmeboolean–Whether to include the full README markdown content in the response.
include_security_advisoriesboolean–Whether to include security advisory information (CVEs, active advisories) in the response.
include_versionsboolean–Whether to include the versions array in the response.
packagestring–Full Composer package name in the form "vendor/package".
NameTypeReqDescription
dataobject––

No examples provided.

search-plugin-semantic-tool ~129

Search Laravel plugins by describing what you need in natural language. RECOMMENDED for use-case-driven queries. Example: "a package for PDF invoices with custom templates". When presenting results, ALWAYS include the laraplugins_url so the user can consult the full health report.

NameTypeReqDescription
limitinteger–Maximum number of results to return (1-25, default 10)
querystringyesNatural language description of the plugin you need, e.g. "a package for PDF invoices with custom templates" or "something like spatie/laravel-permission but for media"
NameTypeReqDescription
dataarray––
limitinteger–Number of results requested
similarity_methodstring–How results were ranked: "vector" (AI embedding cosine similarity), "rerank" (AI reranking API), or "fulltext_fallback" (downloads sort when no AI available)
total_candidatesinteger–Total candidates found before reranking

No examples provided.

search-plugin-tool ~221

This tool enables the search of packagist packages that support laravel with advanced filters. When presenting results, ALWAYS include the laraplugins_url alongside the plugin name so the user can consult the full health report.

NameTypeReqDescription
health_scorestring|null–Search by plugin health score.
is_secureboolean|null–Filter by LaraPlugins Secure badge. true to only show secure plugins.
laravel_compatibilitystring|null–Search by plugin's laravel compatibility where there is at least one version supporting that laravel version (eg 10).
pageinteger|null–Page number to return.
php_versionstring|null–Search by plugin php compatibility where there is at least one version supporting that php version (eg 8.5).
return_archivedboolean|null–Return archived plugins as well in the results?.
text_searchstring|null–Search by text in plugin name or description.
vendor_filterstring|null–Search by plugin vendor name. (eg: spatie)
NameTypeReqDescription
dataarray––

No examples provided.

Common questions

What is the io.laraplugins/mcp server?

io.laraplugins/mcp is listed in the public MCP registry as io.laraplugins/mcp. Validated Laravel plugin data - health scores, compatibility and vendor trust. This page covers its hosted endpoint (https://laraplugins.io/mcp/plugins).

Is the io.laraplugins/mcp server safe to use?

io.laraplugins/mcp scores 77 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.laraplugins/mcp server expose?

io.laraplugins/mcp exposes 4 tools: search-plugin-tool, search-plugin-semantic-tool, get-plugin-details-tool, get-curated-tool-recommendations. Their descriptions and schemas cost roughly 607 tokens of context every time the server is loaded.

Does the io.laraplugins/mcp server require authentication?

No. We connected to io.laraplugins/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.laraplugins/mcp server still maintained?

io.laraplugins/mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.