DongneSOS MCP (kjessie00/dongnesos-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 2 tools. No publisher has claimed this listing.

C
Emerging
74/100
2 months ago

DongneSOS MCP

Helps users prepare Korean neighborhood inconvenience reports by classifying issues, explaining evidence, and drafting neutral reports without submitting them.

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

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

kjessie00

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 →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// 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.
configBUNDLE_VERIFY_OUT
configCONFIRM_EXTERNAL_IMAGE_PUSHDRY_RUN=0 =1.
configDEPLOYED_ENDPOINT_URL
configDEPLOY_BUNDLE_DIR
configDEPLOY_BUNDLE_MANIFEST
configDEPLOY_BUNDLE_NAME
configDEPLOY_BUNDLE_SHA256
configDEPLOY_BUNDLE_TARBALL
configDOCKER_IMAGE
configDOCKER_IMAGE_REPO
configDOCKER_IMAGE_TAG
configDOCKER_PLATFORM
configDOCKER_SMOKE_EVIDENCE
configDRY_RUN0 CONFIRM_EXTERNAL_IMAGE_PUSH=1.
configEVIDENCE_OUTdeploy/playmcp/evidence/remote-smoke.json \
configHEALTH_URL
configHOST
configIMAGE_PUSH_EVIDENCE
configIMAGE_PUSH_EVIDENCE_OUT
configJESSIE_FINAL_SUBMIT_APPROVED
configLOCAL_DOCKER_IMAGE
configLOCAL_RELEASE_SUMMARY
configMCP_URL
configPLAYMCP_TEMP_REGISTRATION_STATUS
configRELEASE_SUMMARY_OUT
configREMOTE_SMOKE_EVIDENCE
configSUBMISSION_EVIDENCE_OUT
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

2/2 tools missing one or more hints — classify_civic_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); draft_civic_report (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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 0/2 tool handlers declare input schemas (0%)

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

Tool handlers catch errors

Only 0/2 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

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

Tool test coverage

Only 0/2 tools referenced in tests (0%)

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 6 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/kjessie00/dongnesos-mcp)](https://m8ven.ai/mcp/kjessie00/dongnesos-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2b75a54a211c77a5c92cf5ab293dc906f3204042
code hash: 33cde1aedf830e3f73034c8b45f9b559ec65a4903322fc1a7e43660c168e3d3d
verified: 6/22/2026, 12:26:26 PM
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