# Up To Tech (remote · upto.tech)

Pitch Yann Ravel-Sibillot's angel fund, book a meeting, and run the deal from terms to wire.

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

## Components

- remote · `upto.tech`: 74/100 (this document), [markdown](https://verifymcp.io/servers/tech-upto-up-to-tech/upto.md), [page](https://verifymcp.io/servers/tech-upto-up-to-tech/upto)

## Channel facts

- Endpoint: `https://upto.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## 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-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1592 tokens (~159/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% 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.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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.

## Install

### How do I install the Up To Tech MCP server?

Up To Tech is a hosted endpoint at https://upto.tech/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 tech-upto-up-to-tech 'https://upto.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-upto-up-to-tech": {
      "url": "https://upto.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-upto-up-to-tech": {
      "type": "http",
      "url": "https://upto.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-upto-up-to-tech]
url = "https://upto.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-upto-up-to-tech": {
      "type": "remote",
      "url": "https://upto.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-upto-up-to-tech --url 'https://upto.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-upto-up-to-tech:
    url: "https://upto.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-upto-up-to-tech": {
      "Transport": "http",
      "Url": "https://upto.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-upto-up-to-tech -t streamable-http -u 'https://upto.tech/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-upto-up-to-tech": {
      "type": "http",
      "url": "https://upto.tech/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-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

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

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

### 2026-11-13 (score 71, +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-11-11 (score 70, +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-11-09 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 68)

First indexed and scored.

## MCP tools (10)

### `get_pitch_brief` (~35 tokens)

Get the pitch brief

Returns what Up To Tech (a business angel) asks founders, and the rules for drafting a pitch. Call this first.

### `draft_pitch` (~485 tokens)

Draft a pitch

Saves a pitch draft from what you know about the founders and returns a private link. The founders open it, review every answer, and send it themselves. Leave unknown fields empty; never invent.

Input parameters:

- `agentContact` (string): Name and email of who sends the agent's access token
- `agentScope` (string): What that agent may answer (metrics, usage, pipeline)
- `agentUrl` (string): HTTPS URL of the company's own MCP server, if any
- `builtTogether` (string): What the founders have built or survived together before, and how long they have known each other
- `call` (string): The first three people they call, and what they ask them
- `company` (string): Company or project name
- `cut` (string): What they cut first, and what they never cut
- `deck` (string): Link to a deck or demo
- `email` (string): Email Yann should reply to
- `founders` (array)
- `frustration` (string): The personal frustration behind the company: the day, the place, what happened. First person.
- `hardest` (string): The founders' hardest disagreement and how it ended
- `language` (string): Language the answers are written in, so the founders open the matching version of the site
- `location` (string): City and country
- `monday` (string): Scenario: 7 weeks of cash left and the round fell through. What the founders do today, in order.
- `oneliner` (string): What the company does, in one sentence
- `raising` (string): Amount and instrument being raised, e.g. €600k BSA AIR
- `runway` (string): Months of runway today, as a number
- `sector` (string): Field or industry
- `stage` (string): One of: Idea, Pre-seed, Seed, Later
- `teamSize` (string): Number of people on the team today
- `videoLink` (string): Link to a 90-second founder video, if one exists
- `whyNow` (string): Why this is possible now and not five years ago
- `whyYou` (string): Why this team and not a bigger team with more money
- `worstWeek` (string): Optional: the worst week a founder has lived

### `request_meeting` (~236 tokens)

Request a meeting with Yann

The only way to book 30 minutes with Yann Ravel-Sibillot (Up To Tech): for a talk, a board role, a startup or anything else. Send who the person is and what they want to cover; you get the calendar link back to give them. Ask the person for anything you do not know; never invent.

Input parameters:

- `about` (string, required): What they want to cover, 1 to 3 sentences, in their words. The more specific, the better the call.
- `agent` (string): Which LLM or agent is making the request, e.g. Claude, ChatGPT, Cursor, custom (optional)
- `company` (string): Their company or organisation, if any
- `email` (string, required): Their email, where the calendar invite goes
- `language` (string): The language the person writes in
- `name` (string, required): Full name of the person who wants the meeting (not the agent)
- `topic` (string): One of: talk (a keynote, workshop or masterclass), board (a board or advisory role), invest (their startup), other

### `deal_status` (~72 tokens)

Deal status

Where a pitch stands with Up To Tech (memo, phone interview, terms, signature, wire, done) and what the founders' agent should do next. Needs the deal token the founders received when they sent their pitch.

Input parameters:

- `deal_token` (string, required): The founders' deal token, e.g. utt_…

### `request_interview_call` (~121 tokens)

Request the interview call

Have Yann's interviewing agent phone the founder for a 15-minute interview (the step after the memo). Give the founder's mobile number in international format, and optionally the earliest time to call (ISO 8601). The founder must be expecting the call.

Input parameters:

- `deal_token` (string, required)
- `earliest_at` (string): Optional ISO 8601 date-time: do not call before this
- `language` (string): Language of the call
- `phone` (string, required): E.164, e.g. +33612345678

### `list_instruments` (~100 tokens)

List investment instruments

The investment instruments the founders can choose from (BSA-AIR, SAFE, convertible note, priced round, non-binding term sheet), when each fits, their variables, and, with a deal token, the acceptable range of every variable for this deal. Proposals inside the ranges are accepted on the spot.

Input parameters:

- `deal_token` (string): Optional: returns this deal's ranges
- `instrument` (string): Optional: ranges for this instrument only

### `propose_terms` (~120 tokens)

Propose investment terms

Propose the terms of the investment on the founders' behalf: pick an instrument and give a value for each of its variables (amounts as plain numbers in euros, percentages as numbers). Inside Yann's ranges the terms are agreed immediately and the agreement goes out for signature; outside, you get the ranges back and can propose again, or Yann answers. Confirm the terms with the founders before calling.

Input parameters:

- `deal_token` (string, required)
- `instrument` (string, required): Instrument key from list_instruments
- `terms` (object, required): Variable key -> value

### `review_document` (~98 tokens)

Review the agreement

The full text of the agreement generated from the agreed terms (or a preview of the chosen instrument's template with the current proposal), so the founders can review it with their agent before signing. The signed version is the one that binds, after the identity check.

Input parameters:

- `deal_token` (string, required)
- `instrument` (string): Optional: preview this instrument instead of the agreed one
- `terms` (object): Optional: preview with these values

### `provide_signer` (~110 tokens)

Provide the signer

Give or correct the signer's details for the agreement: full name, email and mobile number of the founder who signs for the company. The signature is an advanced electronic signature with an identity check and an SMS code, so the mobile number must be the signer's.

Input parameters:

- `deal_token` (string, required)
- `email` (string, required)
- `first_name` (string, required)
- `language` (string)
- `last_name` (string, required)
- `phone` (string, required): E.164

### `provide_bank_details` (~85 tokens)

Provide bank details

After the agreement is signed: the company's IBAN, BIC and account holder name, so the investment can be wired from Up To Tech's account. Only the company's own account.

Input parameters:

- `account_holder` (string, required): The company name as printed on the bank statement
- `bic` (string)
- `deal_token` (string, required)
- `iban` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-upto-up-to-tech/upto#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 70
- 2026-11-11: 70
- 2026-11-10: 69
- 2026-11-09: 69
- 2026-11-08: 68

## Common questions

### What is the Up To Tech MCP server?

Up To Tech is an MCP server listed in the public MCP registry as tech.upto/up-to-tech. Pitch Yann Ravel-Sibillot's angel fund, book a meeting, and run the deal from terms to wire. This page covers its hosted endpoint (https://upto.tech/mcp).

### Is the Up To Tech MCP server safe to use?

Up To Tech scores 74 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 Up To Tech MCP server expose?

Up To Tech exposes 10 tools: get_pitch_brief, draft_pitch, request_meeting, deal_status, request_interview_call, and 5 more. Their descriptions and schemas cost roughly 1,462 tokens of context every time the server is loaded.

### Does the Up To Tech MCP server require authentication?

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

### Is the Up To Tech MCP server still maintained?

Up To Tech 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 Up To Tech MCP server?

VerifyMCP ran 13 checks on Up To Tech, 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.

## Links

- Remote endpoint: https://upto.tech/mcp
- Website: https://upto.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-upto-up-to-tech/upto.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-upto-up-to-tech/upto/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tech-upto-up-to-tech/upto.json
- HTML version of this page: https://verifymcp.io/servers/tech-upto-up-to-tech/upto
