appfolio-mcp-server (CryptoCultCurt/appfolio-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 44 out of 100, grade D. It declares 47 tools. No publisher has claimed this listing.

D
Caution
44/100

appfolio-mcp-server

MCP (Model Context Protocol) Server for AI Agents to access the Appfolio Reporting API

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

CryptoCultCurt

Source: Official · also listed on Glama, ModelScope, 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 →

Install from

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: PASSWORD. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 16 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: PIPEDREAM_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies16 high4 medium10 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.17.2GHSA-345p-7cg4-v4c7

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

highaxios@1.6.7GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.6.7GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

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.
configBYPASS_AUTH_FOR_TESTING
configCORS_ORIGIN
configHTTP_PORT
configHYBRID_MODE
configINSPECTOR_MODE
configMCP_MODE
configOAUTH_AUDIENCE
configOAUTH_ISSUER
configOAUTH_JWKS_JSON
configOAUTH_JWKS_URL
configOAUTH_PROXY_AUTHORIZATION_URL
configOAUTH_PROXY_REGISTRATION_URL
configOAUTH_PROXY_REVOCATION_URL
configOAUTH_PROXY_TOKEN_URL
configOAUTH_RESOURCE_METADATA_URL
configOAUTH_SCOPES_SUPPORTED
configOAUTH_SERVICE_DOC_URL
configPIPEDREAM_CLIENT_ID
🔐 secretPIPEDREAM_CLIENT_SECRET
configPIPEDREAM_PROJECT_ID
configRESOURCE_SERVER_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

47/47 tools missing one or more hints — get_account_totals_report (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_aged_payables_summary_report (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_aged_receivables_detail_report (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +44 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 inputs are validated

Only 8/47 tool handlers declare input schemas (17%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (PASSWORD → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Production dependencies are patched

0 critical, 16 high severity in production deps — @modelcontextprotocol/sdk@1.17.2 (high), @modelcontextprotocol/sdk@1.17.2 (high)

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

Dependency freshness

1/11 production deps stale: bottleneck@2023-02-22 (3.5y)

Domain consistency

npm scope @fluegeldao doesn't match GitHub owner cryptocultcurt

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 7 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/cryptocultcurt/appfolio-mcp-server?variant=verified)](https://m8ven.ai/mcp/cryptocultcurt/appfolio-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 98fa0c0535703a8d9367fd0fcd9f474500f7ffd7
code hash: 772db8331d9cb7751b78776cc09a74c19e407b9ba7e677990b19327ab918b65a
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