> ## Documentation Index
> Fetch the complete documentation index at: https://docs.grantex.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Certification Applications

> Register an MCP server and submit a Bronze, Silver, or Gold certification application.

## Current Status

Grantex provides an MCP server directory and a certification **application intake** workflow. A server owner can register a server, request a Bronze, Silver, or Gold level, and inspect the resulting application status.

<Warning>
  Submitting an application does not certify a server. The current public contract creates an application with status `pending_conformance_test`; it does not promise an automated decision, a review deadline, a public badge URL, or an external compliance attestation. Do not display a Grantex certification badge unless the server record has been approved and Grantex provides a verifiable public record.
</Warning>

## Register a Server

Use the developer portal:

1. Open [MCP Servers](https://grantex.dev/dashboard/mcp).
2. Select **Register MCP Server**.
3. Enter the server metadata and save it.
4. Open the server detail page.

The same operation is available through `POST /v1/mcp/servers`. Registration requires a developer API key.

## Submit an Application

On an MCP server detail page, choose Bronze, Silver, or Gold. The portal calls:

```http theme={null}
POST /v1/mcp/certification/apply
Authorization: Bearer gx_live_...
Content-Type: application/json

{
  "serverId": "mcp_01HXYZ...",
  "requestedLevel": "bronze"
}
```

Accepted levels are `bronze`, `silver`, and `gold`. A successful submission returns HTTP `202`:

```json theme={null}
{
  "certificationId": "cert_01HXYZ...",
  "serverId": "mcp_01HXYZ...",
  "requestedLevel": "bronze",
  "status": "pending_conformance_test",
  "conformancePassed": 0,
  "conformanceTotal": 13,
  "createdAt": "2026-07-10T12:00:00.000Z"
}
```

The server must belong to the authenticated developer. Submitting a duplicate active application may return a conflict response.

## Check Application Status

```http theme={null}
GET /v1/mcp/certification/cert_01HXYZ...
Authorization: Bearer gx_live_...
```

The response includes the requested level, current status, conformance counts and results when available, and reviewer fields when a review has occurred. Treat the returned status as the source of truth.

## Conformance Suite

`@grantex/conformance` validates a Grantex-compatible authorization service. It does not currently accept `--issuer`, `--tier`, or `--output` flags and does not by itself submit an MCP certification application.

```bash theme={null}
npx @grantex/conformance \
  --base-url https://api.grantex.dev \
  --api-key "$GRANTEX_API_KEY" \
  --format json
```

Available options include `--suite`, `--include`, `--format text|json`, and `--bail`. Redirect standard output if you need to retain the JSON report:

```bash theme={null}
npx @grantex/conformance \
  --base-url https://api.grantex.dev \
  --api-key "$GRANTEX_API_KEY" \
  --format json > conformance-results.json
```

<Note>
  The general Grantex conformance report and MCP certification application are separate contracts today. The application endpoint does not accept an uploaded report.
</Note>

## Badges and Public Claims

There is currently no documented public badge asset, Shields.io endpoint, or `/mcp-registry/:slug` verification page. Until a stable verification URL is published:

* do not link to guessed badge or registry paths;
* do not claim that a pending application is certified;
* do not claim SOC 2, GDPR, OAuth, or production-readiness certification from a Grantex application;
* link to an official server record only when the API or portal exposes one as approved.

## Related

* [MCP Auth Server](/features/mcp-auth-server)
* [Conformance Suite](/integrations/conformance)
* [MCP Server (17 tools)](/integrations/mcp)
* [Security Best Practices](/guides/security-best-practices)