Auth

click.myinfrastructurePublished by myinfrastructure.clickOfficial publisherv1.0.3Updated Nov 4, 2026

Usuários, sessões, logins sociais e webhooks da sua aplicação

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Server details

Identifier: click.myinfrastructure/auth
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 21, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to myinfrastructure.click, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/click.myinfrastructure%2Fauth.svg)](https://sourceweft.com/mcp/click.myinfrastructure%2Fauth?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP endpoint for an application's users, sessions, social logins and webhooks, reached over OAuth-authenticated HTTP.

What you can do: The listing gives no tool list, so capabilities are inferred from the description only.
Manage application users and their accounts.
Handle sessions and social logins.
Work with webhooks belonging to the application.
When to use it: Worth considering when an assistant should work with the user, session, social-login and webhook data of an application built on this provider's auth service, rather than querying it by hand.
Requirements: A remote streamable HTTP endpoint at the provider's auth host; OAuth authentication is required. No environment variables or headers are declared. Network access to the provider's service is needed.

Before you install

The server handles identity data: users, sessions and social logins, which are sensitive. OAuth grants access to that account, so review the scopes requested. No tool list is published, so what it can read or change, including webhook configuration, is unverified before connecting.

Installation

In SourceWeft

Open Auth in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.3LatestNov 4, 2026
v1.0.1Oct 21, 2026

Score

67% 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
Auth declaredRequired10 pts
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.