CodeB

io.codebPublished by codeb.ioOfficial publisherv1.1.0Updated Oct 24, 2026

Signing requests, 18+ age checks with EUDI wallets, meetings, cards. People sign in CodeB Wallet.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

CodeB is a remote MCP endpoint for signing requests, 18+ age checks with EUDI wallets, meetings and cards, with users signing in through CodeB Wallet.

What you can do
Sign requests through the CodeB service, with users signing in via CodeB Wallet. Perform 18+ age checks using EUDI wallets. Handle meetings and cards. No individual tools are listed, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to route signing requests, age verification or wallet-based sign-in through CodeB, for example for EUDI wallet age checks or card and meeting workflows.
Requirements
A remote streamable HTTP endpoint at phone.codeb.io. OAuth authentication is required, so the user needs a CodeB Wallet account to sign in. No environment variables or headers are declared.
Before you install
Signing and age-check flows involve identity and wallet credentials handled by CodeB; users sign in through CodeB Wallet, so account and identity data go to that third party. Signing requests may carry legal or financial weight. No tool list is published, so review what each action does before relying on it.

Installation

In SourceWeft

  1. Open CodeB 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/io.codeb%2Fsigning/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": {
    "codeb": {
      "type": "http",
      "url": "https://phone.codeb.io/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

2
  1. v1.1.0LatestOct 24, 2026
  2. v1.0.1Oct 23, 2026

Score

72% 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

    Publish an icon in the registry entry.

  • Documentation15 pts
  • 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.