Inbio

io.github.www-in-bioPublished by GitHub account www-in-biov1.0.0Updated Oct 24, 2026

Official in.bio MCP server: shorten URLs, styled QR codes, and click analytics. No API key needed.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

An official in.bio remote MCP server that lets an assistant shorten URLs, generate styled QR codes, and read click analytics.

What you can do
The server exposes in.bio's link tools to an assistant: creating shortened URLs, producing styled QR codes, and retrieving click analytics for links. It is hosted remotely at a fixed endpoint, so the assistant connects to it rather than running anything locally. The registry description states no API key is needed.
When to use it
Useful when an assistant needs to create or manage short links, generate QR codes for a URL, or pull click statistics as part of a workflow. It is a fit for marketing, content, or reporting tasks that involve sharing and tracking links.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the provider's hosted endpoint. No packages, environment variables, or headers are declared, and the description says no API key is needed.
Before you install
The server is remote, so any URLs, link data, or analytics queries the assistant sends go to the provider. Shortening a link makes it public through the provider's service, and analytics data returned may be shared with the assistant session. No credentials are declared, but confirm the provider's data handling before sending sensitive URLs.

Installation

In SourceWeft

  1. Open Inbio 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.

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/io.github.www-in-bio%2Finbio/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.

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

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.