
Osewa
io.github.ushiosPublished by GitHub account ushiosv1.71.0Updated Oct 31, 2026
Track and share care records for babies and plants: feedings, diapers, sleep, and watering.
Overview
Remote MCP server for Osewa that lets an assistant track and share care records for babies and plants, such as feedings, diapers, sleep and watering.
- What you can do
- Record and follow care events for babies, including feedings, diapers and sleep.
- Track plant care such as watering.
- Share care records with other people.
- No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Useful when a household or caregiver group wants an assistant to log and review everyday baby and plant care in one shared place, for example keeping track of feeds, naps or watering schedules.
- Requirements
- A remote MCP endpoint at mcp.osewa.site over streamable HTTP. Authentication is required: an Authorization header carrying a personal access token in the form Bearer osewa_..., issued to a signed-in human in the Osewa account settings. Agents cannot register themselves, so the operator must supply the token.
Installation
In SourceWeft
- Open Osewa in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.ushios%2Fosewa/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"osewa": {
"type": "http",
"url": "https://mcp.osewa.site/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
25- v1.71.0LatestOct 31, 2026
- v1.70.0Oct 26, 2026
- v1.69.1Oct 24, 2026
- v1.69.0Oct 22, 2026
- v1.68.0Oct 22, 2026
- v1.67.0Oct 20, 2026
- v1.66.0Oct 19, 2026
- v1.65.0Oct 18, 2026
- v1.64.0Oct 18, 2026
- v1.63.0Oct 15, 2026
- v1.62.0Oct 11, 2026
- v1.61.0Oct 8, 2026
- v1.60.1Oct 7, 2026
- v1.59.1Oct 7, 2026
- v1.59.0Oct 6, 2026
- v1.58.1Oct 6, 2026
- v1.58.0Oct 6, 2026
- v1.57.0Sep 24, 2026
- v1.56.3Sep 24, 2026
- v1.56.2Sep 24, 2026
- v1.56.1Sep 20, 2026
- v1.56.0Sep 20, 2026
- v1.54.0Sep 18, 2026
- v1.53.1Sep 17, 2026
- v1.53.0Sep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.