mcp-json-yaml-toml (bitflight-devops/mcp-json-yaml-toml) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

mcp-json-yaml-toml

A token-efficient, schema-aware MCP server that enables AI assistants to safely read, modify, query, and validate JSON, YAML, and TOML files with automatic schema detection and format conversion capabilities.

→ bitflight-devops/mcp-json-yaml-toml· 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

bitflight-devops

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 annotations don’t match behaviour
2 read-only tools perform write/delete/exec — data_convert (line 83: out_path.write_text(result.stdout, encoding="utf-8")); data_merge (line 185: out_path.write_text(merge_result.stdout, encoding="utf-8"))
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: GITHUB_TOKEN, GH_TOKEN
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.
configYQ_VERSION
🔐 secretGITHUB_TOKEN
🔐 secretGH_TOKEN
configYQ_BINARY_PATH
configMCP_CONFIG_FORMATS
configMCP_JYT_LOG_LEVEL
configMCP_JYT_LOG_FILE
configMCP_JYT_LOG_CONSOLE
configMCP_SCHEMA_CACHE_DIRS
// quality suggestions

Tool annotations match behaviour

2 read-only tools perform write/delete/exec — data_convert (line 83: out_path.write_text(result.stdout, encoding="utf-8")); data_merge (line 185: out_path.write_text(merge_result.stdout, encoding="utf-8"))

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Tool inputs are validated

7/8 tool handlers declare input schemas (88%)

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

Tool handlers catch errors

4/8 tool handlers wrap calls in try/catch (50%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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 4 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/bitflight-devops/mcp-json-yaml-toml?variant=verified)](https://m8ven.ai/mcp/bitflight-devops/mcp-json-yaml-toml)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 379dca969f3e11f8b07562fc5b93d86a775c486b
code hash: 6fae31c953aa76208c68319a0fa4ac885df051ea44b970daf78d37705f03c56f
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