UIID v2.17 "Smart Routing": Sign In and Go Straight Back, and a New Home for the MCP Ecosystem

LINKSPREED LLC releases UIID v2.17, a major step toward seamless sign-in and an open, secure foundation for MCP (Model Context Protocol) servers, clients and AI agents.

LINKSPREED uiidmcprelease

The release adds Smart Routing, a new MCP Marketplace, a 27-tool Solutions MCP server, enforced OAuth PKCE (S256), Dynamic Client Registration and cleaner MCP error handling.

LINKSPREED LLC today announces the availability of UIID v2.17, released under the name Smart Routing. This version improves two experiences at once. For people, it removes the detour that often follows sign-in or account creation, so you return straight to the application you started from. For developers, agent builders and the wider MCP community, it adds a marketplace, a larger set of public tools, stricter security defaults, self-service client registration and more predictable error behavior.

The common idea behind these changes is that identity should get out of the way. Signing in should be quick and safe, and it should end where you wanted to be. When the one connecting is an AI agent or an MCP client instead of a person, the process should be just as clear, secure and well-defined.

UIID v2.17 is available now at http://uiid.me/. The complete list of changes is published in the changelog at http://uiid.me/changelog.

Why This Release Matters

Two trends shape how people use the internet today, and v2.17 responds to both.

First, sign-in is one of the most repeated actions online. People sign in to dozens of services, and they often do it in the middle of another task. A small friction point, such as landing on the wrong page, forgetting where you were or having to copy a link by hand, is repeated millions of times a day across the internet. Removing that friction is one of the most direct ways to improve how identity feels.

Second, software is increasingly acting on our behalf. AI assistants and agents now connect to tools, data sources and services through open protocols such as MCP. Each of these connections raises the same questions that identity has always asked. Who is connecting? What are they allowed to do? Can the person who owns the data stay in control? And as the number of MCP servers grows, how do you find ones worth trusting and connect to them without a long setup process?

UIID v2.17 addresses the human side with Smart Routing, and it addresses the agent side with the MCP Marketplace, public tools and discovery, enforced PKCE, Dynamic Client Registration and improved error handling. Together they make UIID a more complete identity layer for people and for the software that works for them.

A Quick Reminder: What Is UIID?

UIID is LINKSPREED’s identity layer. It is built around the idea that people should have an identity they own and control, and that signing in to applications and services should not mean handing personal data to every platform along the way. For developers and organizations, UIID offers a way to provide modern, privacy-respecting sign-in and identity features without building everything from scratch.

UIID is part of the wider LINKSPREED ecosystem, which includes ATRIUM and other products. Identity is the thread that connects them. Whether someone is signing in to an application, connecting a tool or authorizing an AI agent, UIID is meant to be the trusted starting point.

Version 2.17 continues this direction in two ways:

  • For people, it makes the everyday experience smoother with Smart Routing.
  • For tools and agents, it prepares UIID for a world where more and more software connects through MCP, with clear rules, good security defaults and a central place to discover and connect.

Smart Routing: The Detour Is Gone

The problem

Many people know this experience. You are in the middle of something in one application. You decide to sign in, or you need to create an account first. You do that through an identity provider, and once you are done, you land somewhere unexpected. It might be a dashboard, a start page or a settings screen. The application you started in is no longer in front of you. To get back, you have to remember where you were, find it again or copy the link from somewhere and paste it in yourself.

This is a small annoyance each time. Across many sign-ins and many users, it is a real source of drop-off and frustration. It is also hardest on new users, who may not know what to do next after creating an account.

The solution

With UIID v2.17, when you sign in or create an account after starting from another application, you now return straight to that application once you are done. There is no detour to your dashboard, and no need to copy the link back yourself.

That is what Smart Routing means. UIID keeps track of where you came from and brings you back there when the sign-in or account creation is complete.

What it looks like in everyday use

Here are a few situations where the difference shows:

  • Signing in to an application you already use. You open the application, choose to sign in with UIID and complete the sign-in. You land back in the application, ready to continue.
  • Creating a new account along the way. You arrive at an application for the first time and don’t have a UIID account yet. You create one, and when you are done you return to the application that sent you, instead of being left on an unfamiliar page.
  • Following a link someone shared. You click a link that requires you to be signed in. After signing in, you continue to what the link was about, not to a generic start page.

Who benefits

  • Everyday users get a shorter, calmer sign-in flow. They don’t need to remember where they were or copy and paste links.
  • New users get a clearer first experience. After creating an account, the next step is obvious because they are back where they wanted to be.
  • Applications that use UIID for sign-in can count on their users returning to them without extra manual steps. Fewer people get lost between sign-in and the application, which supports a better first impression.

