Up To Tech
REMOTE · UPTO.TECH
Pitch Yann Ravel-Sibillot's angel fund, book a meeting, and run the deal from terms to wire.
Available components
Last scanned (18 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 1592 tokens (~159/item across 10 items; 10 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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 19 Nov 26 +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.
- 17 Nov 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.
- 15 Nov 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.
- 13 Nov 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.
- 11 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.
- 9 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 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 21 Nov 2026 · Probed https://upto.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=upto.tech | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d1befa10c9fa076f0e2b24725b4e720f |
| SANs: upto.tech | ||||||
| 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 upto.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | DS published | 2185 | 13 | Verified |
| upto.tech. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://upto.tech/mcp | Verified | 200 | |
| http (plaintext) | http://upto.tech/mcp | HTTPS enforced | 301 | https://upto.tech/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 →
deal_status Deal status ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_token | string | yes | The founders' deal token, e.g. utt_… |
No output schema declared.
No examples provided.
draft_pitch Draft a pitch ~485
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| 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 |
No output schema declared.
No examples provided.
get_pitch_brief Get the pitch brief ~35
Returns what Up To Tech (a business angel) asks founders, and the rules for drafting a pitch. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_instruments List investment instruments ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_token | string | – | Optional: returns this deal's ranges |
| instrument | string | – | Optional: ranges for this instrument only |
No output schema declared.
No examples provided.
propose_terms Propose investment terms ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_token | string | yes | – |
| instrument | string | yes | Instrument key from list_instruments |
| terms | object | yes | Variable key -> value |
No output schema declared.
No examples provided.
provide_bank_details Provide bank details ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_holder | string | yes | The company name as printed on the bank statement |
| bic | string | – | – |
| deal_token | string | yes | – |
| iban | string | yes | – |
No output schema declared.
No examples provided.
provide_signer Provide the signer ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_token | string | yes | – |
| string | yes | – | |
| first_name | string | yes | – |
| language | string | – | – |
| last_name | string | yes | – |
| phone | string | yes | E.164 |
No output schema declared.
No examples provided.
request_interview_call Request the interview call ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_token | string | yes | – |
| earliest_at | string | – | Optional ISO 8601 date-time: do not call before this |
| language | string | – | Language of the call |
| phone | string | yes | E.164, e.g. +33612345678 |
No output schema declared.
No examples provided.
request_meeting Request a meeting with Yann ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | yes | 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 |
| string | yes | Their email, where the calendar invite goes | |
| language | string | – | The language the person writes in |
| name | string | yes | 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 |
No output schema declared.
No examples provided.
review_document Review the agreement ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_token | string | yes | – |
| instrument | string | – | Optional: preview this instrument instead of the agreed one |
| terms | object | – | Optional: preview with these values |
No output schema declared.
No examples provided.
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.
remote · upto.tech
claude mcp add --transport http tech-upto-up-to-tech 'https://upto.tech/mcp'
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.