Noiz

bio.noizPublished by noiz.bioOfficial publisherv1.0.0Updated Oct 24, 2026

Read and edit your noiz link-in-bio page: views and clicks, links, name, bio and location.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant read and edit a Noiz link-in-bio page, including views, clicks, links, name, bio and location.

What you can do
Noiz is a remote MCP server for managing a Noiz link-in-bio page. According to the registry description, it lets an assistant read and edit the page's views and clicks, links, name, bio and location. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to check link-in-bio performance or update the content of a Noiz page without opening the Noiz interface. It is not useful if you do not have a Noiz page.
Requirements
A remote MCP endpoint at mcp.noiz.bio over streamable HTTP, with OAuth authentication required. No environment variables, headers or packages are declared.
Before you install
The server requires OAuth authorization to your Noiz account, and it can edit page content such as links, name, bio and location, so changes may be visible publicly on your link-in-bio page. Review edits before they are applied.

Installation

In SourceWeft

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

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/bio.noiz%2Fnoiz/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "noiz": {
      "type": "http",
      "url": "https://mcp.noiz.bio/mcp"
    }
  }
}

Tools

0
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

1
  1. v1.0.0LatestOct 10, 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.