C
Emerging
74/100
6 hours ago

OBS MCP

Enables AI assistants to control and automate OBS Studio via natural language, covering scenes, sources, audio, recording, streaming, transitions, filters, media playback, diagnostics, and multi-step workflows over the OBS WebSocket protocol.

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 VerifiedSandbox 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

KshamayBharadwaj · Claimed

Source: Glama

Maintenance & responsiveness
as of 2026-08-19
Issues closed (90d): 0 · 0 open
Releases (90d): none
Active contributors (6mo): 1
⚡ Upgrade to Live Monitored

Connect your repo and M8ven re-verifies it on the push itself. Without it we re-check verified listings about once a day, so a fix can sit unseen. Read-only, one click, 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.
🔐
You'll be asked for 1 credential: OBS_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
Are you the publisher? Confirm or correct these findings.
// 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.
configOBS_PORT4455 OBS WebSocket port (must match Tools → WebSocket Server Settings)
configOBS_CONNECT_TIMEOUT5 Seconds to wait for a connection attempt
configOBS_HOSTlocalhost OBS WebSocket host
🔐 secretOBS_PASSWORDedit .env, set to the password you configured in OBS
configOBS_RECORDING_SCENE(empty) Scene used by prepare_recording / start_recording_session (empty = current scene)
configOBS_STREAM_SCENE(empty) Scene used by prepare_stream (empty = current scene)
configOBS_LOG_LEVELINFO Logging verbosity: DEBUG, INFO, WARNING, ERROR
// 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

89/89 tools missing one or more hints — get_obs_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_obs_stats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); obs_help (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +86 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.

License file

No license file

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

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 3 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/kshamaybharadwaj-obs-mcp-1qtv0h)](https://m8ven.ai/mcp/kshamaybharadwaj-obs-mcp-1qtv0h)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 0b406c0120134b817d4965dcae4b5cbd127683a5
code hash: 4f4824f7a47f5a894a163d5dfdeaa9026b107614570f58cb65f16d9967fae7e0
verified: 8/19/2026, 11:21:55 AM
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