@mrfentmen/meilisearch-mcp

MCPcommunity
v1.0.2io.github.mrfentmenMITUpdated 3d agonpmGitHub

MCP server for MeiliSearch. Search indexes, manage documents, check health and stats.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
64Downloads/wk
3d agoLast update
Reads these credentials
  • MEILISEARCH_API_KEYAPI keyoptional

    MeiliSearch API key for authentication

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.mrfentmen
LicenseMIT
Version1.0.2
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · 2 privileged
Security scan✓ Cleanv1.0.2 · todayHow well does this scan work?
EvalsNone
IndexedSep 23, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · 2 privileged
Statically extracted from the published packagev1.0.2 · 11h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

check_healthCheck if the MeiliSearch server is running and healthy.

Check if the MeiliSearch server is running and healthy.

No input schema was published for this tool.

list_indexesList all MeiliSearch indexes.

List all MeiliSearch indexes.

No input schema was published for this tool.

get_indexGet details about a specific MeiliSearch index.

Get details about a specific MeiliSearch index.

No input schema was published for this tool.

create_indexCreate a new MeiliSearch index.

Create a new MeiliSearch index.

No input schema was published for this tool.

delete_indexprivilegedDelete a MeiliSearch index.

Delete a MeiliSearch index.

No input schema was published for this tool.

search_indexSearch for documents in a MeiliSearch index.

Search for documents in a MeiliSearch index.

No input schema was published for this tool.

get_documentsList documents in a MeiliSearch index.

List documents in a MeiliSearch index.

No input schema was published for this tool.

get_documentGet a single document by ID from a MeiliSearch index.

Get a single document by ID from a MeiliSearch index.

No input schema was published for this tool.

add_documentsAdd documents to a MeiliSearch index. Accepts a JSON array of document objects.

Add documents to a MeiliSearch index. Accepts a JSON array of document objects.

No input schema was published for this tool.

delete_documentprivilegedDelete a document by ID from a MeiliSearch index.

Delete a document by ID from a MeiliSearch index.

No input schema was published for this tool.

get_statsGet statistics about the MeiliSearch instance.

Get statistics about the MeiliSearch instance.

No input schema was published for this tool.

get_index_statsGet statistics for a specific index.

Get statistics for a specific index.

No input schema was published for this tool.

get_taskGet the status of an asynchronous task.

Get the status of an asynchronous task.

No input schema was published for this tool.

list_keysList all API keys for the MeiliSearch instance.

List all API keys for the MeiliSearch instance.

No input schema was published for this tool.

update_settingsUpdate settings for a MeiliSearch index (searchable attributes, filterable, sortable, ranking rules, etc).

Update settings for a MeiliSearch index (searchable attributes, filterable, sortable, ranking rules, etc).

No input schema was published for this tool.

15 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for MeiliSearch. Search indexes, manage documents, check health and stats.

Keywords
mcpmeilisearchsearchvector-searchdatabase
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-24 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in search & retrieval