io.github.navapbc/rebar
Event-sourced ticket system with a Jira reconciler, exposed as an MCP server.
Using io.github.navapbc/rebar in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireVerdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-07-24).
Contracts can change after screening, with no version bump. The gate pins io.github.navapbc/rebar’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
REBAR_ROOTPath to the repo root that holds the .tickets-tracker store (defaults to the git toplevel of the working dir).
REBAR_MCP_READONLYSet to 1 to expose only the read tools (no write/mutation tools).
REBAR_MCP_ALLOW_LLMSet to 1 to enable the billable LLM tools (review_ticket / review_code / scan_spec / verify_completion / review_plan); off by default.
REBAR_MCP_ALLOW_JIRA_SYNCSet to 1 to allow the live (mutating) Jira reconcile mode; otherwise reconcile is dry-run only.
REBAR_MCP_TRANSPORTTransport for the MCP server: 'stdio' (default) or 'http' (the optional Streamable-HTTP transport).
REBAR_MCP_HTTP_HOSTBind host for the Streamable-HTTP transport (default 127.0.0.1).
REBAR_MCP_HTTP_PORTBind port for the Streamable-HTTP transport (1-65535; default 8000).
REBAR_MCP_HTTP_PATHURL path the Streamable-HTTP transport serves on (default /mcp).
REBAR_MCP_HTTP_ALLOWED_HOSTSComma-separated allowlist of exact host:port values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.
REBAR_MCP_HTTP_ALLOWED_ORIGINSComma-separated allowlist of exact Origin values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.
REBAR_MCP_HTTP_TLS_AT_EDGESet to 1 to acknowledge TLS is terminated at the edge; required to bind the Streamable-HTTP transport to a non-loopback host.
REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTPSet to 1 to acknowledge running the Streamable-HTTP transport without a token verifier; required to boot the HTTP transport while auth is off.
REBAR_MCP_AUTH_ENABLEDSet to 1 to enable MCP authentication (the composite token verifier + Resource-Server wiring); off by default.
REBAR_MCP_AUTH_STRATEGIESComma-separated, ordered list of token-verifier strategies to compose (closed set: static, jwt, introspection, proxy, custom).
REBAR_MCP_AUTH_ISSUER_URLOAuth authorization-server issuer URL advertised in the Protected-Resource Metadata (RFC 9728) when auth is enabled.
REBAR_MCP_AUTH_RESOURCE_SERVER_URLThe single resource identifier (RFC 8707 audience) for this server; the composite verifier re-checks every accepted token against it.
REBAR_MCP_AUTH_REQUIRED_SCOPESComma-separated scopes a caller must hold; the SDK returns 403 insufficient_scope when a principal lacks one.
REBAR_MCP_AUTH_STATIC_TOKENS_FILEPath to the JSON secrets file for the static-bearer verifier (stores only SHA-256 digests of the accepted tokens).
REBAR_MCP_AUTH_JWT_JWKS_URIHTTPS JWKS endpoint the `jwt` verifier fetches signing keys from (an OIDC provider's .well-known/jwks.json).
REBAR_MCP_AUTH_JWT_ISSUERExpected `iss` claim for the `jwt` verifier; falls back to REBAR_MCP_AUTH_ISSUER_URL when unset.
REBAR_MCP_AUTH_JWT_ALGORITHMSComma-separated PINNED, asymmetric-only JWS algorithms for the `jwt` verifier (default RS256,ES256); a symmetric algorithm on a JWKS source is refused.
REBAR_MCP_AUTH_JWT_LEEWAYClock-skew leeway in seconds applied to exp/nbf validation by the `jwt` verifier (default 60).
REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWNMinimum seconds between JWKS refetches triggered by an unknown key id (the concurrency-safe flood guard; default 30).
REBAR_MCP_AUTH_JWT_JWKS_TIMEOUTHTTP timeout in seconds for the `jwt` verifier's JWKS fetch (default 10).
REBAR_MCP_AUTH_JWT_EXPECTED_TYPWhen set, the `jwt` verifier requires the JWT header `typ` to equal this (e.g. at+JWT per RFC 9068); unset skips the check.
REBAR_MCP_AUTH_JWT_ALLOW_PRIVATE_JWKS_HOSTSet to 1 to permit a private/link-local/loopback JWKS host (SSRF guard is on by default); off by default.
REBAR_MCP_AUTH_INTROSPECTION_ENDPOINTThe `introspection` verifier's RFC 7662 endpoint URL (must be https://); the opaque token is POSTed here on every request (no caching).
REBAR_MCP_AUTH_INTROSPECTION_CLIENT_IDThe client id the `introspection` verifier presents to the Authorization Server via HTTP Basic (client_secret_basic).
REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENVThe NAME of the env var holding the introspection client secret (never the secret itself); must be present + non-empty at startup or the server refuses to start (fail-closed).
REBAR_MCP_AUTH_INTROSPECTION_ALLOW_PRIVATE_HOSTSet to 1 to permit a private/link-local/loopback introspection endpoint host (SSRF guard is on by default); off by default.
REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUDSet to 1 to accept an active introspection response that OMITS `aud` (many AS do); off by default (fail-closed reject).
REBAR_MCP_AUTH_PROXY_SECRET_ENVThe NAME of the env var holding the trusted-proxy shared secret (never the secret itself); must be present + non-empty at startup or the `proxy` verifier refuses to start (fail-closed).
REBAR_MCP_AUTH_PROXY_SECRET_HEADERThe header the fronting proxy sends its shared secret on; the identity is trusted only when this matches (constant-time; default x-proxy-auth).
REBAR_MCP_AUTH_PROXY_IDENTITY_HEADERThe header carrying the proxy-authenticated principal identity, trusted only when the secret header validates (default x-forwarded-user).
REBAR_MCP_AUTH_PROXY_SCOPESComma-separated fixed scope set granted to proxy-authenticated principals; empty by default (the principal holds no scopes).
REBAR_MCP_AUTH_CUSTOM_IMPORTThe `custom` strategy's `module:factory` import string, resolving to a factory that returns a TokenVerifier; a TRUSTED operator config value that loads and executes the operator-configured code at startup (fail-closed on any load error).
This MCP server enables users to perform scientific computations regarding linear algebra and vect…
Optimize crew and workforce schedules, resource allocation, and routing with linear and mixed-inte…
A Notion workspace is a collaborative environment where teams can organize work, manage projects,…