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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
7 days ago

stateset-agents

StateSet RL Agents Framework

→ stateset/stateset-agents· listed on github_code

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

stateset

Source: github_code

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

GitHub

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.
✅
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 4 credentials: RUNPOD_API_KEY, STATESET_PYPI_TOKEN, API_JWT_SECRET, REDIS_PASSWORD
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.
configSTATESET_AGENTS_STRICT_STARTUP
configSTATESET_DEFAULT_CHECKPOINT
configSTATESET_DEFAULT_BASE_MODEL
configRANK
configLOCAL_RANK
configWORLD_SIZE
🔐 secretRUNPOD_API_KEYMonday, armed the moment the secret exists.
configRUNPOD_ENDPOINT_ID
configRUNPOD_POD_TYPE
configRUNPOD_DISK_SIZE
configRUNPOD_VOLUME_SIZE
configRUNPOD_MIN_PODS
configRUNPOD_MAX_PODS
configSKIP_RELEASE_BRANCH_CHECK
🔐 secretSTATESET_PYPI_TOKEN
configPAGER
configXDG_STATE_HOME
configAPI_CORS_ORIGINS
configAPI_ENVIRONMENT
configAPI_RATE_LIMIT_BACKEND
configAPI_RATE_LIMIT_REDIS_URL
🔐 secretAPI_JWT_SECRET
configAPI_KEYS
configAPI_JWT_ALGORITHM
configAPI_TRACING_ENDPOINT
configAPI_LOG_LEVEL
configAPI_LOG_FORMAT
configAPI_HOST
configAPI_VERSION
configAPI_TITLE
configCACHE_BACKEND
configCACHE_SERIALIZER
configCACHE_ALLOW_PICKLE
🔐 secretREDIS_PASSWORD
configREDIS_DB
configCACHE_DEFAULT_TTL
configCACHE_MAX_MEMORY_ITEMS
configCACHE_KEY_PREFIX
configCACHE_COMPRESSION
configCACHE_REDIS_CONNECT_TIMEOUT
configDB_BACKEND
configDB_POOL_SIZE
configDB_MAX_OVERFLOW
configDB_POOL_TIMEOUT
configDB_ECHO
configDB_AUTO_MIGRATE
configSTATESET_AGENTS_ENABLE_CORE_DEPRECATION
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployREDIS_URL
deployDATABASE_URL
// 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

9/9 tools missing one or more hints — list_rewards (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ingest_transcripts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); grade_transcript (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 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.

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 2 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/stateset/stateset-agents)](https://m8ven.ai/mcp/stateset/stateset-agents)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5ea30e23c787bed3244a62a2159d3931ca9f7d67
code hash: 70038affe284111d5cb2a0a60d55f3a6dc20e7fe7bf64aa51dfd8d4aa0b8152c
verified: 9/3/2026, 6:16:06 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