com.mcparmory/ragie
OCI · GHCR.IO/MCPARMORY/RAGIE:1.0.2 · 2 COMPONENTS · SCANNED SEP 20
Ingest, manage, and retrieve documents for RAG-powered AI applications
Available components
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
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- 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 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8341 tokens (~160/item across 52 items; 52 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 52 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.
How do I install the com.mcparmory/ragie MCP server?
com.mcparmory/ragie runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/ragie:1.0.2. 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/mcparmory/ragie:1.0.2
claude mcp add com-mcparmory-ragie -- docker run --rm -i ghcr.io/mcparmory/ragie:1.0.2
{
"mcpServers": {
"com-mcparmory-ragie": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ragie:1.0.2"
]
}
}
} {
"servers": {
"com-mcparmory-ragie": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ragie:1.0.2"
]
}
}
} codex mcp add com-mcparmory-ragie -- docker run --rm -i ghcr.io/mcparmory/ragie:1.0.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-ragie": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ragie:1.0.2"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-ragie:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/ragie:1.0.2"] {
"McpServers": {
"com-mcparmory-ragie": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ragie:1.0.2"
]
}
}
} {
"mcpServers": {
"com-mcparmory-ragie": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ragie:1.0.2"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 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.
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 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/ragie:1.0.2
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 →
update_partition_limits Update Partition Limits ~244
Configure resource limits for a partition, including document hosting/processing capacity and media streaming/hosting quotas. When a limit is reached, the partition will be automatically disabled. Set any limit to null to remove it.
| Name | Type | Req | Description |
|---|---|---|---|
| audio_processed_limit_max | integer | – | Maximum duration in minutes for audio processing in the partition. Must be at least 1 minute. |
| media_hosted_limit_max | integer | – | Maximum size in megabytes for media hosted in the partition. Must be at least 1 MB. |
| media_streamed_limit_max | integer | – | Maximum size in megabytes for media streamed from the partition. Must be at least 1 MB. |
| pages_hosted_limit_max | integer | – | Maximum number of pages allowed for hosted documents in the partition. Must be at least 1 page. |
| pages_processed_limit_max | integer | – | Maximum number of pages allowed for processed documents in the partition. Must be at least 1 page. |
| partition_id | string | yes | The unique identifier of the partition to configure limits for. |
| video_processed_limit_max | integer | – | Maximum duration in minutes for video processing in the partition. Must be at least 1 minute. |
No output schema declared.
No examples provided.
update_webhook_endpoint Update Webhook Endpoint ~160
Update a webhook endpoint's configuration including its name, URL, or active status. Use this operation to rotate endpoints, change delivery URLs, or temporarily disable webhook delivery without deleting the endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether the webhook endpoint is active and should receive event deliveries. Set to false to temporarily disable delivery without deleting the endpoint. |
| endpoint_id | string | yes | The unique identifier of the webhook endpoint to update, formatted as a UUID. |
| name | string | – | A new display name for the webhook endpoint. |
| partition_pattern | string | – | A pattern to partition webhook events for this endpoint. |
| url | string | – | A new delivery URL for the webhook endpoint. Must be a valid URI between 1 and 2083 characters. |
No output schema declared.
No examples provided.
What is the com.mcparmory/ragie MCP server?
com.mcparmory/ragie is an MCP server listed in the public MCP registry as com.mcparmory/ragie. Ingest, manage, and retrieve documents for RAG-powered AI applications. This page covers its container image (ghcr.io/mcparmory/ragie:1.0.2).
Is the com.mcparmory/ragie MCP server safe to use?
com.mcparmory/ragie scores 50 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 com.mcparmory/ragie MCP server expose?
com.mcparmory/ragie exposes 52 tools: list_documents, create_document, create_document_from_text, ingest_document_from_url, get_document, and 47 more. Their descriptions and schemas cost roughly 8,341 tokens of context every time the server is loaded.
Is the com.mcparmory/ragie MCP server still maintained?
com.mcparmory/ragie is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.