Corn Intelligence MCP Server (thaivu98/mcp-platform) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 19 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
50/100

Corn Intelligence MCP Server

A high-performance MCP server integrated with a Django analytics dashboard, featuring 19 tools for AI interaction tracking, AST code analysis, and real-time token efficiency metrics.

→ thaivu98/mcp-platform· 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

⚡ 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

thaivu98

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
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — corn_changes (line 315: res = subprocess.check_output(["git", "log", "-n", "5", "--oneline"], text=True))
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: DB_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes19 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

corn_session_start

Begin a tracked work session.

corn_session_end

End session with summary and decisions.

corn_health

System health — services, uptime, version.

corn_memory_store

Store agent memory with tags.

corn_memory_search

Semantic/Keyword similarity search over memories.

corn_knowledge_store

Store a shared knowledge item.

corn_knowledge_search

Semantic search over knowledge base.

corn_code_read

Read raw source code from indexed repos.

corn_detect_changes

Uncommitted changes cross-referenced with graph.

corn_list_repos

List indexed repositories with symbol counts.

corn_code_search

Hybrid vector/AST symbol search.

corn_code_context

360° symbol view: callers, callees, hierarchy.

corn_code_impact

Blast radius analysis with recursive CTE.

corn_cypher

Cypher-to-SQL graph queries (Simplified).

corn_tool_stats

View tool usage analytics and trends.

corn_quality_report

Submit 4-dimension quality report (must ≥80%).

corn_record_conversation

Record the token usage of current chat interaction.

corn_plan_quality

Score a plan against 8 criteria (must >=80%).

corn_changes

Check for recent commits by other agents.

// 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.
configDB_NAME
configDB_USER
🔐 secretDB_PASSWORD
configDB_HOST
configDB_PORT
// 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

19/19 tools missing one or more hints — corn_session_start (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); corn_session_end (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); corn_health (missing: readOnlyHint, 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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — corn_changes (line 315: res = subprocess.check_output(["git", "log", "-n", "5", "--oneline"], text=True))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

14/19 tool handlers declare input schemas (74%)

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

Tool handlers catch errors

Only 3/19 tool handlers wrap calls in try/catch (16%)

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.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

corn_changes: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 8 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/thaivu98/mcp-platform?variant=verified)](https://m8ven.ai/mcp/thaivu98/mcp-platform)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 9b0073dec8310003afd962b0278906ae6b43d63e
code hash: b4fcbf81cdaf67770dbcfedb6c437ed89c0735920ca5f8cee7a7186aa972809e
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