Simpro MCP Server (ozmarks/simpro-mcp) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 22 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
54/100

Simpro MCP Server

Enables AI agents to interact with Simpro accounts, allowing natural language queries and updates to quotes, jobs, customers, and other data through the full Simpro API.

→ ozmarks/simpro-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code 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

ozmarks

Source: Glama

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

Glamanot scored here

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
⚠️
Known vulnerabilities in dependencies: 6 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
22 tools verified — handlers match their declared behaviour
13 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: SIMPRO_API_KEY, SIMPRO_CLIENT_SECRET, TOKEN_SEAL_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies6 high4 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highundici@7.27.2GHSA-hm92-r4w5-c3mj

undici vulnerable to cross-origin request routing via SOCKS5 proxy pool reuse

highundici@7.27.2GHSA-vmh5-mc38-953g

undici vulnerable to TLS certificate validation bypass via dropped requestTls in SOCKS5 ProxyAgent

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configHOSTno Network interface to bind. Defaults to 0.0.0.0 (all interfaces). Set to 127.0.0.1 to accept only same-host connections.
configMCP_PATHno Web path the server is reached at. Defaults to /mcp. (Health check is always at /healthz.)
configPUBLIC_URLto it — but the container is never the thing deciding to trust an inbound
🔐 secretSIMPRO_API_KEYDo not set in this mode — the server will refuse to start.
configSIMPRO_AUTH_MODE
configSIMPRO_AUTH_URLno Only set if your Simpro login URL is non-standard. Otherwise worked out automatically from SIMPRO_BASE_URL.
configSIMPRO_CLIENT_IDyes From your Simpro OAuth app.
🔐 secretSIMPRO_CLIENT_SECRETyes From your Simpro OAuth app. Keep it secret.
configSIMPRO_COMPANY_IDno Your company ID. Defaults to 0.
configSIMPRO_ENV_FILE
configSIMPRO_TOKEN_URLno Same — only set if non-standard.
configSIMPRO_TRANSPORTTo use this mode, set =proxy (the supplied Docker setup defaults to the
configSIMPRO_VERSION_CHECK
configSIMPRO_VERSION_CHECK_URL
configSTATIC_CLIENTS
🔐 secretTOKEN_SEAL_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

All four hints declared on every tool

19/22 tools missing one or more hints — find_work (missing: destructiveHint, idempotentHint, openWorldHint); get_work (missing: destructiveHint, idempotentHint, openWorldHint); create_work (missing: destructiveHint, idempotentHint, openWorldHint), +16 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 2/22 tools referenced in tests (9%)

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

Shell command execution

3 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 6 high severity in production deps — @modelcontextprotocol/sdk@1.12.0 (high), @modelcontextprotocol/sdk@1.12.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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 5 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 Verified](https://m8ven.ai/badge/mcp/ozmarks/simpro-mcp?variant=verified)](https://m8ven.ai/mcp/ozmarks/simpro-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 70d29d70516a524410db4044fb145dccd9d3c82f
code hash: d07ec3e39a4a4a11f6063441386db35d866edea612ab1158b2cdb8bda9fe77c7
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