Certifier MCP

io.certifierPublished by certifier.ioOfficial publisherv0.1.0Updated Oct 24, 2026

Official MCP server for Certifier to issue, manage, and track certificates and badges.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Certifier MCP is a remote server that lets an assistant issue, manage and track certificates and badges through Certifier.

What you can do
Issue certificates and badges to recipients through Certifier. Manage existing certificates and badges. Track certificate and badge status. No tool list is published, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to handle digital credentialing work in Certifier, such as issuing or tracking certificates and badges, without switching to the Certifier interface.
Requirements
A remote endpoint at api.certifier.io reached over streamable HTTP. OAuth authentication is required, so a Certifier account with the appropriate access is needed. No environment variables or headers are declared.
Before you install
Issuing certificates and badges creates records that may be visible to recipients, so confirm recipients and content before letting an assistant act. Access is granted through OAuth to your Certifier account; review the scopes requested. No tool list is published, so verify what write actions are available before use.

Installation

In SourceWeft

  1. Open Certifier MCP 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.certifier%2Fmcp/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": {
    "certifier": {
      "type": "http",
      "url": "https://api.certifier.io/v1/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. v0.1.0LatestSep 16, 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.

Other Certifier integrations