Smart Routing is easy to describe, but it touches one of the most frequent interactions on the internet. Small improvements in a frequent interaction add up to a noticeably better experience.

A Short Introduction to MCP

Much of v2.17 focuses on MCP, so a short introduction may be useful.

MCP (Model Context Protocol) is an open protocol that lets AI assistants and agents connect to external tools, data and services in a standardized way. Instead of every assistant needing a custom integration for every service, MCP defines a common way for an MCP client (the AI application or agent) to talk to an MCP server (the service that offers tools and data).

In simple terms:

  • An MCP server exposes tools. A tool is a defined action the server can perform, such as looking up information or carrying out a task.
  • An MCP client connects to the server, discovers which tools are available and calls them when needed.
  • The two sides communicate through a defined protocol, so any compliant client can work with any compliant server.

This has made it much easier to give AI assistants useful capabilities. It has also made identity and access control more important. When an agent connects to a server, the connection has to be authenticated, authorized and understandable. That is where UIID comes in, and it is why this release invests heavily in the MCP experience.

The New MCP Marketplace

A central place to discover and connect

As MCP grows, so does the number of servers. Finding the right server, knowing what it offers and getting connected can take time. Settings have to be pieced together from documentation, and it is not always clear where to look in the first place.

UIID v2.17 introduces the MCP Marketplace.

You can find it in the sidebar under UIID Store. It lists:

  • The UIID MCP endpoint, so you can connect to UIID’s own MCP capabilities.
  • Community MCP servers, built and shared by others.

Open to the community: submit your own server

The marketplace is designed to be a shared space, not just a catalog. If you have built an MCP server, you can submit it for review. Once a server has been approved, it becomes available in the marketplace for others to find and use.

Developers get a place to share their work with people who are looking for it. The people browsing get servers that have gone through a review step instead of an unfiltered list.

Ready-to-use configuration snippets

Connecting to an MCP server usually means adding the right configuration to your MCP client. For approved servers, the marketplace provides ready-to-use configuration snippets. Instead of searching through documentation and assembling settings by hand, you can take the snippet and connect.

This has practical benefits:

  • Beginners can get started without learning every configuration detail first.
  • Experienced developers save time on routine setup and avoid small configuration mistakes.
  • Server authors make their servers easier to adopt, because a smoother first connection means more people actually try them.

Why it lives inside UIID

The marketplace sits within the UIID Store, which ties it directly to the identity layer many of these connections rely on. Discovery, sign-in and authorization are close to each other. That makes it easier to move from “I found a server” to “I am connected and in control of what it can access.”

MCP Public Tools and Discovery

27 tools on the Solutions MCP server

The Solutions MCP server has grown. It now exposes 27 tools, including public tools. The MCP server page lists the full inventory, so you can see everything that is available.

Why a visible inventory matters

For anyone connecting an agent or building an integration, knowing what a server offers is the first step. A complete, visible inventory brings several benefits:

  • Transparency. You can see what a server can do before you connect. Trust starts with knowing what you are connecting to.
  • Planning. Developers and agent builders can look at the full list of tools and design workflows around them, instead of discovering capabilities one at a time.
  • Easier first steps. Public tools lower the barrier to trying things out. You can explore the available capabilities and build on them without having to work out everything in advance.

For the MCP ecosystem, clear discovery is as important as the tools themselves. A tool that cannot be found or understood is hard to use. By listing the whole inventory on a dedicated page, UIID makes the Solutions MCP server easier to evaluate and easier to adopt.

Stronger Security: OAuth With PKCE (S256) Enforced

What changed

Authorization and token requests now enforce PKCE with the S256 method.

This is one of the most important security improvements in v2.17. It is a technical change, but the idea behind it is simple.

What is PKCE?

PKCE (Proof Key for Code Exchange) is an extension to OAuth, the widely used standard for authorizing applications. It protects against a specific kind of attack called authorization code interception.

Here is how that attack works in principle. In a typical OAuth flow, an application sends the user to sign in. When the user has finished, the identity provider sends back a short-lived authorization code. The application then exchanges this code for a token. If an attacker manages to capture the code while it travels back to the application, they could try to exchange it for a token themselves.

PKCE closes this gap:

  1. Before starting the flow, the client creates a secret value called the code verifier.
  2. From it, the client derives a code challenge and sends the challenge with the authorization request.
  3. When the client later exchanges the code for a token, it must present the original code verifier.
  4. The server checks that the verifier matches the challenge from the beginning.

