Malinois
REMOTE · MALINOIS.APP · SCANNED SEP 20
Check a live app you own for public databases, leaked keys and exposed files.
Available components
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 515 tokens (~257/item across 2 items; 2 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 Management30
- Stability observed for 9 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
- Structured output schemas are declared (50% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the Malinois MCP server?
Malinois is a hosted endpoint at https://malinois.app/mcp, 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 · malinois.app
claude mcp add --transport http app-malinois-scan 'https://malinois.app/mcp'
{
"mcpServers": {
"app-malinois-scan": {
"url": "https://malinois.app/mcp"
}
}
} {
"servers": {
"app-malinois-scan": {
"type": "http",
"url": "https://malinois.app/mcp"
}
}
} [mcp_servers.app-malinois-scan] url = "https://malinois.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-malinois-scan": {
"type": "remote",
"url": "https://malinois.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-malinois-scan --url 'https://malinois.app/mcp' --transport streamable-http
mcp_servers:
app-malinois-scan:
url: "https://malinois.app/mcp" {
"McpServers": {
"app-malinois-scan": {
"Transport": "http",
"Url": "https://malinois.app/mcp"
}
}
} assistant mcp add app-malinois-scan -t streamable-http -u 'https://malinois.app/mcp'
{
"mcpServers": {
"app-malinois-scan": {
"type": "http",
"url": "https://malinois.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Sept 26 68
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 20 Sept 2026 · Probed https://malinois.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=malinois.app | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 1773b2fbafb981331336b4f4adc5d9c2 |
| SANs: malinois.app, *.malinois.app | ||||||
| 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 malinois.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| malinois.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; connect-src 'self' https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com; frame-ancestors 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://malinois.app/mcp | Verified | 200 | |
| http (plaintext) | http://malinois.app/mcp | Inconclusive | 405 |
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 →
explain_finding Explain a Malinois finding ~105
Returns the plain-language meaning and step-by-step fix for one Malinois finding. Use it while helping the user fix an issue reported by scan_app, or when they ask what a finding means. Pass the rule_id exactly as scan_app returned it. Read-only, no network, instant.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language for the explanations (default: en). |
| rule_id | string | yes | The rule_id of a finding, e.g. supabase_missing_rls |
No output schema declared.
No examples provided.
scan_app Check a deployed app for data leaks ~303
Runs a passive, outside-in security check of a live web app and returns a letter grade (A–F), each issue in plain language with fix steps, and a report link. Use when the user asks whether their deployed app is safe, before launch, or after a redeploy to confirm a fix. It checks for publicly readable Supabase/Firebase data, secret keys (Stripe, OpenAI, Supabase service_role…) in client JavaScript, downloadable .env/.git files, source maps, permissive CORS and missing security headers. Do not use it for apps the user does not own or is not authorized to test, for localhost or private addresses, or to review source code — it only sees what the public URL serves. Behavior: sends ordinary GET requests like a browser (no login, exploitation or load testing); takes about 10–30 seconds; saves the result as a report page on malinois.app, linked in the response; secrets appear only masked. Each app can be checked at most 20 times per hour.
| Name | Type | Req | Description |
|---|---|---|---|
| i_own_this | boolean | yes | Must be true. Set it only after the user has explicitly confirmed they own this app or are authorized to test it; without it the check is refused. |
| lang | string | – | Language for the explanations (default: en). |
| url | string | yes | Public http(s) address of the deployed app, e.g. https://my-app.lovable.app (scheme optional). |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | Most serious first. |
| grade | string | yes | A (best) to F |
| host | string | yes | – |
| limited | boolean | yes | True when the app exposed little to a passive check; a good grade is then not proof of safety. |
| platform | string|null | – | Detected builder/host, e.g. lovable, replit |
| report_url | string | yes | – |
| score | number | yes | 0–100 |
No examples provided.
What is the Malinois MCP server?
Malinois is an MCP server listed in the public MCP registry as app.malinois/scan. Check a live app you own for public databases, leaked keys and exposed files. This page covers its hosted endpoint (https://malinois.app/mcp).
Is the Malinois MCP server safe to use?
Malinois scores 73 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 Malinois MCP server expose?
Malinois exposes 2 tools: scan_app, explain_finding. Their descriptions and schemas cost roughly 408 tokens of context every time the server is loaded.
Does the Malinois MCP server require authentication?
No. We connected to Malinois without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Malinois MCP server still maintained?
Malinois 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.