> ## 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.

# Release Status

> Choose the current Grantex TypeScript, Python, Go, or MCP package with exact versions, runtime requirements, limitations, and reproducible install commands.

## Current published releases

Last verified: **July 12, 2026**

Grantex packages are versioned independently. There is no single version number
that represents every SDK, integration, service, and protocol artifact in this
repository.

| Surface          |                               Current release | Status                           | Runtime requirement             |
| ---------------- | --------------------------------------------: | -------------------------------- | ------------------------------- |
| TypeScript SDK   |                         `@grantex/sdk@0.3.13` | Published to npm                 | Node.js 18+; ESM                |
| Python SDK       |                             `grantex==0.3.14` | Published to PyPI                | Python 3.9+                     |
| Go SDK           | `github.com/mishrasanjeev/grantex-go@v0.1.10` | Published with known limitations | Go 1.26.1+                      |
| MCP Auth server  |                     `@grantex/mcp-auth@2.0.2` | Published with known limitations | Node.js 18+; ESM                |
| OpenAPI contract |                                      `0.3.12` | Repository API-contract version  | Independent of SDK-only patches |

<Info>
  The SDK patch versions differ because each language package is released on its
  own schedule. A newer package version does not imply a newer protocol or API
  contract version.
</Info>

## Repository changes awaiting publication

<Info>
  As of July 14, 2026, repository source on `main` corrects the documented Go
  Agent/Audit read/write contracts, removes unsupported audit filters and list
  metadata, and URL-encodes query values. No corrected Go module tag is published.
  Standard developer API-key plan throughput is also source-only; custom-auth quotas and managed rollout remain separate.
</Info>

## Which Grantex package should I use?

* **TypeScript application:** use `@grantex/sdk@0.3.13`.
* **Python application:** use `grantex==0.3.14`.
* **Go application:** use `github.com/mishrasanjeev/grantex-go@v0.1.10` with the [published-version workarounds](/sdks/go/overview#known-v0110-limitations), including the [REST/CLI audit-write workaround](/sdks/go/audit#log).
* **MCP HTTP transport authorization:** use an established MCP-compatible authorization server and maintained MCP SDK that implement the current MCP authorization specification.
* **Agent-specific MCP tool enforcement:** after transport authorization, use a primary Grantex SDK or direct JWKS validation at each tool boundary. Treat `@grantex/mcp-auth@2.0.2` as single-process evaluation software.
* **Current revocation:** local JWT verification is insufficient by itself; perform an online state check or synchronize revocation data.

## Known limitations in the current published artifacts

<Warning>
  **Go SDK `v0.1.10`:** registration responses use `agentId`, but `Agent.ID`
  expects `id`; derive the ID from `did:grantex:<agentId>`. Registration also
  sends optional zero values, while updates cannot set `status` or clear scopes;
  provide registration fields and use REST for those updates.

  `LogAuditParams` lacks required `agentDid` and `principalId`; use REST or CLI
  for audit writes. `AuditEntry` omits `DeveloperID`, and `Since`, `Until`,
  `Page`, and `PageSize` list filters are ignored by the API; use the four
  supported filters and raw REST responses when `developerId` is required.

  Agent and audit list metadata is not returned; use slice lengths. List helpers
  also fail to URL-encode reserved filter characters; avoid those values or issue
  a `net/url`-encoded REST request. These workarounds remain required until a
  corrected module release is published.
</Warning>

<Warning>
  **MCP Auth `2.0.2`:** use a single process for evaluation only. Authorization
  codes are always process-local, `consentUi` does not create a page,
  `onTokenIssued` is not called, `allowedRedirectUris` is not a server-wide
  allowlist, middleware/introspection do not check current revocation state, and
  the Grantex authorization code is not persisted for the token handler. See [MCP Auth Server](/features/mcp-auth-server) for the detailed
  endpoint and deployment matrix.
</Warning>

## Reproducible installation

Pin exact versions in applications, examples, CI, and deployment manifests:

<CodeGroup>
  ```bash TypeScript theme={null}
  npm install @grantex/sdk@0.3.13
  ```

  ```bash Python theme={null}
  python -m pip install grantex==0.3.14
  ```

  ```bash Go theme={null}
  go get github.com/mishrasanjeev/grantex-go@v0.1.10
  ```

  ```bash MCP Auth theme={null}
  npm install @grantex/mcp-auth@2.0.2 @grantex/sdk@0.3.13
  ```
</CodeGroup>

Unpinned `npm install`, `pip install`, and `go get` commands resolve according to
their registries and module proxy. Use the pinned commands above when the build
must be repeatable.

## How to read release information

* [Public machine-readable release status](https://grantex.dev/release-status.json)
  is the canonical retrieval URL for tools and agents. The same file is versioned
  in the [GitHub repository](https://github.com/mishrasanjeev/grantex/blob/main/release-status.json) and drives automated cross-surface checks.
* [Compatibility matrix](https://github.com/mishrasanjeev/grantex/blob/main/COMPATIBILITY.md)
  maps repository packages to artifact names, versions, and publication status.
* [Repository changelog](https://github.com/mishrasanjeev/grantex/blob/main/CHANGELOG.md)
  records cross-project work. Its latest numbered entry can trail independently
  published SDK patches.
* Package registries are authoritative for public availability:
  [npm (`@grantex/sdk`)](https://www.npmjs.com/package/@grantex/sdk),
  [PyPI (`grantex`)](https://pypi.org/project/grantex/),
  [Go Packages](https://pkg.go.dev/github.com/mishrasanjeev/grantex-go), and
  [npm (`@grantex/mcp-auth`)](https://www.npmjs.com/package/@grantex/mcp-auth).

## Upgrade checklist

1. Read the package-specific notes in the compatibility matrix and changelog.
2. Confirm the required Node.js, Python, or Go toolchain version.
3. Update the exact dependency version and regenerate the relevant lockfile.
4. Run your authorization, token-verification, scope-enforcement, and revocation
   tests before deployment.
5. For self-hosted environments, verify the API contract used by your service;
   an SDK-only patch does not upgrade the service automatically.

<Warning>
  Do not infer publication from a repository manifest or marketing page alone.
  Confirm the exact artifact on its public registry before promoting a release.
</Warning>