# Jules (remote · mcp.heyjules.app)

Create, list, update and cancel phone call reminders that ring your phone, via your Jules account.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.heyjules.app`: 67/100 (this document), [markdown](https://verifymcp.io/servers/peteabu-jules/mcp.md), [page](https://verifymcp.io/servers/peteabu-jules/mcp)

## Channel facts

- Endpoint: `https://mcp.heyjules.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_jules_reminder).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 722 tokens (~103/item across 7 items; 6 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Jules MCP server?

Jules is a hosted endpoint at https://mcp.heyjules.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.

### Claude

```bash
claude mcp add --transport http peteabu-jules 'https://mcp.heyjules.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "peteabu-jules": {
      "url": "https://mcp.heyjules.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "peteabu-jules": {
      "type": "http",
      "url": "https://mcp.heyjules.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.peteabu-jules]
url = "https://mcp.heyjules.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "peteabu-jules": {
      "type": "remote",
      "url": "https://mcp.heyjules.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add peteabu-jules --url 'https://mcp.heyjules.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  peteabu-jules:
    url: "https://mcp.heyjules.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "peteabu-jules": {
      "Transport": "http",
      "Url": "https://mcp.heyjules.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add peteabu-jules -t streamable-http -u 'https://mcp.heyjules.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "peteabu-jules": {
      "type": "http",
      "url": "https://mcp.heyjules.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 67, +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.

### 2026-11-02 (score 66, +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.

### 2026-10-31 (score 65, +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.

### 2026-10-28 (score 64, +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.

### 2026-10-26 (score 63, +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.

### 2026-10-24 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 61)

First indexed and scored.

## MCP tools (6)

### `prepare_jules_reminder` (~196 tokens)

Prepare a Jules reminder

Generate a Jules setup link for a connected Jules user so they can finish setup, verify their number, and save the reminder on heyjules.app.

Input parameters:

- `date` (string, required): Reminder date in YYYY-MM-DD format.
- `email` (string): Optional email address to prefill.
- `name` (string): Optional user name to prefill.
- `phoneNumber` (string): Optional phone number to prefill. Include country code when possible.
- `task` (string, required): The reminder task or note.
- `time` (string, required): Reminder time in 24-hour HH:MM format. Only use this after the user has provided or confirmed an exact time.
- `timeExpression` (string, required): The user's original time wording, preserved exactly, such as '4:00 PM' or '16:00'. If the user said something fuzzy like 'later this afternoon', ask a follow-up instead of calling this tool.

### `get_jules_account_status` (~26 tokens)

Get Jules account status

Check whether the connected Jules account is ready to manage reminders in ChatGPT.

### `list_jules_reminders` (~46 tokens)

List Jules reminders

List reminders from the connected Jules account.

Input parameters:

- `limit` (integer): Maximum number of reminders to return.
- `view` (string): Optional filter for which reminders to list.

### `create_jules_reminder` (~183 tokens)

Create a Jules reminder

Create a reminder directly on the connected Jules account.

Input parameters:

- `callWindowMinutes` (integer): How many minutes before the scheduled time Jules should call.
- `recurrenceDays` (array): Weekday numbers for custom recurrence, Sunday = 0 through Saturday = 6.
- `recurrenceFrequency` (string): Optional recurrence frequency.
- `scheduledAt` (string, required): The reminder time as an ISO datetime string. Only use this after the user has provided or confirmed an exact time.
- `snoozeRetries` (integer): How many retry calls Jules should make.
- `timeExpression` (string, required): The user's original time wording, preserved exactly, such as '4:00 PM' or '16:00'. If the user said something fuzzy like 'later this afternoon', ask a follow-up instead of calling this tool.
- `title` (string, required): The reminder title.

### `update_jules_reminder` (~170 tokens)

Update a Jules reminder

Update a reminder on the connected Jules account.

Input parameters:

- `callWindowMinutes` (integer): Optional new call lead time in minutes.
- `recurrenceDays` (array): Weekday numbers for custom recurrence, Sunday = 0 through Saturday = 6.
- `recurrenceFrequency` (string): Optional new recurrence frequency.
- `reminderId` (string, required): The Jules reminder ID to update.
- `scheduledAt` (string): Optional new reminder time as an ISO datetime string. Only use this after the user has provided or confirmed an exact time.
- `snoozeRetries` (integer): Optional new retry count.
- `timeExpression` (string): Required when changing the reminder time. Preserve the user's exact time wording, such as '4:00 PM'.
- `title` (string): Optional new reminder title.

### `delete_jules_reminder` (~78 tokens)

Delete a Jules reminder

Delete a reminder on the connected Jules account after the user has clearly identified which reminder should be removed.

Input parameters:

- `reminderId` (string, required): The Jules reminder ID to delete.
- `reminderLabel` (string, required): A human-readable label for the reminder being deleted, such as 'Order items from Waitrose at 4:00 PM today'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/peteabu-jules/mcp#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 67
- 2026-11-03: 66
- 2026-11-02: 66
- 2026-11-01: 65
- 2026-10-31: 65
- 2026-10-30: 64
- 2026-10-29: 64
- 2026-10-28: 64
- 2026-10-27: 63
- 2026-10-26: 63
- 2026-10-25: 62
- 2026-10-24: 62
- 2026-10-23: 61

## Common questions

### What is the Jules MCP server?

Jules is an MCP server listed in the public MCP registry as io.github.peteabu/jules. Create, list, update and cancel phone call reminders that ring your phone, via your Jules account. This page covers its hosted endpoint (https://mcp.heyjules.app/mcp).

### Is the Jules MCP server safe to use?

Jules scores 67 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 Jules MCP server expose?

Jules exposes 6 tools: prepare_jules_reminder, get_jules_account_status, list_jules_reminders, create_jules_reminder, update_jules_reminder, delete_jules_reminder. Their descriptions and schemas cost roughly 699 tokens of context every time the server is loaded.

### Does the Jules MCP server require authentication?

No. We connected to Jules without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Jules MCP server still maintained?

Jules is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.heyjules.app/mcp
- Website: https://www.heyjules.app/developers
- Changelog RSS feed: https://verifymcp.io/servers/peteabu-jules/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/peteabu-jules/mcp.json
- HTML version of this page: https://verifymcp.io/servers/peteabu-jules/mcp