Tuurio ID

io.github.TuurioPublished by GitHub account Tuuriov1.0.0Updated Oct 24, 2026

Manage users, OIDC clients, roles, settings, and audits with tenant-bound OAuth.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant manage users, OIDC clients, roles, settings, and audit records in a Tuurio ID tenant over OAuth.

What you can do
Tuurio ID is a remote MCP server for identity administration in a Tuurio tenant. According to its registry description, it covers managing users, OIDC clients, roles, settings, and audits, with access bound to a tenant through OAuth. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to help administer identity in a Tuurio ID tenant, for example handling users, OIDC client registrations, role assignments, tenant settings, or audit review. It is not useful outside a Tuurio ID environment.
Requirements
A remote streamable HTTP endpoint at so a specific tenant subdomain is needed. Authentication is described as tenant-bound OAuth; the manifest declares no API keys, environment variables, or headers. Network access to the endpoint is required.
Before you install
The server can change identity data: users, OIDC clients, roles, and settings are administrative objects, and audit records may be sensitive. Access is tenant-bound via OAuth, so review which tenant and scopes the assistant is granted before connecting. No credentials are declared in the manifest, but OAuth authorization still grants real administrative power.

Installation

In SourceWeft

  1. Open Tuurio ID in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.