ConsoleMouse profiles
REMOTE · MCP.CONSOLEMOUSE.COM
Write and check ConsoleMouse profile files: format, validator, plain-language preview, import code.
Available components
Last scanned (21 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category IoT and Hardware
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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 875 tokens (~175/item across 5 items; 5 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 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.
- 11 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.2.0 → 0.2.1 functional
- 10 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 71
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 21 Nov 2026 · Probed https://mcp.consolemouse.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=consolemouse.com | CN=WE1,O=Google Trust Services,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 6db960a31c1a07cb0ede5fdea3f66f28 |
| SANs: consolemouse.com, mcp.consolemouse.com, *.mcp.consolemouse.com | ||||||
| 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 mcp.consolemouse.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| consolemouse.com. | No DS | 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 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.consolemouse.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.consolemouse.com/mcp | HTTPS enforced | 301 | https://mcp.consolemouse.com/mcp |
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 →
format_examples List ConsoleMouse example profiles ~63
Lists the published base profiles (accessibility templates), example profiles and invalid examples with their expected validator message; with an id, returns that file. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Return this example file (id from the list). |
| kind | string | – | – |
No output schema declared.
No examples provided.
format_spec Get the ConsoleMouse profile format ~107
Returns the ConsoleMouse profile format (profile-v1 1.32.0): a quick reference for writing profiles and macros, one section of the specification (import_code: the CMP2 import code and the older CM1 share code), or the JSON Schema. Read-only; returns published documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | quick_reference (default: everything needed to write a profile, with the base profiles and their bound keys), a specification section, full, or schema (JSON Schema). |
No output schema declared.
No examples provided.
profile_describe Describe a ConsoleMouse profile in plain words ~135
Returns a plain-language preview of a valid ConsoleMouse profile: for a derived profile one sentence per change against its base (keys, macros, press once, mouse movement), for a full profile one sentence per key. Languages: de, en, es, fr, it, pl, pt-BR. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the sentences. |
| profile | object|string | yes | The profile as a JSON object, as JSON text, an import envelope, or an import code (CMP2., or the older CM1.). Usually a derived profile (origin "derived", base_profile_id, patch). |
No output schema declared.
No examples provided.
profile_import_code Build a ConsoleMouse import code ~268
Checks a derived ConsoleMouse profile and returns an import code (CMP2) the person pastes into ConsoleMouse under Games > Import profile or in the AI Workshop (Import code), with the plain-language preview and the import steps. A full profile is accepted when base_profile_id names its base. Use format CM1 only when the person has an older ConsoleMouse (0.3.9 to 0.4.x). Read-only: the code is computed and returned, nothing is stored or sent anywhere.
| Name | Type | Req | Description |
|---|---|---|---|
| author_note | string | – | Optional note shown with the import preview. Plain text (no control characters); describe the controls, nothing personal. |
| base_profile_id | string | – | Only for a full profile: the base it was made from. |
| format | string | – | CMP2 (default, current ConsoleMouse). CM1 only for ConsoleMouse 0.3.9 to 0.4.x, which need the exact base version. |
| lang | string | – | Language of the preview and the import steps. |
| profile | object|string | yes | The profile as a JSON object, as JSON text, an import envelope, or an import code (CMP2., or the older CM1.). Usually a derived profile (origin "derived", base_profile_id, patch). |
No output schema declared.
No examples provided.
profile_validate Check a ConsoleMouse profile ~120
Checks a ConsoleMouse profile (full or derived), an import envelope or an import code (CMP2, or the older CM1) against the JSON Schema and every format rule, including the macro limits. Returns valid or a list of issues with the path to fix. Read-only; nothing is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | object|string | yes | The profile as a JSON object, as JSON text, an import envelope, or an import code (CMP2., or the older CM1.). Usually a derived profile (origin "derived", base_profile_id, patch). |
No output schema declared.
No examples provided.
How do I install the ConsoleMouse profiles MCP server?
ConsoleMouse profiles is a hosted endpoint at https://mcp.consolemouse.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 · mcp.consolemouse.com
claude mcp add --transport http com-consolemouse-profiles 'https://mcp.consolemouse.com/mcp'
What is the ConsoleMouse profiles MCP server?
ConsoleMouse profiles is an MCP server listed in the public MCP registry as com.consolemouse/profiles. Write and check ConsoleMouse profile files: format, validator, plain-language preview, import code. This page covers its hosted endpoint (https://mcp.consolemouse.com/mcp).
Is the ConsoleMouse profiles MCP server safe to use?
ConsoleMouse profiles scores 77 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 ConsoleMouse profiles MCP server expose?
ConsoleMouse profiles exposes 5 tools: format_spec, format_examples, profile_validate, profile_describe, profile_import_code. Their descriptions and schemas cost roughly 693 tokens of context every time the server is loaded.
Does the ConsoleMouse profiles MCP server require authentication?
No. We connected to ConsoleMouse profiles without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ConsoleMouse profiles MCP server still maintained?
ConsoleMouse profiles is still listed as active in the MCP registry. We last reached this channel on 21 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 ConsoleMouse profiles MCP server?
VerifyMCP ran 13 checks on ConsoleMouse profiles, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.