Verified Human Cert MCP Server: Prove Your Music Is Human-Made, Right from the Terminal

The line between human-made and machine-generated music is getting blurry. Verified Human Cert (VHC) is one answer to that problem: a public registry where artists and labels certify that their tracks were created by humans.

I wanted to query that registry without leaving my terminal. So I built an MCP server for it and open-sourced it: mcp-verifiedhumancert.

What the server does

The server exposes six tools that map directly to the VHC public API:

No API key needed. The VHC registry is public, and all these endpoints are read-only.

Once connected, you just talk to Claude:

• "Is ISRC USHM82148308 certified as human-made?"
• "Check if 'Yesterday' by The Beatles has a VHC certification"
• "Show me the latest certified tracks"

The multi-agent workflow

This is where it gets interesting. I already had mcp-metadata, my open-source MCP server for reading and writing audio file metadata (ID3 tags, ISRC codes, Vorbis comments). Combining the two servers creates a multi-agent pipeline:

1. Agent 1 (mcp-metadata) reads the ISRC code from an audio file
2. Agent 2 (mcp-verifiedhumancert) verifies that ISRC against the VHC registry
3. Claude orchestrates both agents and presents the result

User: "Read the ISRC from song.flac and check if it's certified"

Agent 1 (mcp-metadata): metadata_read("song.flac") -> ISRC: USHM82148308
Agent 2 (mcp-verifiedhumancert): vhc_verify_isrc("USHM82148308") -> certified: true

Two MCP servers, two specialized agents, one orchestrator. No glue code, no custom integrations. Claude handles the coordination.

Why this matters for the music industry

The rise of generative audio tools has created a trust problem. Listeners, labels, and platforms need a way to distinguish human-created work from machine-generated output. VHC provides that layer of trust, and my MCP server makes it accessible to developers and tooling without building custom API integrations.

Setting it up

1. Clone and install

git clone https://github.com/musictechlab/mcp-verifiedhumancert.git
cd mcp-verifiedhumancert
poetry install

2. Register with Claude Code

Add this to your ~/.claude/settings.json or project .claude/settings.local.json:

{
  "mcpServers": {
    "vhc": {
      "command": "poetry",
      "args": ["--directory", "/path/to/mcp-verifiedhumancert", "run", "python", "-m", "mcp_verifiedhumancert"]
    }
  }
}

3. Start using it

That's it. Ask Claude anything about the VHC registry:

• "Look up cert number VH-2026-000001"
• "What are the current VHC pricing tiers?"
• "How many tracks are certified on the platform?"

Under the hood

The server is built with FastMCP, the Python SDK for the Model Context Protocol. The architecture is straightforward:

• client.py - a thin HTTP wrapper around the VHC REST API using httpx
• server.py - six tool definitions that call the client and return JSON
• Tests - full test coverage using respx for HTTP mocking

@mcp.tool()
def vhc_verify_isrc(isrc: str) -> str:
    """Verify a human-made music certification by ISRC code."""
    result = client.verify_by_isrc(isrc)
    return json.dumps(result, indent=2, ensure_ascii=False)

def verify_by_isrc(isrc: str) -> dict:
    """Verify a certification by ISRC code."""
    return _get("/api/v1/verify", params={"isrc": isrc})

The entire server is under 200 lines of Python. That's intentional. MCP servers should be thin wrappers, not application frameworks.

What I learned building MCP servers

This is the third MCP server I have open-sourced (after signnow-mcp and mcp-metadata). A few patterns have emerged:

1. Keep servers focused. One server per domain. Don't bundle unrelated tools into a single server.
2. Separate the client from the server. The HTTP client should be testable independently of the MCP layer.
3. Return JSON, not prose. Let Claude format the output for the user. The server's job is to provide structured data.
4. Skip authentication when you can. Public APIs make MCP servers trivial to set up. No .env files, no OAuth flows, no token management.

Open source

The full source code is on GitHub: musictechlab/mcp-verifiedhumancert. MIT licensed. Contributions welcome.

If you're building MCP servers for the music industry, or if you're using Verified Human Cert and want to integrate it into your tooling, I'd love to hear from you.

Related resources

• GitHub: musictechlab/mcp-verifiedhumancert - the source code
• GitHub: musictechlab/mcp-metadata - audio metadata MCP server
• SignNow MCP Server: E-Signatures from Claude Code - my previous MCP server article
• Verified Human Cert - the certification platform
• Model Context Protocol - the MCP standard

FAQ

What is Verified Human Cert?

Verified Human Cert is a registry that certifies music tracks as human-made. Artists and labels register their tracks to receive proof that the music was created by humans, not generated by artificial intelligence.

What is the mcp-verifiedhumancert server?

It is an open-source Model Context Protocol server that connects the Verified Human Cert public API to Claude Code and other MCP-compatible clients. It lets you verify certifications, browse the registry, and check pricing directly from your terminal.

Do I need an API key to use this?

No. The server queries the public VHC API, which does not require authentication for read-only operations like verifying certifications and browsing the registry.

What is the multi-agent workflow?

By combining mcp-verifiedhumancert with mcp-metadata, Claude can read the ISRC code embedded in an audio file and then verify its certification status in a single conversation. Two MCP servers, two agents, one orchestrator.

Can I use this with clients other than Claude Code?

Yes. Any MCP-compatible client can use this server. The MCP protocol is open and supported by a growing number of tools.

Cover: Photo by Erika Giraud on Unsplash