A stolen authorization code on its own is no longer enough. The attacker would also need the code verifier, which never travels with the code.

Why S256?

PKCE supports different methods for creating the challenge. With S256, the challenge is created by applying a SHA-256 hash to the verifier, so the verifier itself is not sent in the first request. This is the stronger and recommended method. The simpler alternative sends the verifier unchanged, which gives weaker protection if the first request is observed.

By enforcing S256, UIID makes sure that clients connecting to it follow the stronger approach by default.

Who is protected?

PKCE is especially valuable for public clients. These are applications that cannot keep a secret safely, such as:

  • Mobile apps
  • Single-page web applications
  • Desktop tools
  • Many MCP clients

Because these clients cannot store a client secret securely, they rely on PKCE to protect the authorization flow. With enforcement in place, every such client connecting to UIID benefits from the same protection, whether or not its developer thought to enable it.

Dynamic Client Registration for MCP Clients

The problem it solves

In the traditional OAuth model, a developer registers an application with an identity provider ahead of time and receives credentials for it. That works well when there are a few known applications. MCP changes the picture. An MCP client, such as an AI assistant, may need to connect to many servers, including ones it has never seen before. Asking a person to register the client manually with each server does not scale and creates friction right when people want to try something new.

What v2.17 adds

UIID v2.17 supports Dynamic Client Registration. MCP clients can now register themselves at /oauth/register.

This lets a client introduce itself to UIID programmatically, so the registration step happens as part of the connection instead of as a separate manual task.

Hero Image

Clear rules for redirect URIs

Self-registration is only helpful if it is safe. UIID therefore sets clear rules for redirect URIs, which are the addresses where the user is sent back after authorizing:

  • Redirect URIs must use HTTPS.
  • HTTP is allowed only on localhost.

These rules are practical:

  • HTTPS protects the redirect in transit, which matters because the redirect carries the authorization response.
  • HTTP on localhost supports the way developers actually work. Local development servers and desktop tools often run on the developer’s own machine, where HTTPS is impractical and the traffic does not leave the device.
  • Anything else is not accepted, which reduces the risk of redirect abuse.

Better together with PKCE

Dynamic Client Registration and PKCE enforcement complement each other. Self-registration makes it easy for new clients to connect. PKCE makes sure those clients, many of which are public clients, connect securely. Together they let UIID welcome new MCP clients without lowering its security standards.

Better MCP Error Handling

Tool errors versus protocol errors

Anyone who has built an agent or an integration knows how much it matters how errors are reported. There is a meaningful difference between two kinds of failure:

  • A protocol-level failure, which signals that something went wrong with the communication itself.
  • A tool-level error, which says the communication worked, the tool was called and the tool reported a problem.

If a failed tool call is reported as a protocol-level failure, a client may treat it as a broken connection. It might retry in the wrong way, stop entirely or show the user a confusing message.

What changed

In v2.17, failed tool calls now return a proper tool error result (isError) instead of a protocol-level failure.

What this means in practice

  • Agents can handle failures gracefully. A tool error is a normal part of operation. An agent can read the error, understand what happened and decide what to do next, such as trying a different approach or telling the user what went wrong.
  • Fewer misleading failures. The connection is no longer implicated when only a single tool call did not succeed.
  • Better developer experience. Developers get clearer, more predictable behavior, which makes integrations easier to build and debug.

Policy denials stay distinct

One detail is important. Policy denials still return their own error code. When a request is denied because of a policy decision, as opposed to a tool failing, UIID reports it separately. Clients can tell the difference between “this tool failed” and “this action was not allowed.” That distinction is important for identity, where access decisions need to stay visible and unambiguous.

How It All Fits Together

The individual features in v2.17 are useful on their own, but they were designed to work together. Here is a typical journey that touches several of them.

  1. Discover. A developer opens the MCP Marketplace under UIID Store and browses the UIID MCP endpoint and approved community servers.
  2. Inspect. They visit the MCP server page and review the full inventory of 27 tools on the Solutions MCP server, including its public tools.
  3. Connect. They copy a ready-to-use configuration snippet into their MCP client.
  4. Register. If the client has not connected before, it can register itself at /oauth/register, using an HTTPS redirect URI, or HTTP on localhost during development.
  5. Authorize securely. The client starts the OAuth flow with PKCE (S256), which UIID now enforces.
  6. Sign in and return. The person signs in or creates an account, and Smart Routing returns them straight to the application they started from.
  7. Use the tools. The agent calls tools. If one fails, it receives a clear isError tool result. If a request is blocked by policy, it receives the distinct policy error code.

From discovery to day-to-day use, each step is clearer and safer than before.

