saybooks (alviso/saybooks) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 144 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

saybooks

Saybooks — open-source books an AI agent can keep: invoicing, order to cash, CRM, job hunt and personal finances over one MCP connector, with rules the agent cannot break and one audit trail for people and agents. AGPL-3.0.

→ alviso/saybooks· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

alviso

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: GOOGLE_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 1 credential: GOOGLE_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
configOTC_DATA
configOTC_DEMO
configOTC_MODULES
configOTC_PORT
configOTC_WORKSPACE
configSAYBOOKS_ADMIN
configSAYBOOKS_DATA
configSAYBOOKS_DEMO
configSAYBOOKS_MODULES
configSAYBOOKS_PORT
configSAYBOOKS_PUBLIC_URL
configSAYBOOKS_WORKSPACERegister for a Claude Code session: claude mcp add saybooks-local -e =$USER -- node <path>/mcp-server.js
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

144/144 tools missing one or more hints — bridge_export (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bridge_map_account (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bridge_accounts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +141 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 35/144 tools referenced in tests (24%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/alviso/saybooks)](https://m8ven.ai/mcp/alviso/saybooks)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9bea338fd1cd57b4c561896a880dd9b2fc13d6e8
code hash: 9885deafbc0e95bad7c988482761bf9b5184cf9aceecc6e05adf24fead9c23d6
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client