_ registry / mcp streamable-http · checked 57m ago

up-to-tech

https://upto.tech

Registry code: 966d5e927f0181e2

api record

To pitch a startup: call get_pitch_brief, then draft_pitch with what you know, and give the founders the returned link. To book 30 minutes with Yann (the only way to book): call request_meeting with the person's name, email, topic and what they want to cover, and give them the booking link. After a pitch is sent, the founders hold a deal token (utt_…): use deal_status to see the step, request_interview_call for the phone interview, list_instruments and propose_terms to agree the investment terms, provide_signer and provide_bank_details for the signature and the wire.

endpoint
https://upto.tech/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is up-to-tech live?
Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is up-to-tech free to use?
Yes — the hub reached it with no key and no payment.
What tools does up-to-tech have?
10 tools: provide_bank_details, draft_pitch, deal_status, request_interview_call, propose_terms, review_document, provide_signer, request_meeting, ….
Is up-to-tech safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
650ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
2 open 8 never probed 2 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_instruments open 57m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "deal_token": {
      "type": "string",
      "description": "Optional: returns this deal's ranges"
    },
    "instrument": {
      "type": "string",
      "description": "Optional: ranges for this instrument only"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_pitch_brief open 57m ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • provide_bank_details unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "deal_token",
    "iban",
    "account_holder"
  ],
  "properties": {
    "bic": {
      "type": "string"
    },
    "iban": {
      "type": "string"
    },
    "deal_token": {
      "type": "string"
    },
    "account_holder": {
      "type": "string",
      "description": "The company name as printed on the bank statement"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • draft_pitch unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "cut": {
      "type": "string",
      "description": "What they cut first, and what they never cut"
    },
    "call": {
      "type": "string",
      "description": "The first three people they call, and what they ask them"
    },
    "deck": {
      "type": "string",
      "description": "Link to a deck or demo"
    },
    "email": {
      "type": "string",
      "description": "Email Yann should reply to"
    },
    "stage": {
      "type": "string",
      "description": "One of: Idea, Pre-seed, Seed, Later"
    },
    "monday": {
      "type": "string",
      "description": "Scenario: 7 weeks of cash left and the round fell through. What the founders do today, in order."
    },
    "runway": {
      "type": "string",
      "description": "Months of runway today, as a number"
    },
    "sector": {
      "type": "string",
      "description": "Field or industry"
    },
    "whyNow": {
      "type": "string",
      "description": "Why this is possible now and not five years ago"
    },
    "whyYou": {
      "type": "string",
      "description": "Why this team and not a bigger team with more money"
    },
    "company": {
      "type": "string",
      "description": "Company or project name"
    },
    "hardest": {
      "type": "string",
      "description": "The founders' hardest disagreement and how it ended"
    },
    "raising": {
      "type": "string",
      "description": "Amount and instrument being raised, e.g. €600k BSA AIR"
    },
    "agentUrl": {
      "type": "string",
      "description": "HTTPS URL of the company's own MCP server, if any"
    },
    "founders": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "link": {
            "type": "string",
            "description": "LinkedIn or GitHub URL"
          },
          "name": {
            "type": "string",
            "description": "Full name"
          },
          "role": {
            "type": "string",
            "description": "Role, e.g. CEO, CTO"
          },
          "known": {
            "type": "string",
            "description": "Their unfair advantage: what they know or have done that almost nobody else has"
          },
          "fulltime": {
            "type": "string",
            "description": "One of: Full time, Part time, Joining at funding"
          }
        },
        "additionalProperties": false
      },
      "maxItems": 6
    },
    "language": {
      "enum": [
        "en",
        "fr",
        "es"
      ],
      "type": "string",
      "description": "Language the answers are written in, so the founders open the matching version of the site"
    },
    "location": {
      "type": "string",
      "description": "City and country"
    },
    "oneliner": {
      "type": "string",
      "description": "What the company does, in one sentence"
    },
    "teamSize": {
      "type": "string",
      "description": "Number of people on the team today"
    },
    "videoLink": {
      "type": "string",
      "description": "Link to a 90-second founder video, if one exists"
    },
    "worstWeek": {
      "type": "string",
      "description": "Optional: the worst week a founder has lived"
    },
    "agentScope": {
      "type": "string",
      "description": "What that agent may answer (metrics, usage, pipeline)"
    },
    "frustration": {
      "type": "string",
      "description": "The personal frustration behind the company: the day, the place, what happened. First person."
    },
    "agentContact": {
      "type": "string",
      "description": "Name and email of who sends the agent's access token"
    },
    "builtTogether": {
      "type": "string",
      "description": "What the founders have built or survived together before, and how long they have known each other"
    }
  },
  "additionalProperties": false
}
    arguments 137 lines
  • deal_status unknown 57m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "deal_token"
  ],
  "properties": {
    "deal_token": {
      "type": "string",
      "description": "The founders' deal token, e.g. utt_…"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • request_interview_call unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "deal_token",
    "phone"
  ],
  "properties": {
    "phone": {
      "type": "string",
      "description": "E.164, e.g. +33612345678"
    },
    "language": {
      "enum": [
        "en",
        "fr",
        "es"
      ],
      "type": "string",
      "description": "Language of the call"
    },
    "deal_token": {
      "type": "string"
    },
    "earliest_at": {
      "type": "string",
      "description": "Optional ISO 8601 date-time: do not call before this"
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • propose_terms unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "deal_token",
    "instrument",
    "terms"
  ],
  "properties": {
    "terms": {
      "type": "object",
      "description": "Variable key -> value",
      "additionalProperties": true
    },
    "deal_token": {
      "type": "string"
    },
    "instrument": {
      "type": "string",
      "description": "Instrument key from list_instruments"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • review_document unknown 28h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "deal_token"
  ],
  "properties": {
    "terms": {
      "type": "object",
      "description": "Optional: preview with these values",
      "additionalProperties": true
    },
    "deal_token": {
      "type": "string"
    },
    "instrument": {
      "type": "string",
      "description": "Optional: preview this instrument instead of the agreed one"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • provide_signer unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "deal_token",
    "first_name",
    "last_name",
    "email",
    "phone"
  ],
  "properties": {
    "email": {
      "type": "string"
    },
    "phone": {
      "type": "string",
      "description": "E.164"
    },
    "language": {
      "enum": [
        "en",
        "fr",
        "es"
      ],
      "type": "string"
    },
    "last_name": {
      "type": "string"
    },
    "deal_token": {
      "type": "string"
    },
    "first_name": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 37 lines
  • request_meeting unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "email",
    "about"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Full name of the person who wants the meeting (not the agent)"
    },
    "about": {
      "type": "string",
      "description": "What they want to cover, 1 to 3 sentences, in their words. The more specific, the better the call."
    },
    "agent": {
      "type": "string",
      "description": "Which LLM or agent is making the request, e.g. Claude, ChatGPT, Cursor, custom (optional)"
    },
    "email": {
      "type": "string",
      "description": "Their email, where the calendar invite goes"
    },
    "topic": {
      "enum": [
        "talk",
        "board",
        "invest",
        "other"
      ],
      "type": "string",
      "description": "One of: talk (a keynote, workshop or masterclass), board (a board or advisory role), invest (their startup), other"
    },
    "company": {
      "type": "string",
      "description": "Their company or organisation, if any"
    },
    "language": {
      "enum": [
        "en",
        "fr",
        "es"
      ],
      "type": "string",
      "description": "The language the person writes in"
    }
  },
  "additionalProperties": false
}
    arguments 50 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 966d5e927f0181e2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/966d5e927f0181e2/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/966d5e927f0181e2/badge.svg)](https://brick.blue/agent/966d5e927f0181e2?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.