Hero Image

Summary of Changes

AreaWhat changedWho benefits
Smart RoutingAfter signing in or creating an account from another application, you return straight to that application. No dashboard detour, no copying the link back.Everyday users, new users and partner applications
MCP MarketplaceNew sidebar entry under UIID Store listing the UIID MCP endpoint and community MCP servers. Submit your server for review and connect to approved servers with ready-to-use configuration snippets.Developers, agent builders and the community
MCP Public Tools & DiscoveryThe Solutions MCP server exposes 27 tools, including public tools. The MCP server page lists the full inventory.Integrators and agent developers
OAuth PKCE (S256)Authorization and token requests enforce PKCE with S256, protecting public clients against authorization code interception.Public clients and security-minded teams
Dynamic Client RegistrationMCP clients can register at /oauth/register. Redirect URIs must use HTTPS, or HTTP on localhost.MCP client developers
MCP Error HandlingFailed tool calls return a proper tool error result (isError) instead of a protocol-level failure. Policy denials keep their own error code.Agents and integrations

What This Means for Different Audiences

For everyday users

You get a smoother sign-in experience. You come back to where you started, and you do not need to find your way again. If you want to explore MCP, the marketplace gives you a place to start.

For developers building applications with UIID

Your users return to your application after signing in or creating an account. That makes the first experience cleaner and reduces the chance of people getting lost along the way.

For MCP server authors

The MCP Marketplace gives you a place to submit your server for review and share it with others. Ready-to-use configuration snippets make it easier for people to connect once it is approved.

For MCP client and agent developers

You get self-registration through /oauth/register, clear redirect rules, enforced PKCE and predictable error handling. A visible tool inventory also helps you plan what your agent can do.

For security-minded teams

Enforced PKCE with S256 raises the baseline for every public client. Strict redirect URI rules limit the risk of abuse. Distinct error codes for policy denials keep access decisions clear.

Frequently Asked Questions

What is the main theme of UIID v2.17?

Smart Routing and MCP. The release makes sign-in smoother for people and makes UIID more open, secure and predictable for MCP servers, clients and agents.

What does Smart Routing do?

When you sign in or create an account after starting from another application, you return straight to that application once you are done. You are not sent to your dashboard first, and you do not need to copy the link back yourself.

Where can I find the MCP Marketplace?

In the sidebar under UIID Store.

What does the MCP Marketplace list?

The UIID MCP endpoint and community MCP servers.

Can I add my own MCP server?

Yes. You can submit your server for review. Approved servers become available in the marketplace, with ready-to-use configuration snippets for connecting.

How many tools does the Solutions MCP server offer?

It now exposes 27 tools, including public tools. The MCP server page lists the full inventory.

What does PKCE with S256 do?

It protects public clients against authorization code interception. A stolen authorization code is not enough to get a token, because the exchange also requires the code verifier that matches the original challenge.

Where do MCP clients register?

At /oauth/register. Redirect URIs must use HTTPS, or HTTP on localhost.

What changed in MCP error handling?

Failed tool calls now return a proper tool error result (isError) instead of a protocol-level failure. Policy denials still return their own error code.

Where can I see every change in this release?

In the changelog at http://uiid.me/changelog.

Looking Ahead

UIID v2.17 reflects a consistent direction. Identity should be owned and controlled by the person it belongs to, and it should work smoothly in the places where people and their software need it. Smart Routing makes the human experience feel more natural. The MCP Marketplace, public tools, PKCE enforcement, Dynamic Client Registration and improved error handling make UIID a clearer and safer foundation for the agent era.

LINKSPREED will continue to develop UIID with these principles in mind. The changelog is the best place to follow what ships and when.

Get Started With UIID v2.17

  1. Visit http://uiid.me/ to sign in or create an account and experience Smart Routing.
  2. Open the MCP Marketplace in the sidebar under UIID Store and browse the UIID MCP endpoint and community servers.
  3. Review the MCP server page to see the full inventory of the Solutions MCP server.
  4. Submit your own MCP server for review if you have built one you want to share.
  5. Connect your MCP client with a ready-to-use configuration snippet, registering at /oauth/register if needed.
  6. Read the full changelog at http://uiid.me/changelog for every detail of this release.

About UIID

UIID is LINKSPREED’s identity layer, built around the principle that people should own and control their digital identity. It provides sign-in, identity features and a growing set of integrations for people, applications and AI agents. Learn more at http://uiid.me/.

About LINKSPREED LLC

LINKSPREED LLC builds products that put privacy, ownership and identity control at the center of the internet experience, including UIID and the ATRIUM ecosystem.