Habits prompt-injection guard
REMOTE · HABITS.DARMOUSSEH.COM
Check user prompts for injection/jailbreaks; your own guard learns from your labels. Works keyless.
Available components
Last scanned (23 hours ago)
Scores higher than 3% of remote servers
Unreachable for 6 days in a row. Last reached 15 Nov 2026.
Category Security
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: The hosted service is retired; the endpoint no longer answers.
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (2)
- HTTPS
- Transport
Checks we could not complete (9)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- DNSSEC in Endpoint SecurityDNSSEC not yet verified: we couldn't validate it against a resolver.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Nov 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Nov 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Nov 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Nov 26 +55
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Nov 26 −55
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://habits.darmousseh.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of habits.darmousseh.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| habits.darmousseh.com. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://habits.darmousseh.com/mcp | Unreachable | ||
| http (plaintext) | http://habits.darmousseh.com/mcp | HTTPS enforced |
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 →
check_prompt Check a prompt for injection ~123
Is this user-typed text a prompt injection or jailbreak (an attempt to override, hijack or extract an AI system's instructions)? Returns flagged true/false and a 0-1 score. Without a key it uses the public guard (30 checks per day per network). With a key it uses your own guard, which learns from teach_guard; the result carries a request_id. Built for user prompts; it is weak on injections hidden in tool output or documents.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | the user prompt to check, up to 8,000 characters |
No output schema declared.
No examples provided.
get_free_key Get a free API key ~83
Create a free Habits account and API key (no email). The key is shown once; set it as the Authorization: Bearer header for this MCP server. The free plan has a fixed $0.10/day spend cap and its own trainable injection guard.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | – | optional: 2-32 of a-z 0-9 - |
No output schema declared.
No examples provided.
teach_guard Teach your guard ~99
Label one prompt for your own guard so it stops repeating a mistake (a false alarm on a normal request, or a missed injection). Needs an API key (get_free_key). About 50 of your own labels cut false alarms from 15% to 4% in our benchmark.
| Name | Type | Req | Description |
|---|---|---|---|
| injection | boolean | yes | true if it IS an injection/jailbreak, false if it is a normal request |
| text | string | yes | the prompt |
No output schema declared.
No examples provided.
How do I install the Habits prompt-injection guard MCP server?
Habits prompt-injection guard is a hosted endpoint at https://habits.darmousseh.com/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 · habits.darmousseh.com
claude mcp add --transport http com-darmousseh-habits-guard 'https://habits.darmousseh.com/mcp'
What is the Habits prompt-injection guard MCP server?
Habits prompt-injection guard is an MCP server listed in the public MCP registry as com.darmousseh/habits-guard. Check user prompts for injection/jailbreaks; your own guard learns from your labels. Works keyless. This page covers its hosted endpoint (https://habits.darmousseh.com/mcp).
Is the Habits prompt-injection guard MCP server safe to use?
Habits prompt-injection guard scores 12 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 Habits prompt-injection guard MCP server expose?
Habits prompt-injection guard exposes 3 tools: check_prompt, teach_guard, get_free_key. Their descriptions and schemas cost roughly 305 tokens of context every time the server is loaded.
Does the Habits prompt-injection guard MCP server require authentication?
Its publisher declares no required credentials for Habits prompt-injection guard. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Habits prompt-injection guard MCP server still maintained?
Habits prompt-injection guard is marked deprecated in the MCP registry. We last reached this channel on 15 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Habits prompt-injection guard MCP server?
VerifyMCP ran 2 checks on Habits prompt-injection guard, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about Habits prompt-injection guard: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.