_ registry / mcp streamable-http · checked 50m ago

Laravilt MCP

https://mcp.laravilt.com

Registry code: f9a4d61f4509d16b

api record

Laravilt MCP gives read-only access to the latest documentation, READMEs, changelogs and released versions of every Laravilt package (laravilt/*), synced from GitHub and Packagist.

Laravilt is a Laravel admin panel framework (panels, resources, forms, tables, actions, infolists, widgets, notifications, AI, plugins) with Vue and React (Inertia) frontends.

endpoint
https://mcp.laravilt.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Laravilt MCP live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is Laravilt MCP free to use?
Yes — the hub reached it with no key and no payment.
What tools does Laravilt MCP have?
9 tools: search-docs, read-doc, list-docs, plugin-development-guide, get-package, get-changelog, get-latest-versions, installation-guide, ….
Is Laravilt MCP safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
475ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
3 open 6 never probed 3 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get-latest-versions open 50m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • installation-guide open 50m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "stack": {
          "enum": [
            "vue",
            "react"
          ],
          "type": "string",
          "description": "Frontend stack of the Laravel app: \"vue\" (Inertia + Vue 3) or \"react\" (Inertia + React). Defaults to \"vue\"."
        }
      }
    }
    arguments 13 lines
  • list-packages open 50m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search-docs unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Maximum number of results (1-25, default 8)."
        },
        "query": {
          "type": "string",
          "description": "Keywords to search for."
        },
        "package": {
          "type": "string",
          "description": "Optional package to restrict the search to, e.g. \"forms\" or \"laravilt/panel\"."
        }
      }
    }
    arguments 22 lines
  • read-doc unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "package",
        "path"
      ],
      "properties": {
        "page": {
          "type": "integer",
          "minimum": 1,
          "description": "Page number for long documents (default 1)."
        },
        "path": {
          "type": "string",
          "description": "File path inside the package repository, e.g. \"README.md\", \"CHANGELOG.md\" or \"docs/resources/introduction.md\"."
        },
        "package": {
          "type": "string",
          "description": "Package name, e.g. \"panel\" or \"laravilt/forms\"."
        }
      }
    }
    arguments 22 lines
  • list-docs unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "package": {
          "type": "string",
          "description": "Optional package name, e.g. \"laravilt\" (main docs), \"panel\" or \"plugins\". Omit to list every package."
        }
      }
    }
    arguments 9 lines
  • plugin-development-guide unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get-package unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "package"
      ],
      "properties": {
        "package": {
          "type": "string",
          "description": "Package name, e.g. \"panel\", \"forms\" or \"laravilt/tables\". Use list-packages to see all names."
        }
      }
    }
    arguments 12 lines
  • get-changelog unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "package"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum number of releases and changelog entries to include (1-50, default 10)."
        },
        "package": {
          "type": "string",
          "description": "Package name, e.g. \"panel\" or \"laravilt/forms\"."
        }
      }
    }
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f9a4d61f4509d16b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f9a4d61f4509d16b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f9a4d61f4509d16b/badge.svg)](https://brick.blue/agent/f9a4d61f4509d16b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.