Archived listing / no verified MCP endpoint/Design

Orisu listing

No MCP endpoint is published. This listing is retained for reference.

Archived listing: Orisu was listed as a remote MCP server for a node-based workflow builder for AI images, video and voice. An assistant could build workflows from a plain description, run them with image, video and voice models, wait for results, apply a brand kit and share or publish an app. The provider documentation did not complete a TLS handshake when checked on 16 November 2026, so the endpoint, tools and auth flow remain unverified. This page is retained as a reference only.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.
No MCP endpoint Reviewed 2026-11-16
About

Where it fits

People who followed the listing and need to know the provider could not be verified.

  • Check the provider's current documentation before using Orisu.
  • Treat the listed workflow-building capabilities as unverified.
  • Do not install from this page until a first-party endpoint is confirmed.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.