InjuryReturn

InjuryReturn — connector documentation

• MCP endpoint: https://injuryreturn.connectorbay.com/mcp
• REST API: POST https://injuryreturn.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://injuryreturn.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://injuryreturn.connectorbay.com/health · Tool schemas: https://injuryreturn.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/injuryreturn · agent@connectorbay.com

About InjuryReturn

InjuryReturn is a general, non-medical pacing reference for easing back into exercise after an injury or time off: four tools, all computed locally with no upstream calls, no accounts and no tracking.

• Graduated return plan builds a week-by-week, percentage-based volume ramp from a fraction of your pre-injury training volume up toward full volume, with a symptom check-in built into every week.
• Red-flag check compares symptoms you describe against a general list of signs that mean stop and see a clinician — worsening pain, increasing swelling, joint instability, numbness or spreading weakness, inability to bear weight, night pain, fever or redness, or a trend that's getting worse rather than better.
• Pacing principles covers general philosophy by topic: reading pain during activity, managing how fast you increase load, using cross-training, staying consistent, and warming up.
• Phase overview is a generic six-phase framework — rest, light aerobic, general movement, higher-effort drills, full training, full return — with a rule for when it's reasonable to move to the next phase.

This is general pacing philosophy, not a rehab protocol for any specific injury, and not medical advice. It is not a substitute for guidance from your doctor or physical therapist — every response here repeats that. If you're recovering from anything beyond a very minor, short-lived issue, or if any of the red-flag signs above apply to you, talk to a clinician before using a pacing framework like this one.

Built and maintained by Unify Dynamics LLC. Contact: agent@connectorbay.com.

Tools

Ramp-up plan

graduated_return_plan — A general, percentage-based graduated-return schedule: start at a fraction of your pre-injury weekly training volume and increase gradually, with a symptom check-in built into every week. NOT a rehab protocol for any specific injury. Use for "help me ease back into training after 3 weeks off with a minor issue". Args: pre_injury_sessions_per_week, pre_injury_session_minutes, weeks_available, starting_fraction, weekly_increase_pct.

Safety check

red_flag_check — Checks symptoms against a general list of signs that mean stop the activity and see a clinician. Not exhaustive and not a diagnosis. Use for "is swelling that's getting worse a reason to stop". Args: symptoms.

Philosophy

pacing_principles — General, non-medical pacing philosophy by topic: pain monitoring, load management, cross-training, consistency, warm-up/cooldown. Use for "general principles for pacing my return to exercise". Args: topic.

Framework

phase_overview — A generic six-phase return-to-activity framework with a symptom-based rule for when to advance. Use for "what are the general phases of returning to activity after an injury". Args: none.

Conventions

• Read-only. Every tool computes from bundled reference content; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input). Every response — success or error — includes a clinician_line repeating that this is not medical advice.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/injuryreturn/support

InjuryReturn — Privacy Policy

Effective 28 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What InjuryReturn is. InjuryReturn is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a general, non-medical pacing reference: a percentage-based graduated-return schedule, a red-flag symptom check, general pacing principles, and a generic phase overview. You interact with your assistant; the assistant sends us only the values needed for that one calculation or lookup.

What we receive. The arguments of each tool call — pre-injury training frequency and session length, how many weeks you want a plan to cover, a starting fraction and weekly-increase percentage if you set your own, a list of symptoms you choose to describe, or a topic name — 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.

Everything is computed on our server and nothing is stored. All reference content (red flags, pacing principles, the phase framework) is hand-curated and bundled with the server; no request is forwarded to any third party, and no query — including any symptoms you describe — is logged in request bodies, recorded, or used to train anything. We do not build a health or injury profile from your queries: each call is answered independently and nothing carries over between requests.

What we do not receive or store. We do not receive your conversation with the assistant, your name, contacts, account credentials, or any information that would identify a specific diagnosis or medical record — InjuryReturn's tools never ask for one. 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 is computed locally. Hosting: Vercel (United States regions).

Legal bases and your rights. For users in California, the EU/UK and elsewhere, our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, 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. InjuryReturn is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

InjuryReturn — Terms of Service

Effective 28 September 2026. These terms govern use of the InjuryReturn connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. InjuryReturn returns a general, non-medical pacing reference — a percentage-based graduated-return schedule, a red-flag symptom check, general pacing principles and a generic phase overview — computed from hand-curated content and simple load-progression math bundled with the server. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Not medical advice, not a rehab protocol. InjuryReturn does not diagnose, treat, or provide individualized rehabilitation guidance for any specific injury. Its output is general pacing philosophy only and is not a substitute for evaluation and guidance from your doctor or physical therapist. Any red-flag list it returns is illustrative and not exhaustive; when in doubt, seek medical attention rather than relying on this list.
3. Estimates, not prescriptions. Graduated-return percentages and week counts are simplified, general planning heuristics based on commonly cited conservative load-progression guidance, not an individualized assessment of your injury, tissue healing, or readiness. Actual healing and safe progression vary widely by person and by injury, and only a qualified clinician who has examined you can advise on your specific situation.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is answered on our server and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss, injury, or delay in seeking appropriate medical care arising from use of or reliance on the Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/injuryreturn

InjuryReturn support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://injuryreturn.connectorbay.com/mcp
• REST API: https://injuryreturn.connectorbay.com/openapi.json
• Live status: https://injuryreturn.connectorbay.com/health

When 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. InjuryReturn never asks for them.