MCP servers › io.github.stanislav-petryashov › monido
MCP server · registry snapshot 2026-11-18 · last checked 2026-11-18
monido MCP server
Registry name io.github.stanislav-petryashov/monido
by stanislav-petryashov · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗
Self-hosted family finance with an AI advisor: can we afford it? Net worth, loans, goals, statements — the publisher's description
Summary
io.github.stanislav-petryashov/monido is a remote MCP server listed in the official MCP registry at version 1.9.0, under the namespace of the GitHub account stanislav-petryashov. Its linked repository, github.com/stanislav-petryashov/monido, belongs to the same GitHub account.
Record checks
5 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- #2,559 of 28,859 repositories by GitHub stars, tied with 85 others
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 1.9.0, published 2026-11-18 (registry, as of the 2026-11-18 snapshot)
- First listed version
- 2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 14 versions listed, 2026-11-16 to 2026-11-18; 14 in the 90 days before the 2026-11-18 snapshot.(versions still listed in the registry only)
Most recent 12 versions
1.9.0· 2026-11-181.8.3· 2026-11-171.8.2· 2026-11-171.8.1· 2026-11-171.8.0· 2026-11-171.7.0· 2026-11-171.6.1· 2026-11-161.6.0· 2026-11-161.5.0· 2026-11-161.4.0· 2026-11-161.3.0· 2026-11-161.2.0· 2026-11-16
- Registry data
- snapshot 2026-11-18
- Package and repository
- checked 2026-11-18
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 1.7.0 (published 2026-11-17) → 1.9.0 (published 2026-11-18), between the registry lists of 2026-11-17 and 2026-11-18.
The publisher’s GitHub release note for v1.9.0 (“Monido 1.9.0”), published 2026-11-18.
Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
### Changed
- **The database is updated on start (schema version 3).** Before the update the server writes a copy of the database, `before-upgrade-v2-<date>.sqlite`, next to it in the data folder; delete it once the new version works. An older release cannot open the updated database: to go back, restore that copy or a backup made before the update. The closings of accounts are kept one per closing (`account_closings`, filled from `account_closures`, which goes); an older backup restores and is updated too.
### Fixed
- Review fixes: an early payment that holds interest is judged by the principal the bank credited; undoing a property rename is refused when the old name was taken by another property or a loan was linked to the new name since; undoing a one-balance account rename is refused while its closings stay under the new name; two people with no live member never share an id after a restore; a goal editor keeps the goal it opened on; a Telegram supergroup paired already keeps its own settings, and a refused resend does not count as today's reminder; a demo tab notices a fresh sandbox at once; a day or month with surplus digits is not read; gridline labels share one precision.
- Restoring a backup into an installation whose users were created in another order no longer gives the family proposals' authorship and votes to other people: they follow the member.
- A double click on "Add standard categories" adds them once, instead of a false "Could not save".
- Only one database copy is downloaded at a time; downloads left hanging no longer each hold a copy in memory.
- A date typed in another order than the field's (a day-first date in a year-first field) is left unread instead of saved as another day; a pasted "(500)" or "500-" is a minus; a pasted "1e5" or "1.5k" is refused instead of read as another number.
- Chart and amount texts: no "−0" or "NaN" in short amounts, gridline labels that never repeat (Chinese 亿), and no "+" beside an amount hidden in privacy mode.
- A demo tab brought back after "Start over" in another tab reads the fresh sandbox; the history template downloads in Safari; pairing a Telegram group works with the device clock off; Escape in a menu inside a window closes only the menu; an amount in its own currency is hidden in privacy mode too.
- An account name that was closed, used again and closed again keeps both closings: the months between its two lives no longer lose their net worth, and reopening the later month keeps the earlier closing. A closing already overwritten before this update cannot be brought back, so those months stay incomplete.
- Reminders and proposal notices follow a Telegram group that was upgraded to a supergroup (it gets a new id); they used to stop silently while Settings still showed the group as connected.
- A group the bot was removed from no longer gets a retry of every proposal notice on every run, nor the whole backlog when the bot is added back: its notices are switched off.
- A group gets one notice per proposal with its status now, instead of one per vote or change.
- If Telegram sign-in was switched off at start, Settings now offers "Stay on the family password", and the bot can no longer be disconnected meanwhile: it used to come back in Telegram mode with no bot after a restart, and nobody could sign in.
- Signing out also ends a manager's confirmed test sign-in in that browser, so the next person signing in there cannot switch the sign-in mode with it.
- A sign-out the server did not answer keeps you signed in and says so, instead of showing the sign-in screen over a live session.
- After the sign-in mode is switched on another device, an open tab shows the new sign-in screen instead of the old one.
- The rights of a user added under the family password while nobody manages can be changed again ("last manager" was refused).
- The setup wizard asks for the typed word before loading test data whenever it cannot be sure there is no data.
- A family member can no longerSource: the official MCP Registry list on 2026-11-17 and on 2026-11-18; release notes from the GitHub Releases API, checked 2026-11-18.
What it is
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://{host}/mcpCursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"monido": {
"url": "https://{host}/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"monido": {
"type": "http",
"url": "https://{host}/mcp"
}
}
}Claude Code
claude mcp add --transport http monido "https://{host}/mcp"Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"monido": {
"type": "streamableHttp",
"url": "https://{host}/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"monido": {
"httpUrl": "https://{host}/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.monido]
url = "https://{host}/mcp"Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"monido": {
"url": "https://{host}/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url "https://{host}/mcp" --transport http- The URL contains parts in { } that the entry marks as variables; replace them with your own values.
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-18. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-18. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-18. Source: read 2026-11-18.
- Cline marketplace. Not in the Cline marketplace on 2026-11-18. Source: read 2026-11-18.
Own host
- security.txt. No security.txt at https://monido.dev/.well-known/ (HTTP 404, 2026-11-18). Source: monido.dev/.well-known/security.txt · read 2026-11-18.
- A2A agent card. No A2A agent card at https://monido.dev/.well-known/ (HTTP 404, 2026-11-18). Source: monido.dev/.well-known/agent-card.json · read 2026-11-18.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Repository github.com/stanislav-petryashov/monido | Opens publicly | matches | api.github.com · 2026-11-18 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.stanislav-petryashov
- GitHub owner
- a personal account (stanislav-petryashov)
- Repository
- github.com/stanislav-petryashov/monido
- Stars
- 15
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-18; security policy read from GitHub · 2026-11-16.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating5 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- #2,559 of 28,859 repositories by GitHub stars, tied with 85 others
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-18 (security policy 2026-11-16). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.stanislav-petryashov/monido
Answered from the data aboveWho publishes io.github.stanislav-petryashov/monido?
The registry ties the namespace io.github.stanislav-petryashov to the GitHub account stanislav-petryashov; only its owner can publish under it. Its linked repository, github.com/stanislav-petryashov/monido, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.stanislav-petryashov/monido safe to install?
We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.stanislav-petryashov/monido been security tested?
No. It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it.
Does io.github.stanislav-petryashov/monido publish a security policy?
Yes: its repository has a public security policy (github.com/stanislav-petryashov/monido/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Where is the source code of io.github.stanislav-petryashov/monido?
In github.com/stanislav-petryashov/monido, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. — the server's own choice
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.stanislav-petryashov/monido: MCP server record.” Data checked 2026-11-18. https://protocolprobe.com/mcp/servers/io.github.stanislav-petryashov/monido
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.stanislav-petryashov/monido)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology