rebar (navapbc/rebar) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 50 tools. No publisher has claimed this listing.

D
Caution
54/100

rebar

Rebar can block work until an AI plan review passes, require signed completion verification before close, and reconcile its event-sourced ticket record with Jira across CLI, Python, and MCP. GitHub is a read-only mirror. Code review runs in Gerrit.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

navapbc

Source: Glama · also listed on github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: GOOGLE_SECRET_PARAM. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 6 credentials: ORIGIN_SECRET, JIRA_DC_ADMIN_PASSWORD, JIRA_DC_PASSWORD, GITHUB_TOKEN, REBAR_SIGNING_KEY, JIRA_API_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAWS_REGION
configBASE_DOMAIN
configCOOKIE_DOMAIN
configCOOKIE_SECRET_PARAM
configGOOGLE_CLIENT_ID
configGOOGLE_SECRET_PARAM
configHOSTED_DOMAIN
🔐 secretORIGIN_SECRET
configREDIRECT_URI
configSESSION_TTL_SECONDS
configREVIEW_BOT_PORT
configREBAR_RECONCILER_LOCK_STEAL
configREBAR_ROOT"env": { "": "/path/to/your/repo" }
configREBAR_MCP_READONLYinstead.) Server flags: =1 exposes only read tools;
configREBAR_MCP_ALLOW_LLM
configREBAR_MCP_ALLOW_JIRA_SYNCreconcile is dry-run unless =1. Both flags
configGITHUB_REPOSITORY
configX
configJIRA_DC_BASE_URL
configJIRA_DC_ADMIN
🔐 secretJIRA_DC_ADMIN_PASSWORD
configJIRA_DC_MAP_OUTPUT_DIR
configJIRA_DC_USER
🔐 secretJIRA_DC_PASSWORD
configJIRA_DC_PROBE_OUTPUT_DIR
configCONCLUSION
configFAILURE_OBSERVED
configREBAR
configPROBE_LIVE
configREBAR_SYNC_PULLsync.pull (env ) — on (default) lets reads fetch from the
configREBAR_SYNC_PUSHsync.push (env ) — always (default) pushes each write
configPROBE_INJECT_FAIL
configCLAUDE_JOB_DIR
configREBAR_CONFIG
configREBAR_TRACKER_DIRtracker.dir = ".tickets-tracker" # store worktree/symlink dir (env )
configREBAR_LLM_CONFIG_FILE
configXDG_CONFIG_HOME~/.config/rebar/config.toml (honoring $). Precedence, highest
configREBAR_CONFIG_UNKNOWN_KEYS
configREBAR_LOG_LEVEL
configREBAR_OPCERT_KEY_PATH
configREBAR_OPCERT_ENV_ID
configREBAR_DOCS_URL
🔐 secretGITHUB_TOKEN
🔐 secretREBAR_SIGNING_KEY
configJIRA_URL
configJIRA_USER
configJIRA_PROJECT
configOTEL_EXPORTER_OTLP_ENDPOINT
configREBAR_TEST_COMPACT_RENAME_BARRIER
configREBAR_DETECTED_BY
🔐 secretJIRA_API_TOKEN
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

50/50 tools missing one or more hints — review_ticket (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); review_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); scan_spec (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +47 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — unlink_tickets deletes at line 232 (rebar.unlink(id1, id2))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

47/50 tool handlers declare input schemas (94%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 5/50 tool handlers wrap calls in try/catch (10%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/navapbc/rebar?variant=verified)](https://m8ven.ai/mcp/navapbc/rebar)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 66cabeb4d5f5100feebbde143b059b991d890c33
code hash: 4e370ccc0c0ed088d97be5d6841dbe8b7d6569e4a902a60107fb65e0f72f58f8
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client