"Origin" matching MCP servers:

Enables formatting whole OriginLab Origin projects into a fixed thesis or journal house style from inside DeepSeek Harness. It applies per-layer grid layouts, unified fonts, render-measured axis-title placement, overlap resolution, panel labels, and 600-dpi export with corrected dpi metadata, while leaving original files untouched.

Enables searching, browsing, and installing OriginUI components through the Model Context Protocol. It provides detailed component information, visual previews, and installation commands compatible with the shadcn CLI.

Enables clients to interact with a spec-shaped Model Context Protocol endpoint over Streamable HTTP, supporting initialization, session handling, tool listing and calls, plus ping, with origin validation and protocol version enforcement.

Monitors origin/main for new commits, analyzes conflict risk with local AI (Ollama), and syncs your working branch via rebase or merge with automatic stash/unstash and conflict resolution options.

Enables publishing, updating, and sharing HTML artifacts with strict security isolation (origin separation, CSP, API keys) via MCP tools.

Just to be clear about the final JSON: the MCP server is named herdr-inbox, and it enables Claude Code agents in herdr to ask questions asynchronously without stalling, with all open questions answered from one popup and answers routed back to the asking agent.

Enables multiple AI agents to each run Google's full Chrome DevTools toolset in an isolated Chrome instance with saved logins, origin allowlists, reconnect recovery, and process cleanup. It also provides visibility into running browsers so stale sessions can be inspected or reaped.

Enables asking a consuming app in plain language to audit its design system usage, returning tables that sort every value and component by origin—design system, app-named, or none—along with token and contrast checks.

Enables an MCP server to gate tools/call requests by requiring a per-send channel-policy attestation for outbound actions, checking ROPE-lite origin tags on sensitive arguments, and returning SEP-2643-shaped structured denials with retry handles and remediation hints when a call is blocked. It logs client-asserted audit context (such as turnId and userIntent) for correlation across allowed and denied calls, but never uses that receipt for allow/deny decisions.

Enables running a stateless Model Context Protocol server over Streamable HTTP on Cloudflare Workers or any fetch-capable runtime, with signed sessions, origin checks, and JSON-RPC request handling. It lets developers define tools with JSON Schema validation and per-request context.