Trainplan
Computed couch-to-5k through marathon training plans — 10% rule, cutback weeks, taper — from your level and weeks available
Bouldering training-log analytics — grade pyramid, hardest-grade tracker, attempts-to-send ratio, next-grade projection
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
grade_pyramidgrade_pyramidhardest_grade_progressionhardest_grade_progressionattempts_to_send_ratioattempts_to_send_rationext_grade_projectiontraining_log_summarygrade_conversion_tablegrade_conversion_tableClimbGrade is a fully local bouldering training-log analytics connector — distinct from the sibling ascent connector, which is climbing gear/technique/safety reference with no training-log concept at all. Every training-log tool takes session_log (a list of {date, grade, attempts, sent} objects, grade as a V-scale string like 'V4' or 'VB') as a plain argument each call; nothing is stored server-side between calls. grade_pyramid groups sent sessions by V-scale tier and checks the shape against the classic wide-base pattern, flagging any tier with more sends than an easier tier below it — a common top-heavy/plateau warning sign. hardest_grade_progression sorts the log chronologically regardless of input order and reports the running hardest grade sent as of each session's date. attempts_to_send_ratio groups every session by grade and reports total attempts, sends, attempts-per-send and send rate per tier. next_grade_projection fits an ordinary least-squares trend line to sent grades over time and extrapolates a rough next-grade estimate for a caller-chosen horizon, needing at least two sent sessions on different dates and explicitly caveated as a rough estimate, never a guarantee. training_log_summary runs all four in one call. grade_conversion_table converts between V-scale, Font, YDS, French and UIAA off a compact 14-row reference table — smaller and coarser than ascent's fuller, independently cross-checked table — enough to translate an occasional roped-route grade into its V-scale bucket before logging it. General fitness/hobby tracking, not medical, coaching, or injury-risk advice. Keyless; fully local; zero upstream calls; nothing stored.
Sources: Computed locally from the training log you provide on each call (grade pyramid, hardest-grade-over-time tracker, attempts-to-send ratio, ordinary-least-squares next-grade trend projection); the V-scale/Font/YDS/French/UIAA reference table is a hand-curated, compact dataset (14 rows), smaller and coarser than the sibling ascent connector's fuller table. Nothing is stored between calls; fully local, zero upstream calls.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
6 tools, grouped by job. Every one is read-only or compute-only.
https://climbgrade.connectorbay.com/mcpComputed couch-to-5k through marathon training plans — 10% rule, cutback weeks, taper — from your level and weeks available
A hand-curated, sport-agnostic fantasy sports reference — formats, drafts, rules and terms
A hand-curated badminton reference — rules, technique how-tos, gear and match formats
A hand-curated table tennis reference — rules, scoring, technique and equipment
A fully local Brazilian football history and facts reference — World Cups, Copa América, legends and trivia
A hand-curated Indian cricket reference — IPL, World Cups, rules and trivia
ascentThe sibling ascent connector is a climbing reference toolkit: a fuller, independently cross-checked
grade-conversion table, a gear glossary, belay-technique and climbing-discipline explainers, safety-system
concepts, a climbing-knot subset, and warmup/injury-prevention guidance. It has no concept of a training log.
ClimbGrade is a training-log analytics connector. Its own grade-conversion table is intentionally smaller and
reference-only — 14 milestone rows (VB through V12) — just enough to translate an occasional roped-route grade
into its approximate V-scale bucket so a mixed indoor/outdoor log stays comparable on one axis. The reason
ClimbGrade exists, and the majority of its tools, is real statistics computed over a caller-supplied training log
— something ascent does not have at all.
"Build my grade pyramid from this log", "what's my hardest grade sent over time", "what's my attempts-to-send ratio by grade", "at this rate, what grade might I be sending in two months" — turning a plain list of climbing sessions into the statistics climbers actually track to gauge their own progress.
ClimbGrade is stateless: every training-log tool takes session_log — a list of {date, grade, attempts,
sent} objects, where grade is a V-scale string like "V4" or "VB" — as a plain argument on every call.
Nothing is stored server-side between calls; the caller is the source of truth and re-sends the log each time,
exactly like the other tracker-style connectors in this catalogue.
grade_pyramid groups sent sessions by V-scale tier and checks the shape against the classic "wide base,
narrower near your limit" pattern, flagging any tier with more sends than an easier tier below it — a common
top-heavy/plateau warning sign, not a badge of honor. hardest_grade_progression sorts the log chronologically
(regardless of the order sessions were passed in) and reports the running hardest grade sent as of each session's
date. attempts_to_send_ratio groups every session — sent or not — by grade and reports total attempts, sends,
attempts-per-send, and send rate per tier. next_grade_projection fits an ordinary least-squares trend line to
sent grades over time and extrapolates a rough next-grade estimate for a caller-chosen horizon; it needs at least
two sent sessions on two different dates, and its result is explicitly caveated as a rough trend extrapolation,
never a guarantee or a coaching plan. training_log_summary runs all four over the same log in one call.
grade_conversion_table converts between V-scale, Font, YDS, French and UIAA using the compact 14-row table.
Not medical, coaching, or injury-risk advice — general fitness/hobby tracking and arithmetic over the numbers you
provide. next_grade_projection is a straight-line extrapolation of past data, not a prediction: it cannot see
plateaus, injuries, gear changes, or technique breakthroughs, and should be treated as one input, not a forecast.
ClimbGrade's own grade table is deliberately smaller and coarser than ascent's; for a fuller, finer-grained,
independently cross-checked grade-conversion reference, use the sibling /ascent connector.
Effective 28 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What ClimbGrade is. ClimbGrade is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf to compute bouldering training-log statistics — a grade pyramid, a hardest-grade-over-time tracker, an attempts-to-send ratio, a next-grade trend projection — and to convert climbing grades between V-scale, Font, YDS, French and UIAA. You interact with your assistant; the assistant sends us only the arguments needed for that one calculation.
General fitness/hobby tracking, not medical or coaching advice. ClimbGrade is general fitness and hobby tracking, arithmetic and trend-fitting over the numbers you supply. It is not medical advice, not a certified coaching program, and performs no real injury-risk assessment. See our Terms of Service for the full disclaimer; this policy covers data handling only.
What we receive. The arguments of each tool call — most notably, when you use a training-log tool, the session log you supply that call (dates, V-scale grades, attempt counts, and whether each session was sent) — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.
Nothing is stored between calls. ClimbGrade is stateless by design: your training log exists only for the duration of the single request that includes it, is used only to compute that request's answer, and is discarded immediately afterward — it is never written to a database, a file, or any persistent store, and it is not retained to build a profile across your calls. Each request's session log must be resupplied on the next call if you want continuity; we do not keep it for you. The grade-conversion table is a small, bundled, hand-curated reference file; nothing is fetched from any third party to answer any tool call — there is no upstream call at all, live or otherwise.
What we do not receive or store. We do not receive your conversation with the assistant or your name. Rate- limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.
Sub-processors. None — every tool computes locally from the numbers you provide. Hosting: Vercel (United States regions).
Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs and rate-limit counters, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.
Children. ClimbGrade is a general-audience service operated by the adult using the assistant.
Changes. We will post changes here with a new effective date.
Effective 28 September 2026. These terms govern use of the ClimbGrade connector ("the Service") operated by Unify Dynamics LLC ("we", "us"), Menlo Park, California.
next_grade_projection is a straight-line (ordinary least-squares)
extrapolation of grades you report having sent in the past. It cannot see plateaus, injuries, rest periods,
gear changes, technique breakthroughs, or anything else that shapes real progress, and it is not a promise,
forecast, or coaching plan. Treat any projected grade as one rough input among many, never as a target you are
entitled to reach on schedule./ascent connector's fuller,
independently cross-checked table.Email agent@connectorbay.com. We answer within two business days.
https://climbgrade.connectorbay.com/mcphttps://climbgrade.connectorbay.com/openapi.jsonWhen you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. ClimbGrade never asks for them.